G
Greg Porchia
When demoting the DC I get an error "FAILED FINDING A
SUITABLE DOMAIN CONTROLLER". How can I correct this?
SUITABLE DOMAIN CONTROLLER". How can I correct this?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Greg Porchia
Can you tell me what in DNS I'm suppose to be looking for
J
Jimmy Andersson
Make sure you can do name resolution correctly.
241515 How to Verify the Creation of SRV Records for a Domain Controller:
http://support.microsoft.com/?id=241515
260371 Troubleshooting Common Active Directory Setup Issues in Windows 2000:
http://support.microsoft.com/?id=260371
Regards,
/Jimmy
241515 How to Verify the Creation of SRV Records for a Domain Controller:
http://support.microsoft.com/?id=241515
260371 Troubleshooting Common Active Directory Setup Issues in Windows 2000:
http://support.microsoft.com/?id=260371
Regards,
/Jimmy
H
Herb Martin
Greg Porchia said:Can you tell me what in DNS I'm suppose to be looking for
Run DCDiag, especially on the to be demoted DC, save
the output in a text file -- search that file for ERROR, WARN,
FAIL.
DCDiag is in the Support Tools from the Win2000+ Server
CD-ROM.
Also run it on other DCs -- they use DNS to "find each other"
- as a 'locator' or 'rendezvous' service.
Each DC must have it's own "client settings" in the NIC\IP\DNS Server
setting pointed to the "Dynamic DNS" (set of) servers.
The DNS Server(s) must in fact be enabled for dynamic update.
They will automagically create a BUNCH of records in several
sub-domains that begin with _underscore.
N
Nicki
Check to see that you did not disable port 135 (RPC) which
was a recommendation floating around when Blaster hit. We
had a similar problem and it was caused by the network
guys blocking port 135.
was a recommendation floating around when Blaster hit. We
had a similar problem and it was caused by the network
guys blocking port 135.