Thanks. After trying to dig up some old info, I had the sites and services setup but I didnt have them in different sites. So I added the different subnets and create different sites now and put a site link between them. Im hoping this clears up which servers talk to which dc's.
Michael, do you think I will still need to run this? Sounds like I will be good after a reboot now that the sites have been updated. Thats good info to have though we are preparing the DR site for a test in the next month or so, and will want to remember to failback all the servers talking to which DC's post rollback I would think :) -----Original Message----- From: Michael B. Smith [mailto:[email protected]] Sent: Monday, February 08, 2010 6:42 PM To: NT System Admin Issues Subject: RE: dc replication / logonserver Nltest /sc_reset:<domain>\<desired-dc> Note that a domain member, once connected to a particular DC, will continue to talk to that DC unless the site is changed or the secure channel reset or the DC isn't available. Netdom can do this too. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Benjamin Zachary - Lists [mailto:[email protected]] Sent: Monday, February 08, 2010 6:30 PM To: NT System Admin Issues Subject: dc replication / logonserver I have a site @ 600 users, with dual 100mb links between the primary and secondary site (a datacenter). We have a sensitive network application being deployed and find people getting kicked out of it because the server cannot authenticate them fast enough (1ms is the limit, don't ask why). So on some of the servers I keep finding their 'logonserver' being listed as the 3rd DC in the datacenter. In AD Sites/Services there is full replication between all 3, and while the link is a full fiber 100mb connection, I wanted to keep that locally. I wouldn't normally think anything of it, but the application developers are pointing this out as the potential problem so I have to make it so all computers and servers in the primary network do not talk to the DC in the datacenter. In DNS no one is pointing to the remote site, so I guess the remote server is just responding faster than the local dc's. WINS/DHCP/DNS all have replication to this DC as well. Isnt there a simple way to do that? I know ive read up on wan links etc and I can force a particular domain controller in the registry but that's not going to be a fun permanent solution I don't think. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
