Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



DCDiag GUID Error

Windows Server Help


Reply
 
Thread Tools Search this Thread
  #1  
Old 06-02-2007
Thom Paine
 
Posts: n/a
DCDiag GUID Error

I'm having problems with my server, and I ran the dcdiag and it's coming up
about the guid of the server not resolving. I'm unsure how to correct this
error.

Testing server: Default-First-Site\PDC-RL-401
Starting test: Connectivity
PDC-RL-401's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(e2756922-bc3d-440c-a4b8-40794678c722._msdcs.RocklandFlooring.local)

couldn't be resolved, the server name

(PDC-RL-401.RocklandFlooring.local) resolved to the IP address

(192.168.0.2) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... PDC-RL-401 failed test Connectivity

Where would I go to fix this?

Thanks.



Reply With Quote
  #2  
Old 06-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

I should followup that google hits telling me to try dcdiag /fix and
stopping and starting the netlogon service have proved unsuccessful.


"Thom Paine" <painethom@hotmail.com> wrote in message
news:Okep0KhSHHA.1036@TK2MSFTNGP03.phx.gbl...
> I'm having problems with my server, and I ran the dcdiag and it's coming
> up about the guid of the server not resolving. I'm unsure how to correct
> this error.
>
> Testing server: Default-First-Site\PDC-RL-401
> Starting test: Connectivity
> PDC-RL-401's server GUID DNS name could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
>
>
> (e2756922-bc3d-440c-a4b8-40794678c722._msdcs.RocklandFlooring.local)
>
> couldn't be resolved, the server name
>
> (PDC-RL-401.RocklandFlooring.local) resolved to the IP address
>
> (192.168.0.2) and was pingable. Check that the IP address is
>
> registered correctly with the DNS server.
> ......................... PDC-RL-401 failed test Connectivity
>
> Where would I go to fix this?
>
> Thanks.
>



Reply With Quote
  #3  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:Okep0KhSHHA.1036@TK2MSFTNGP03.phx.gbl...
> I'm having problems with my server, and I ran the dcdiag and it's coming
> up about the guid of the server not resolving. I'm unsure how to correct
> this error.


Ok there are two major reasons for these failures so you check and correct
these, then re-run the NetDiag /fix or stop/start NetLogon AGAIN, as you
already
tried.

Typical reasons:

On DNS Server:
1) zone is not dynamic
2) zone doesn't exist
3) Multiple DNS servers, but not replicated (see other fixes too)
arrange secondary zone transfer from primary or other master

Check the above for both the "domain zone" and the _MSDCS zone if
it is separate (i.e., not a subdomain of the domain zone itself.)

On DC as a DNS "client":
1) NIC must point STRICTLY at the INTERNAL DNS servers
2) Remove any external (ISP etc) DNS server
3) If replication problem persists, set all DCs to ONE "favored" DNS
server until replication is fixed -- inefficient but
works for
temporary fix purposes

DC replication of AD and integrated DNS:
1) DCs are AD Integrated but not replicating so DNS is also not
replicating -- use "DNS client" #3 above.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #4  
Old 07-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

One quick question.

Should I have the DNS ip in the TCPIP properties of my nic to be 127.0.0.1
or should it be the IP address of my server?
This is on the server., not on workstations. On workstations I have only the
IP of the server.

Thanks.


Reply With Quote
  #5  
Old 07-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

Herb:

I have the _msdcs zone as a subdomain of my scps.lan domain. I looked at my
old server which is running Windows 2000 server that worked awesome and it
has the guid in the _msdcs zone. I tried creating this CNAME record but I
get an error that this CNAME record cannot be added to this domain because
it contains records that are incompatible with the cname record.

Also, I am unable to run netdiag as I get a different error. The error
message is:

The procedure entry point DnsGetPrimaryDomainName_UTF8 could not be located
in the dynamic link library DNSAPI.dll.

I have the Windows Server 2003 Resource kit, but I can't seem to get this
working after alot of reading and googling.

Thanks.

-=/>Thom

"Herb Martin" <news@learnquick.com> wrote in message
news:OQjrcyiSHHA.2188@TK2MSFTNGP03.phx.gbl...
>
> "Thom Paine" <painethom@hotmail.com> wrote in message
> news:Okep0KhSHHA.1036@TK2MSFTNGP03.phx.gbl...
>> I'm having problems with my server, and I ran the dcdiag and it's coming
>> up about the guid of the server not resolving. I'm unsure how to correct
>> this error.

