Problem : DNS DsGetDcName returned information for… Server is not responding or is not considered suitable
I’ll start at the beginning. I inherited a Windows 2000 network that appeared to be running fine. It contained the following servers:
Fileserver: Windows 2000 PDC with all 5 FSMO roles, DNS and global catalog
Reaserver: Windows 2000 BDC
Dhcpserver: Windows 2000 member server. Ran DHCP and served as e-mail gateway.
Mercury: Windows 2000 PDC running e-mail service and hosting website
Mercury needs a bit more explanation. It thought it was a PDC on the same domain as the rest of the network (according to its AD) but it did not show up in the AD of either of the other two DCs. The login screen for mercury listed two domain options that were different from my present domain name. It could be logged in on one of these (SRSDI) but not the other. In My Network Places, the network showed up as having two domains. Mercury was the sole inhabitant of SRSDI (but again, according to its AD was in streetside) and the rest of the network was all in streetside . Also, mercury’s AD listed only itself and one other server–which I surmised was replaced long ago–as members of the streetside domain.
Mercury and dhcpserver are set up on workstations and are old and I need to replace them. They have shut off their services several times without warning. I have a new, unconfigured server that I plan to add to the network. I want to put Exchange 2003 on the new server and retire mercury. I also want to upgrade the entire network to Windows 2003. Of the 2 W2k domain controllers, only the PDC appears to be running services vital to the network. The BDC is running SQL server, but I don’t know what for. The tech I replaced also did not know why we would need it. Because all our network file storage is on the PDC, I want to preserve that network name. If I don’t, I will have to reconfigure a whole lot of systems. It is summer, and this is a school, so I have time to take some things offline for a bit without disrupting productivity terribly.
So my plan is:
1. Setup the new, unconfigured server as the PDC with Windows 2003
2. Change name of fileserver (the old Windows 2000 PDC) after its demotion to member server (say I call it fileserver2)
3. Reformat the old Windows 2000 BDC with Windows 2003 server, name it fileserver, and make it the PDC. Begin moving the network storage and applications from fileserver2 to fileserver
4. Install Exchange 2003 on the first server after it is demoted by the promotion of the old server in step 3.
Then I will gradually retire mercury, dhcpserver, and fileserver2. Once fileserver2 can be taken offline, I will install Windows 2003 on it and spread some of the network services around.
Here is what I have done so far:
1. Demoted reaserver to member server and took it offline.
2. Demoted mercury to member server (had to use the option this server is the only domain controller in the domain). That went finewhy didnt I do it months ago?
3. Installed Windows 2003 on the new server.
4. Ran the adprep options on the new server and installed AD, but did not make the new server the PDC. This was not a smooth operation, but I guess the domain prep was good enough to complete the AD installation.
I currently have a windows 2000 PDC (fileserver) and a Windows 2003 BDC (netserver).
I get no errors when I run netdiag /q on fileserver. When I run dcdiag /c /q on fileserver, I get NO RECORD OF FILE REPLICATION SYSTEM, SYSVOL STARTED.
When I run dcdiag on netserver, I get:
C:\Documents and Settings\Administrator.STR
Warning: DsGetDcName returned information for \\fileserver.streetside.or
when we were trying to reach NETSERVER.
Server is not responding or is not considered suitable.
……………………. NETSERVER failed test Advertising
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
……………………. NETSERVER failed test frsevent
An Error Event occured. EventID: 0x00000416
Time Generated: 06/26/2006 16:00:16
Event String: The DHCP/BINL service on the local machine,
……………………. NETSERVER failed test systemlog
When I run netdiag on netserver, I get only the following error.
Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local
machine. This machine is not working properly as a DC.
[WARNING] You don’t have a single interface with the <00> ‘WorkStation Servi
ce’, <03> ‘Messenger Service’, <20> ‘WINS’ names defined.
I want to promote netserver to the PDC, but do not want to do so unless I am confident everything is running fine.
There is a whole lot more going on here than I have stated, and I think I have probably given a lot of irrelevant information anyway. I figure you folks who suspect the problem will know what to ask me so I can supply only meaningful data. What I am really looking for is how to fix the errors in netdiag and dcdiag.
Solution : DNS DsGetDcName returned information for… Server is not responding or is not considered suitable
For .40 and .12 (since they are no longer DCs) you need to go through each and every container in the _msdcs container and remove any occurrence of those addresses.
You also want to remove the 184.108.40.206 address from the same containers.
Is the last IP actually setup on the NIC of one of your DCs?
If this is simply to direct internal clients to the website locally, then you need to add a CNAME record to the forward lookup zone. This IP should NOT be registered to any SRV records since it is not local. I suspect this might be one of your pain points.