I have a working DC, but my problem is that my old DC, (which crashed a while back) I am trying to do a DCPromo on the old server and I get an error message:
"The operation failed because:
Managing the network session with servername.domainname.com failed
The network path was not found. If this computer is connected to the network via a RAS connection, ensure that File and Printer Sharing for Microsoft Networks is enabled for that connection."
These two DCs are on the same LAN and no RAS connection.
My last option is to do a force demotion on that old server then use theNtdsutil.exe too on a working DC to do a metadata cleanup, would that work too?
Has anyone every ran across this problem? Thank you for your help!
Sport
There might be lot of reason for this errors. I will list some of them down
1) Check the Network Connectivity between 2 servers.
2) Check the Dns settings
3) Check the Network Credentials
and also try to follow the article listed below from Microsoft
http://support.microsoft.com/kb/332199
Syed
- Edited by Syed KhairuddinMVP Thursday, June 12, 2008 6:24 AM Edited
Especially, please pay attention to the DNS resolving on the DC. Verify the DNS server connectivity and the DNS settings on the old DC that needs to be demoted.
- Can the old DC access the shared folders on another DC?
Run "new view servername" on the old DC to verify.
- Check whether the TCP/IP NetBIOS Helper service is started or not.
For further investigation, could you please search in the "DCPromoUI.log" (in '%systemroot%\debug\' folder ) for errors in that demotion attemption?
- Marked as answer by Laura ZhangMicrosoft employee, Moderator Friday, June 20, 2008 10:35 AM
Then on a remaining DC follow this kb to remove the removed server from AD
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
done.
Hi
Verify DNS and/or WINS settings on the NIC interface of the old DC.
When replacing a 2003SBS DC with a 2008R2 Std DC, I was stopped by "Managing the network session with <2008R2 FQDN> failed" when I tried to demote the 2003SBS server. Removing the contents of "%windir%\debug" with the exception of NetLogon.log, NtFrs_000#.log & PASSWD.LOG resolved the issue.
I got the idea from this apparently unrelated post: http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/3b3eaced-04ff-49f5-89df-597003d573aa - which showed up on my google search.
- Proposed as answer by AndrewWiggin Friday, December 07, 2012 11:54 PM
Was very surprised, but this solved my issue. Thanks for your post!