>
> Ok there are two major reasons for these failures so you check and correct
> these, then re-run the NetDiag /fix or stop/start NetLogon AGAIN, as you
> already
> tried.
>
> Typical reasons:
>
> On DNS Server:
> 1) zone is not dynamic
> 2) zone doesn't exist
> 3) Multiple DNS servers, but not replicated (see other fixes too)
> arrange secondary zone transfer from primary or other
> master
>
> Check the above for both the "domain zone" and the _MSDCS zone if
> it is separate (i.e., not a subdomain of the domain zone itself.)
>
> On DC as a DNS "client":
> 1) NIC must point STRICTLY at the INTERNAL DNS servers
> 2) Remove any external (ISP etc) DNS server
> 3) If replication problem persists, set all DCs to ONE "favored"
> DNS
> server until replication is fixed -- inefficient but
> works for
> temporary fix purposes
>
> DC replication of AD and integrated DNS:
> 1) DCs are AD Integrated but not replicating so DNS is also not
> replicating -- use "DNS client" #3 above.
>
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com
> (phone on web site)
>



Reply With Quote
  #6  
Old 07-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

Here is a screnshot of my dns. Maybe that will help.

Thanks.

-=/>Thom




Reply With Quote
  #7  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:ORSeXPsSHHA.4844@TK2MSFTNGP03.phx.gbl...
> One quick question.
>
> Should I have the DNS ip in the TCPIP properties of my nic to be 127.0.0.1
> or should it be the IP address of my server?


It isn't that big a deal which you use. They route to the same place.

> This is on the server., not on workstations. On workstations I have only
> the IP of the server.


That is correct also. All of your DNS "clients" (all of your machines) must
use strictly the addresses of your Internal DNS server (set).

On a machine, 127.0.0.1 is equivalent to it's own address.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #8  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:%23jO6ufsSHHA.1600@TK2MSFTNGP05.phx.gbl...
> Herb:
>
> I have the _msdcs zone as a subdomain of my scps.lan domain. I looked at
> my old server which is running Windows 2000 server that worked awesome and
> it has the guid in the _msdcs zone. I tried creating this CNAME record but
> I get an error that this CNAME record cannot be added to this domain
> because it contains records that are incompatible with the cname record.


The above paragraph made some sense but ended in confusing me --
You would ahve ONLY the _msdcs in your AD zone if you started with
Win2000, but it would be separate (also) if you started with Win2003.

If separate, that zone needs to be dynamic and replicated to (or findable
by)
all of your internal DNS servers.

> Also, I am unable to run netdiag as I get a different error. The error
> message is:
>
> The procedure entry point DnsGetPrimaryDomainName_UTF8 could not be
> located in the dynamic link library DNSAPI.dll.


Likely wrong NetDiag. You need SP1 or some current NetDiag from the later
Support Tools. Or you are running Win2000 tools on Win2003 or vice versa.

> I have the Windows Server 2003 Resource kit, but I can't seem to get this
> working after alot of reading and googling.


"Can't seem to get it working" is not something that I can diagnose beyond
telling
you to go back to Microsoft and download the one that matches you OS and
SP status.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #9  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:e0kd9msSHHA.1228@TK2MSFTNGP06.phx.gbl...
> Here is a screnshot of my dns. Maybe that will help.



Sorry, I don't open .Doc files from unverified sources.

Post a jpg or something on a web site.

Do you currently have any DNS problems? What are you current symptoms?

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #10  
Old 07-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

> The above paragraph made some sense but ended in confusing me --
> You would ahve ONLY the _msdcs in your AD zone if you started with
> Win2000, but it would be separate (also) if you started with Win2003.
>


This is a brand new dell server running 2003 r2.
Everything was a fresh install. No upgrade was done.

> If separate, that zone needs to be dynamic and replicated to (or findable
> by)
> all of your internal DNS servers.
>
> Likely wrong NetDiag. You need SP1 or some current NetDiag from the later
> Support Tools. Or you are running Win2000 tools on Win2003 or vice versa.


I found the correct version and I am able to run netdiag and dcdiag now.
Here is the output from dcdiag. I have a dns issue and slow logons and some
other problems. I think the root of it is dns issues with group policy.


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\PDC-SCPS-2006
Starting test: Connectivity
The host ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan could
not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan) couldn't be

