In a Microsoft AD environment, how does SecureLogin locate a Domain Controller?
SecureLogin follows the built-in AD functionality to find the closest DC.
The Active Directory physical structure governs when and how replication and authentication takes place. This is true of both intersite and intrasite replication.
Network site performance also impacts the location of objects and logon authentication. As users log on to the network, they are able to reach the closest domain controller site through the previous assignment of subnet information and Site definition in the AD Sites and Services MMC snapin.
If a Domain Controller cannot be located, the local cache file will be used (if enabled) and SecureLogin will continue to attempt to find the domain controller at the cache refresh interval and synchronise data between the offline cache and the directory once connection is established.
For more information, see the Microsoft Knowledgebase