Re: DCDiag GUID Error
- From: "Thom Paine" <painethom@xxxxxxxxxxx>
- Date: Wed, 7 Feb 2007 14:36:37 -0500
[ You confused the issue by bringing up your 2000 Server a few
messages back in this thread. ]
Yes, I brought it up because I was comparing the old server setup to the new
server setup. Sorry about that.
Your DC is not properly registered in DNS.
There is only one DC.
Windows IP Configuration
Host Name . . . . . . . . . . . . : PDC-SCPS-2006
Primary Dns Suffix . . . . . . . : scps.lan
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)?
It is a subzone of the scps.lan zone.
I do not know how to tell if it is dynamic. I checked the properties on
scps.lan and it says dynamic updates - secure only. Is that the right
spot to check this?
Then it is dynamic IF the main zone is dynamic. You might as well check
that but they likely are dynamic since DCPromo does that IF you let
DCPromo
setup the DNS.
Did you let DCPromo create the DNS or did you do it manually?
(If you did it manually then you likely didn't make it dynamic OR you
have it as a Secondary to the now missing Primary on your old server.)
Look at the Zone properties for scps.lan zone properties, and tell me what
TYPE of server it is, and if it is set to DYNAMIC updates allowed or not.
(Type: Primary, AD Integrated, Secondary, or unlikely a Stub.)
It is AD Integrated. Set to Secure Updates only.
Check that it is dynamic.
Check that all DCs can find the "primary" (Master) and register
themselves in that zone.
As a new domain. I migrated data with a thumbdrive since there was soI 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.
little.
Did you setup DNS yourself or just let the DCPromo do that?
I let the wizard set it up.
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?
Run NetDiag /Fix (again after each change).
Then check (each time) DCDiag /c /d tell you now?
You should always send DCDiag to a text file and open it in a text editor
so
that you can easily search for FAIL and WARN messages.
Yes, I have been dumping these to a text file and reading them and copy
pasting the information form them.
Thanks.
.
- Follow-Ups:
- Re: DCDiag GUID Error
- From: Herb Martin
- Re: DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- References:
- DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- From: Herb Martin
- Re: DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- From: Herb Martin
- Re: DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- From: Herb Martin
- Re: DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- From: Herb Martin
- Re: DCDiag GUID Error
- From: Thom Paine
- Re: DCDiag GUID Error
- From: Herb Martin
- DCDiag GUID Error
- Prev by Date: Re: DCDiag GUID Error
- Next by Date: Re: DCDiag GUID Error
- Previous by thread: Re: DCDiag GUID Error
- Next by thread: Re: DCDiag GUID Error
- Index(es):
Relevant Pages
|