After restore from Ghost image, Active Directory naming information cannot be located.

  • Thread starter Thread starter Joe M
  • Start date Start date
J

Joe M

After I restore a Windows 2k domain controller from a Norton ghost image.
Everything works fine, except for Active Directory. Active Directory on this
Domain controller no longer works, it keep on giving error " Naming
information cannot be located because: The target principal name is
incorrect. Contact your system administrator to verify that your domain is
properly configured and is currently online". How do I restore Active
Directory and it's consistency on this Domain Controller? Thanks
 
Furthermore because previously before the Crashed it was a Domain Controller
with Active Directory installed. Because of this the DC cannot be renamed or
get out of a domain and join a workgroup..
 
In
Joe M said:
Furthermore because previously before the Crashed it was a Domain
Controller with Active Directory installed. Because of this the DC
cannot be renamed or get out of a domain and join a workgroup..
Click to expand...


The only reason you would get "Naming info cannot be located...", is because
it can't find it in DNS. Usually happens when an admin decides to use their
ISP's DNS server in IP properties, which is a complete NO-NO in AD. Point to
your internal DNS, then recommended to configure a forwarder for efficient
Internet resolution.

So you didn't give us enough info to figure this out...

How old is the Ghost image?
Are the DNS settings configured correctly?
Have they been changed since creating the image?
Is DNS on this server?
Is it only pointing to itself if this is the case?
Are there other DCs that are part of this domain?
If so, is DNS on them?

Maybe simply pointing to itself for DNS only, then do this:
delete the system32\config\netlogon.dns and netlogon.dnb files
ipconfig /registerdns
net start netlogon
net stop netlogon

Hope that helps...


--
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
 
Windows 2003 AD

Dear Ace:

I cannot thank you enough for saving my life today due to your article.

I needed to change the configuration of the drives, so i took a "Symantec System Recovery" image and destroyed the drives, then after recreating in the way i wanted, i restored the images.

However to my deathly surprise the AD stopped! **** i did not even use my VM Machine to take AD backup and i had killed off the secondary AD also. So i had to get this to work.

I did exactly what you said and 100% it was DNS trouble. I deleted the two files and then started and stopped the net logon its working fine.

Can you tell me why this happend on the first place? i would like to understand a bit more.

Also if you live in london, then i owe you Pint, would like to meet with you.
 
Back
Top