Networks

Ask something
Discussion Locked

Changing Authenticating DC's

0 helpful
5 replies

by legj1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Site A and Site B are connected via T-1. Site A has had two Domain Controllers. Site B had no DC's until today. We add the DC, but users on Site B subnet are still authenticating to Site A DC's. Why? What can I do to force Site B Users to authenticate to SIte B DC?
100% Win2k Domain. Perhaps I have not setup my Site correctly. Perhaps there is a Group Policy that will force Users/Groups/Locations to use a certain DC. All help appreciated!

5 replies

by joseph moore

Do you actually have Sites configured in AD Sites & Services? Because you said that you have sites A & B, but that there was no DC in site B until today.
So, without a DC in a Site, you can't have a Site!

So, I just want to be sure. Do you have 2 Sites set up in Sites & Services? Did you move the new DC into Site B? Because you associate a Domain Controller with a Site, and then the users in that Site authenticate to the DC in the Site.

hope this helps

by legj1

Yes, I have created a Site and moved the DC. I notice under NTDS that replication is every 24 hrs. Is there anyway you can force replication? Perhaps this is the problem?

by nettek

Microsoft added a new utility with the release of SP 4 (and greater) called SETPRFDC.EXE. This will allow you to force a client to authenticate to a particular DC. Unfortunately, I believe it is not part of the SP download, but only comes on the SP CD that can be ordered from Microsoft.

This discussion is closed to new replies.