GUID DNS name could not be resolved

  • Thread starter Thread starter Adam
  • Start date Start date
A

Adam

I have a Windows 2000 Exchange Server which also is my PDC
for my domain. I had a seperate domain that handled the
office but now am trying to move everything to the Windows
2000 domain and am having issues adding clients. My 3
servers all see each other, but when trying to add my
Windows XP workstation it cannot reach the domain
controller. Running DCDIAG on the server tells me that
the GUID DNS name coupld not be resolved to an IP
address. It also says although the GUID DNS name could
not be resolved, the server name resolved to the IP
address and was pingable. Check that the IP address is
registered correctly with the DNS server.
Unfortunately I am not an expert at DNS. We use our ISP's
DNS servers for internet resolution.
Any advice on how to easily get the servers DNS record
correct so that my clients can reach the machine would be
apprecaited.
Thanks in advance
 
In
Adam said:
I have a Windows 2000 Exchange Server which also is my PDC
for my domain. I had a seperate domain that handled the
office but now am trying to move everything to the Windows
2000 domain and am having issues adding clients. My 3
servers all see each other, but when trying to add my
Windows XP workstation it cannot reach the domain
controller. Running DCDIAG on the server tells me that
the GUID DNS name coupld not be resolved to an IP
address. It also says although the GUID DNS name could
not be resolved, the server name resolved to the IP
address and was pingable. Check that the IP address is
registered correctly with the DNS server.
Unfortunately I am not an expert at DNS. We use our ISP's
DNS servers for internet resolution.
Any advice on how to easily get the servers DNS record
correct so that my clients can reach the machine would be
apprecaited.
Thanks in advance
Click to expand...

Usually the issue with this is that the ISP's DNS server or the router's
address is used for DNS in your AD internal machines (DCs and clients). Only
use your internal DNS since that;s where all the AD records are stored.

Other issues can be that your AD domain name is a single label name and
doesn't work properly with AD especially with SP4. XP clients have
difficulty with single label names.

If you can post an ipconfig /all from the DC and one of your clients and let
us know the AD domain name, we can diagnose it from there for you.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top