By jsizer ·
All of a sudden yesterday we could no longer open the Exchange Management Console to administer mail. It is telling up that it cannot find a Domain Controller. I started poking and finding that we have a major issue and I don't know what happend and I cannot seem to fix it no matter what I do... I think that something is screwed up royally! Here is my netdiag and dcdiag... My DNS looks different but I don't have anything to compare it to... I think that somehow we are missing parts of the tree that I remember seeing there before. I think that they were like something to that effect.


DCDIAG - I have replaced the domain and server names... I am running W2K3 x64 Standard. This machine is a DC and running as the GC and DNS/WINS server. I have a 2nd DNS/WINS server on a DC2.

Testing server: Default-First-Site-Name\CSCIDC1
Starting test: Connectivity
* Active Directory LDAP Services Check
The host could
not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
( couldn't be
resolved, the server name ( resolved to the IP
address (x.x.x.x) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... servername failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\servername
Skipping all tests, because server servername is
not responding to directory service requests


DNS test . . . . . . . . . . . . . : Failed
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for read
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for read
[FATAL] No DNS servers have the DNS records for this DC registered.

I have done everything that I can find on the internet. I have stopped the netlogon and restarted. I have stopped and renamed the netlogon.dns file and restarted. I have tried the netdiag /fix and dcdiag /v/fix. I am at a complete and entire loss at this time!!!!!

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

log on to the server that's running DNS


make sure the DNS service is started. Check your DNS zone and records.

Collapse -

Fix your DNS problems.

If you're having problems Web surfing, you may have a DNS problem. Here are quick ways to fix it.
DNS, though, can be your foe as well as your friend. DNS problems may stop you from being able to visit Web sites. If you're having problems connecting, it doesn't take much work to see if DNS is the cause, and if it is, to try to fix it.
To find out whether DNS is a potential culprit when you're having trouble connecting to a site, first ping the site to which you can't connect by issuing the ping command at the command prompt, like this:
If the site is live, you'll get an answer like this
[ with 32 bytes of data:

Reply from bytes=32
time=22ms TTL=235
Reply from bytes=32
time=23ms TTL=235
Reply from bytes=32
time=23ms TTL=235
Reply from bytes=32
time=24ms TTL=235

Ping statistics for
Packets: Sent = 4, Received = 4,
Lost = 0 (0% loss),
Approximate round trip times in
Minimum = 22ms, Maximum = 24ms,
Average = 23ms
If it's not, you'll get a response like this:
Ping request could not find host.
Please check the name and try again.
If you ping a site and it's live but you can't connect to it with your browser, a DNS problem might be the reason. If you suspect you're having a DNS problem, take the following actions:
Check your HOSTS file
If your HOSTS file contains an incorrect or outdated listing, you won't be able to connect. Even if you don't recall adding listings to a HOSTS file, it still might contain listings, because some Internet accelerator utilities edit them without telling you. Open your HOSTS file with Notepad and see if the site you can't connect to is listed there. If it is, delete the entry, and you should be able to connect.
For details about editing a HOSTS file, see "Hack DNS for lightning-fast Web browsing."
Check your DNS settings
Make sure your DNS settings are correct for your ISP or network. If you've changed your DNS settings to use a service such as OpenDNS, for example, you might have entered them incorrectly.
Find out from your ISP or network administrator what your DNS settings are supposed to be, or check the OpenDNS site (or another DNS service) for their server settings. Once you've done that, you'll need to make sure that you've entered the DNS settings properly.
Check the article "Hack DNS for lightning-fast Web browsing" for details about how to change your DNS settings. Then change the DNS servers to the proper ones, or choose "Obtain DNS server address automatically" if your ISP or network administrator tells you to use that setting.
Flush your DNS cache
The problem might be related to your DNS cache, so flush it out. To flush the cache, type ipconfig /flushdns at a command prompt.
Find out if your ISP is having DNS problems
Your ISP could be the source of the problem. One possibility is that one of its DNS servers is down and you're trying to access the downed server. If you know the addresses of the DNS servers, ping each of your ISP's DNS servers, and if any of them don't respond, remove them from your DNS list.
If you don't know the address of the DNS servers and you're supposed to use the choose "Obtain DNS server address automatically" setting, you'll have to call your ISP to see whether its DNS servers are having problems. Alternately, you can use the OpenDNS servers instead of your ISP's DNS servers. For details, see "Hack DNS for lightning-fast Web browsing."

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums