>> 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.)
>
We started from scratch. So basically we set up the new lan with the new
server and manually input the users again. I guess you could say we just
deployed this lan for the first time. I have the old server sitting here
just for reference.
>>> 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)?
>
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?
> 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?
>
As a new domain. I migrated data with a thumbdrive since there was so
little.
>>> 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
Bookmarks