Discussion Locked

Salvaging a DC.....

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Our main DC at site1 went offline for some reason. I rebooted but it has stalled at "creating network connections"...been that way for 2 days.
I have 4 other sites that are having logon errors now. They can't find the domain. DC1 was the role master etc. Any ideas to fix it?
I can possibly seize the roles at another site but 3 sites can't see site 1, so that maybe will put site 1 out of commission for good. I could try a restore of some sort at site 1 but that has never worked well for me.
help

7 replies

by cul8rm8e

Reboot the server,hit F8 and try using (last known good configuration) ifthat dont work post back here!

by whatme?

Tried that ... just boots up at stays at "opening network connections"
Als in safe mode, did a check on capacity (only 4 gig out of 8gig), error checking, defrag and reboot.

by timwalsh

Wneh you say 3 sites can't see site 1, do you mean they can't "see" the site 1 DC, or they can't "see" anything in site 1? What about the fourth site?

The first order of priority should be to get the other sites working. Go ahead and sieze the FSMO roles from one of the other DCs. You will probably need to adjust DNS and point the clients at site 1 to the new DNS server (assuming the site 1 DC was also the primary DNS server).

NOTE: If you go this route (siezing the FSMO roles vs. gracefully transferring them), you MUST remove the site 1 DC from the network. It should not be re-admitted to the domain until you have run dcpromo, and/or otherwise reconstructed it.

Once you get everyone so that they can log-on, you can try and troubleshoot the site 1 DC. You might consider constructing a temporary DC for site 1 while you fix the original.

by whatme?

none of the other 4th sites can log in correctly (unknown domain, unknown user account etc) They eventually do but with a lot of errors. There was a DC w/ad /global catalogue ,dns, dhcp at each site, with site 1 being the role master etc. I can't terminal service into any of the other dcs. I can ping all of them except site 1
If I seize the role at site 2 say, I am worried that I may not be able to get from site 1 to site 2 again when I rebuild. I have always had problems going across separate subnets in different geograhic regions . Unfortunately, I can't build another dc at site 2 and move it over.... a distance of 1500 miles. Reply again, your close... thanks

by magetower

There may be a problem with the NIC drivers or NIC. Can you put another one in the server?

You could also try disabling the NIC while in safe mode and then reboot. You may get a bunch of errors about server services not starting but it may get you back to the desktop.

Can you see any errors on the event logs?

by whatme?

No, that was not it. Thanks anyway. The server finally gave up and I got the blue screen. May be memory or other hardware error. Problem is, I am not physically there so I removed it from the system. I am still heving connection problems with the other sites now.... the big one is.. not recognizing the new DC at times. My DC group policy is screwed up again also. I am now getting my 1000 and 1002 errors every 5 minutes. I am still working on that

This discussion is closed to new replies.