Force a client to use different DC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have seen an article that mentions using SETPRFDC but as I'm not dealing
with NT4 machines, this won't work. I'm not so interested in which one they
use when they boot up(found that registry hack), just swinging a client
that's maybe using DC2 to look at DC3. Kind of like the nslookup command lets
you use another DNS server.

What has replaced SETPRFDC for newer OS's? Are there tools that already
exist on the systems that I can leverage to force the client to a different
DC?
 
Aleric said:
I have seen an article that mentions using SETPRFDC but as I'm not dealing
with NT4 machines, this won't work. I'm not so interested in which one
they
use when they boot up(found that registry hack), just swinging a client
that's maybe using DC2 to look at DC3. Kind of like the nslookup command
lets
you use another DNS server.

What has replaced SETPRFDC for newer OS's? Are there tools that already
exist on the systems that I can leverage to force the client to a
different
DC?
Click to expand...


Really only possible if you create a site within AD
 
If it could be moved to the same domain but specified to a different DC, that
would be cool.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Force a client (2000/XP) to validate its logon against a specific 3
Logging into the correct DC 3
Disabling a W2k DC and making a newer server the main DC 2
reviving ad after first dc crashed 3
Rebuild a W2k server DC... 2
Oultook uses wrong DC 1
Force client to authenticate against specific DC 6
User authentication in windows 2000 domain failing to second domain controller 3

Back
Top