Problems and Solutions
Problems and Solutions
Server GUID DNS name could not be resolved to an IP address. Check items such as the DNS server,
DHCP and server name. Although the GUID DNS name (._msdcs.domain-name.local) couldn't be
resolved, the server name () resolved to the IP address (). Check that the IP address is registered
correctly with the DNS server.
This type of error will cause you to not be able to add computers to your domain, or even add new
domain controllers.
Obviously, a problem like this is going to bring AD to a grinding halt and provide little to no
functionality, so here's how to fix it:
Step1
Step2
Download DcDiag.exe
Step3
Step4-clear the ARP cache as well, you can do this by typing "arp –d
Step5
At the prompt type in dcdiag /fix
Step6
Still at the command prompt, type "dcdiag /fix", then "net stop netlogon" and
"net start netlogon
Or go to services.msc- restart the netlogon service
2-Common Problems on DHCP Server
The administrator can't connect to a DHCP server by using DHCP
Manager. The message that appears might be "The RPC server is
unavailable."
DHCP clients cannot renew the leases for their IP addresses. The
message that appears on the client computer is "The DHCP client could
not renew the IP address lease."
The DHCP client service or Microsoft DHCP service is stopped and cannot
be restarted.
Solution:= To restart a DHCP server that is stopped
3-Active directory Domain services problems and solutions
ntdsutil
3. At the ntdsutil: command prompt, type the following command, and
then press ENTER:
metadata cleanup