asked on
Windows 2008 R2 domain controller
Two Win2K8R2 DC’s with temp names were added (migration) to W2K3 network w/2 existing DC’s, tested and checked according MS recommendations.
During renaming something went wrong with one of the DC’s:
1. The DC exists in ADUC / Domain Controllers with the new name.
2. In AD Sites and Services the temp name still appears, replication to the second Win2K8R2 DC fails with error msg: “The RPC server unavailable. This condition may be caused by DNS lookup problem”.
Please help resolve the problem keeping in mind that most of MS hints were unsuccessfully tried.
Are the two new DC’s all the same?
Thank you.
During renaming something went wrong with one of the DC’s:
1. The DC exists in ADUC / Domain Controllers with the new name.
2. In AD Sites and Services the temp name still appears, replication to the second Win2K8R2 DC fails with error msg: “The RPC server unavailable. This condition may be caused by DNS lookup problem”.
Please help resolve the problem keeping in mind that most of MS hints were unsuccessfully tried.
Are the two new DC’s all the same?
Thank you.
Windows Server 2008Active Directory
Last Comment
cohhelp
You were renaming the DCs? To the old DCs name?
Run dcdiag post results.
Run dcdiag post results.
ASKER
Everything was working fine before the rename! Yes , I sow same article about troubleshooting error 1722 on TechNet.
Yes, I was renaming the DC's to the old (2003) names. Attaching thedcdiag on "bad" dcm1.log
Thank you.
Yes, I was renaming the DC's to the old (2003) names. Attaching thedcdiag on "bad" dcm1.log
Thank you.
ASKER
If both W2k8R2 DC's identical, maybe the easy way just to rebuild the "fallen" one? (the old W2k3 DC's are not demoted and online)
The 2003 DCs are NOT demoted? Did you rename those DCs to something else?
Run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix
Restart netlogon service
If this doesn't change anything then a demote of the new server would be quick and easy.
Run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix
Restart netlogon service
If this doesn't change anything then a demote of the new server would be quick and easy.
ASKER
Yes, the 2003 DC's were renamed to "nameold".
Already ran ipconfig /flushdns - didn't make changes.
Will follow your recommendations.
Thanks.
Already ran ipconfig /flushdns - didn't make changes.
Will follow your recommendations.
Thanks.
ASKER
"Windows could not start the Netlogon service on Local Computer.
Error 0xc0000064; 0xc0000064"
Error 0xc0000064; 0xc0000064"
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
It seems I found a GUI way: http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
ASKER
The "sick" server constantly logs Event ID: 1055
Yeah I don't think the GUI works unless you are running Windows 2008 Server domain level
ASKER
Thx
http://support.microsoft.com/kb/2102154?wa=wsignin1.0
Thanks
Mike