J.R. Sitman
asked on
Need advice removing a Domain Controller
I need to remove a DC that is the one the users are authenticating to. As a test I shut it down and this morning some users could log on to the other DC and some not. How do I trouble shoot the problem?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
The DNS setting for the DNS server should be it's own IP and the secondary should be the other DNS server, correct?
@sysreg2000. Already done. Thanks
@sysreg2000. Already done. Thanks
Yes.
You need to verify that client's settings have those entries as well.
You need to verify that client's settings have those entries as well.
ASKER
I have minimum DNS experience, but I noticed what I would think is a "big" problem. Both our DNS servers have a subnet of 255.255.255.0. One of the computers I checked is 255.255.0.0. This is "BAD" right?
How would this happen and how do I correct it before I DCPromo the DC?
How would this happen and how do I correct it before I DCPromo the DC?
ASKER
Hope you guys return to this post tomorrow. :-(
Just change the subnet mask on your client.
Maybe somebody accidentally forgot the 255 on the third octet or the DHCP scope is misconfigured.
Maybe somebody accidentally forgot the 255 on the third octet or the DHCP scope is misconfigured.
ASKER
DHCP is set to 255.255.0.0, should I leave that and change the servers, or leave the servers and fix DHCP?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
won't a reboot of the clients do the same?
A reboot will provide you the same result.
What kind of errors did you users get when the DC was down?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks to all
http://www.petri.co.il/transferring_fsmo_roles.htm
Also make sure the other DC is a catalog server as well. Make sure that the users who logged in, were ACTUALLY logging in using the other server, and not just using cached credentials. From a command prompt on the client run echo %logonserver% to be sure.