resolved, the server name (PDC-SCPS-2006.scps.lan) resolved to the
IP

address (192.168.142.150) and was pingable. Check that the IP
address

is registered correctly with the DNS server.
......................... PDC-SCPS-2006 failed test Connectivity

Doing primary tests

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

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : scps
Starting test: CrossRefValidation
......................... scps passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... scps passed test CheckSDRefDom

Running enterprise tests on : scps.lan
Starting test: Intersite
......................... scps.lan passed test Intersite
Starting test: FsmoCheck
......................... scps.lan passed test FsmoCheck


Thanks.

-=/>Thom


Reply With Quote
  #11  
Old 07-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

http://i160.photobucket.com/albums/t189/mostr/dns1.jpg

http://i160.photobucket.com/albums/t189/mostr/dns2.jpg

I have slow logins and logoffs as well as some AD problems that I was told
are likely from broken DNS.

Thanks.


Reply With Quote
  #12  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:%23Jm2kutSHHA.496@TK2MSFTNGP06.phx.gbl...
>> The above paragraph made some sense but ended in confusing me --
>> You would ahve ONLY the _msdcs in your AD zone if you started with
>> Win2000, but it would be separate (also) if you started with Win2003.
>>

>
> This is a brand new dell server running 2003 r2.
> Everything was a fresh install. No upgrade was done.


Including adding the 2003 DC to the Domain or Forest?

This is about upgrading Forests which you seem to imply when
you mention your Win2000 DC.

>> If separate, that zone needs to be dynamic and replicated to (or findable
>> by)
>> all of your internal DNS servers.
>>
>> Likely wrong NetDiag. You need SP1 or some current NetDiag from the
>> later
>> Support Tools. Or you are running Win2000 tools on Win2003 or vice
>> versa.

>
> I found the correct version and I am able to run netdiag and dcdiag now.
> Here is the output from dcdiag. I have a dns issue and slow logons and
> some other problems. I think the root of it is dns issues with group
> policy.
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site\PDC-SCPS-2006
> Starting test: Connectivity
> The host ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
> could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
>
> (ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan) couldn't be
>


Your DC is not properly registered in DNS.

Show me the IPConfig /all from each DC.

Check the _msdcs zone to make sure all DCs can resolve from it.

Check that it is dynamic.

Check that all DCs can find the "primary" (Master) and register themselves
in that zone.

After all this is correct, run "Netdiag /fix" or restart NetLogon service,
and then retry DCDiag /C /D on every DC.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #13  
Old 07-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:%238A89ztSHHA.3948@TK2MSFTNGP05.phx.gbl...
> http://i160.photobucket.com/albums/t189/mostr/dns1.jpg
>
> http://i160.photobucket.com/albums/t189/mostr/dns2.jpg
>
> I have slow logins and logoffs as well as some AD problems that I was told
> are likely from broken DNS.


Yes, see my other response this thread.

Clients which have trouble finding a DC through DNS may eventually
fail over and use NetBIOS etc and get on but slowly.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


Reply With Quote
  #14  
Old 08-02-2007
Thom Paine
 
Posts: n/a
Re: DCDiag GUID Error

>> This is a brand new dell server running 2003 r2.
>> Everything was a fresh install. No upgrade was done.

>
> Including adding the 2003 DC to the Domain or Forest?
>
> This is about upgrading Forests which you seem to imply when
> you mention your Win2000 DC.



This is the only server on our lan. We decommissioned our 2000 server. The
two servers were not on the lan at the same time. A new lan was built in a
separate enviornment and then the client pc's were wiped and loaded on the
new lan.


>> I found the correct version and I am able to run netdiag and dcdiag now.
>> Here is the output from dcdiag. I have a dns issue and slow logons and
>> some other problems. I think the root of it is dns issues with group
>> policy.
>>
>>
>> Domain Controller Diagnosis
>>
>> Performing initial setup:
>> Done gathering initial info.
>>
>> Doing initial required tests
>>
>> Testing server: Default-First-Site\PDC-SCPS-2006
>> Starting test: Connectivity
>> The host ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan
>> could not be resolved to an
>> IP address. Check the DNS server, DHCP, server name, etc
>> Although the Guid DNS name
>>
>> (ef255104-5591-4517-af81-393e31ac9dcf._msdcs.scps.lan) couldn't
>> be
>>

