i just transferred fsmo roles to a new domain controller, my network has three domain controllers all active directory integrated, with DNS active directory zones, they are all global catalogs. This is a single domain, nothing fancy.
Problem i am having is that when i log into a workstation i expect to see the logon server, using cmd and set log, to be dc3 which is the domain controller that now holds all the fsmo roles. What i see is that the workstation's logon server is dc2. Could there be too much traffic on the switch that dc3 is on and therefore the workstation is getting pushed to another domain controller?
update: actually it is either dc1 or dc2 that it is using as logon server but not the expected dc3. I have verified that my dns entries in order for the dhcp scope are dc3, dc1 and then dc2
update 2: we actually are seeing a mix of all three dc's responding to workstations
Answer
As far as I know, the placement of the FSMO roles has nothing to do with DC selection by the client. In addition, the DC's have no awareness of the network infrastructure so they can't "push" a client to a specific DC based on network conditions.
Here are some articles that detail the DC locator process:
http://support.microsoft.com/kb/247811
http://technet.microsoft.com/en-us/library/cc978011.aspx
http://technet.microsoft.com/en-us/library/cc961830.aspx
No comments:
Post a Comment