Cannnot connection with RDC using hostname
I have a domain with two dc's. I have been using RDC to access one from the other, that is until this morning. Now, I get the error msg that "the target computer is not accessible because it is either 1) turned off or 2) RDC is turned off or 3) the computer is not on the network." None of this is true. After research I found that I could connect using the target machine's IP. But when I ping it the DNS resolution is to the network's public IP and it fails. I checked th e DNS service on both DC's. On the target machine it's working, but on the other DC, it has failed to start with an error code 4000, "The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code." What to do next? How does one re-load a zone and how could this have suddenly stopped working?
When DNS failed to start, was that just after a server reboot? Have you tried starting the DNS service manually? Does it still fail?
ASKER
It seems to have stopped working after the last weekly update. In server manager DNS says it is running but nothing changes when I restart it manually, except another 4000 error code. BTW, the log lists a 4000 error every 11 minutes.
Often, a DNS Event ID 4000 will be accompanied by another event, such as ID 4013 or 4015. Are these or other events appearing along with the 4000?
What version of windows are the DC's running?
Also, can you run an "ipconfig /all" on the affected server and post the output here?
What version of windows are the DC's running?
Also, can you run an "ipconfig /all" on the affected server and post the output here?
ASKER
There i are multiple 4521:
The DNS server encountered error 13 attempting to load zone jskent.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
and one 708:
The DNS server did not detect any zones of either primary or secondary type during initialization. It will not be authoritative for any zones, and it will run as a caching-only server until a zone is loaded manually or by Active Directory replication. For more information, see the online Help.
The DNS server encountered error 13 attempting to load zone jskent.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
and one 708:
The DNS server did not detect any zones of either primary or secondary type during initialization. It will not be authoritative for any zones, and it will run as a caching-only server until a zone is loaded manually or by Active Directory replication. For more information, see the online Help.
Check the network settings on that server. Does it have just one adapter? What is it's IP address, and what are the DNS servers it's pointing to? (Is it pointing to itself?)
ASKER
The source server (not the target) shows IPs 192.168.1.11 and 12.
DNS servers are 192.168.1.11 and 12. The target server is 192.168,1.8 & 43. It seems to have the only working DNS service yet the source server doesn't refer to any machine but itself.
DNS servers are 192.168.1.11 and 12. The target server is 192.168,1.8 & 43. It seems to have the only working DNS service yet the source server doesn't refer to any machine but itself.
Just to make sure I'm clear, let's call them ServerA and ServerB
ServerA has 2 network adapters, with IP's of 192.168.1.11 and 192.168.1.12
The DNS servers for each network interface are pointing to 192.168.1.11 and 192.168.1.12
ServerB also has 2 adapters, with 192.168.1.8 and 192.168.1.43
Is ServerA the one with the DNS errors in the event log?
What are the dns server settings on ServerB's network adapters?
If each server is only pointing to itself for DNS resolution, that's going to cause issues. I would suggest you change the secondary DNS server on each one to point to the other server.
ServerA has 2 network adapters, with IP's of 192.168.1.11 and 192.168.1.12
The DNS servers for each network interface are pointing to 192.168.1.11 and 192.168.1.12
ServerB also has 2 adapters, with 192.168.1.8 and 192.168.1.43
Is ServerA the one with the DNS errors in the event log?
What are the dns server settings on ServerB's network adapters?
If each server is only pointing to itself for DNS resolution, that's going to cause issues. I would suggest you change the secondary DNS server on each one to point to the other server.
ASKER
Server B 192.168.1.8 is pointed to 192.168.1.12 and to 127.0.0.1
Server B 192.168.1.43 is pointed to 192.168.1.11 and 192.168.1.12
Server A 192.168.1.11 is pointed to 192.168.1.11 and 192.168.1.12 and 127.0.0.1
Server A 192.168.1.12 is pointed to 129.168.1.11 and 192.168.1.12 and 127.0.0.1
Server B 192.168.1.43 is pointed to 192.168.1.11 and 192.168.1.12
Server A 192.168.1.11 is pointed to 192.168.1.11 and 192.168.1.12 and 127.0.0.1
Server A 192.168.1.12 is pointed to 129.168.1.11 and 192.168.1.12 and 127.0.0.1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Bingo! That did it. Both ping and RDC by hostname now work. I can't imagine what might have change to make it stop working or why it would have worked with the previous setup. But anyway, many thanks for your help.
No problem, I'm glad you got it woking.
Since my last response resolved your issue, I'd appreciate it if you would mark that post as the answer, so that your post will no longer appear in the list of unanswered questions, and I will get credit for the answer.
Since my last response resolved your issue, I'd appreciate it if you would mark that post as the answer, so that your post will no longer appear in the list of unanswered questions, and I will get credit for the answer.
ASKER
RR. Wilco.
ASKER
Many thanks again.