>
> Your DC is not properly registered in DNS.
>
> Show me the IPConfig /all from each DC.


There is only one DC.

Windows IP Configuration
Host Name . . . . . . . . . . . . : PDC-SCPS-2006
Primary Dns Suffix . . . . . . . : scps.lan
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : scps.lan
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-13-72-56-E8-26
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.142.150
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.142.10
DNS Servers . . . . . . . . . . . : 192.168.142.150
Primary WINS Server . . . . . . . : 192.168.142.150


>
> Check the _msdcs zone to make sure all DCs can resolve from it.
>

I'm not sure how to check this since we only have one server.

> Check that it is dynamic.



> Check that all DCs can find the "primary" (Master) and register themselves
> in that zone.
>

I ran the server setup wizard when we got the new server and added the roles
I wanted it to do. This included active directory, dns, dhcp fileserver, and
print server.

> After all this is correct, run "Netdiag /fix" or restart NetLogon service,
> and then retry DCDiag /C /D on every DC.


Thanks Herb. I appreciate all this help.

-=/>Thom


Reply With Quote
  #15  
Old 08-02-2007
Herb Martin
 
Posts: n/a
Re: DCDiag GUID Error


"Thom Paine" <painethom@hotmail.com> wrote in message
news:uNg0RduSHHA.4260@TK2MSFTNGP06.phx.gbl...
>>> This is a brand new dell server running 2003 r2.
>>> Everything was a fresh install. No upgrade was done.

>>
>> Including adding the 2003 DC to the Domain or Forest?
>>
>> This is about upgrading Forests which you seem to imply when
>> you mention your Win2000 DC.

>
>
> This is the only server on our lan. We decommissioned our 2000 server. The
> two servers were not on the lan at the same time. A new lan was built in a
> separate enviornment and then the client pc's were wiped and loaded on the
> new lan.


Did you properly DCPromo so that the old server was removed from the
AD? (Otherwise you must do the NTDSUtil "metadata cleanup" procedure").
This would cause 'failures' to replicate with the server that is no longer
available.

Do you have a GC? Many people who have decommisioned a DC have
neglected to set the replacement as a GC. (Set a GC in AD Sites and
Services.)

What about your FSMO, or single master roles? Did you transfer them to
the new DC? (If not you will need to seize those roles but this doesn't
seem
to be your issue.)

>> Your DC is not properly registered in DNS.
>>
>> Show me the IPConfig /all from each DC.

>
> There is only one DC.
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : PDC-SCPS-2006
> Primary Dns Suffix . . . . . . . : scps.lan
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : scps.lan
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-13-72-56-E8-26
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.142.150
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.142.10
> DNS Servers . . . . . . . . . . . : 192.168.142.150
> Primary WINS Server . . . . . . . : 192.168.142.150
>
>
>>
>> Check the _msdcs zone to make sure all DCs can resolve from it.

> I'm not sure how to check this since we only have one server.


Is _MSDCS a separate zone or not (previous messages were unclear on
this point)?

If separate is it DYNAMIC?

>> Check that it is dynamic.
>> Check that all DCs can find the "primary" (Master) and register
>> themselves
>> in that zone.
>>

> I ran the server setup wizard when we got the new server and added the
> roles I wanted it to do. This included active directory, dns, dhcp
> fileserver, and print server.


As a new domain or did you join it to an older domain before removing your
old DC?

>> After all this is correct, run "Netdiag /fix" or restart NetLogon
>> service,
>> and then retry DCDiag /C /D on every DC.

>
> Thanks Herb. I appreciate all this help.


Did it work yet?



Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Tags: ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "DCDiag GUID Error"
Thread Thread Starter Forum Replies Last Post
DCDIag error on Windows 2003 Server SP2 rao_jags Operating Systems 1 22-09-2010 08:16 AM
NetDiag Default Gateway Error -->DcDiag Advertising Error wimmer Active Directory 3 19-04-2010 07:57 PM
DCDiag Error KDC-SPN Tom Active Directory 8 01-03-2007 01:11 PM
DCDIAG Error and Solution Needed SENTHILKUMARAN B Active Directory 5 09-09-2006 04:22 AM


All times are GMT +5.5. The time now is 10:54 AM.