Windows Server 2003 Reinstall and backup restore - Browsing by name gives 'server is not accessible. Login Failure: The target account name is incorrect

I have a file server at one of our sites that has the file server and a domain controller. I have recently rebuilt the server and have restored the files from Ultrabac backup. Since this was a rebuilt i made sure to reset the file server's computer account and then re-add it back to the domain. AFter it was added back to the domain i performed a 'dcpromo' to promote it to a domain controller because i would like to remove the one already in place (old and out of support). Dcpromo went through fine. I am able to connect to this computer via IP and even ping by name and IP, just unable to network browse by name. I've looked this up and saw that some people had to perform a dcpromo /forceremoval to get this fixed, however, i am several states away and it may be difficult to walk someone through re-adding it to the network because this also put the server in a workgroup, correct? Any options i have to resolve this that dont involve putting in a workgroup? Thanks very much experts!!
Frank FerrerIT ManagerAsked:
Who is Participating?
 
Frank FerrerIT ManagerAuthor Commented:
i removed AD with dcpromo. Then checked with NTDSUTIL. No issues there. I then put into a workgroup (I used Pc-Duo to connect to the computer via IP in case DNS came into play and didn't want to be disconnected using something like remote desktop). After putting into a workgroup i immediately added it back to the domain (without restarting after being put into a workgroup) and now everything works fine. Sorry if that was a little confusing but i think reinstalling the file server from scratch and the resetting the account in AD messed something up, but removing from the network and re-adding solved it. Thanks for your help
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
You have to run metadata cleanup for that failed DC, /forceremoval is to use for decommission DC if you cannot do that in regular mode.

Please run ntdsutil and follow an article on my blog for metadata cleanup at
http://kpytko.wordpress.com/2011/08/29/metadata-cleanup-for-broken-domain-controller/

then repromote it as DC again

Regards,
Krzysztof
0
 
Frank FerrerIT ManagerAuthor Commented:
Thanks Krzysztof!
Does it make a difference that this was not a domain controller when i did the restore? I promoted it after the restore (bringing it back up as a file server). What  i've done is remove active directory from it by doing a dcpromo after i got the message above. I guess i have't needed to do a 'forceremoval' since it was not a failed DC...just a file server that i restored by re-installing the OS and restoring data folders. Since the demotion worked successfully wouldn't i just wait for AD to replicate the changes to the other sites? Do I need to have it in a workgroup before i run the metada cleanup?
0
 
Frank FerrerIT ManagerAuthor Commented:
quick update. I ran ntdsutil and the server is not listed there. I think this is because the issue was because i rebuilt the 'file' server from scratch, reset the computer account in AD, then re-added it to the domain....prior to promoting it to a domain controller. Promotion/demotion works fine, i am thinking that maybe i need to remove it from the domain and then re-add? I may try that.
0
 
Frank FerrerIT ManagerAuthor Commented:
i think i had to work in out in my head and my conclusion was correct. Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.