Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a W2K3 server that every time an update restart the server, at boot the tcp/ip stack gets corrupted.

This makes the server unable to do any kind of networking, and when i issue an

 ipconfig 

on a Command Window, the result is empty. to solve this problem i have to issue the following command and restart the server:

 netsh int ip reset <logfile>

This is causing a full network outage, because almost all services depends on the Domain Controller. when the server restarts i have to configure again the tcp/ip settings.

Another question regarding this issue is why the clients and Applications do not use the secondary domain controller, that is suposed to take over when the primary one fails?.

here are the FSMO roles assignations, SSCZDC01 is the server that fails>

dsquery server -hasfsmo rid
"CN=SSCZDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
XXXXXXXXXX,DC=com"  

dsquery server -hasfsmo pdc
"CN=SSCZDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
XXXXXXXXXX,DC=com"

dsquery server -hasfsmo name
"CN=SSCZDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
XXXXXXXXXX,DC=com"

dsquery server -hasfsmo schema
"CN=SSCZDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
XXXXXXXXXX,DC=com"  

dsquery server -hasfsmo infr  
"CN=SSCZDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=
enserbic,DC=com"

any insights or comments would be very appreciated, because i'm lost regarding the possible origin of this problem.

thanks very much for your time

share|improve this question
    
BTW, i have Done a full malware scan, and there were not any threats. –  Hugo Garcia Nov 11 '10 at 15:38

2 Answers 2

up vote 3 down vote accepted

Have you done a recent virus scan with an up to date virus scanner on the problem server? Is the server up to date on it's windows updates?

I'm guessing from your tags that your domain is a Windows 2003 active directory domain. I also take it that you have a single domain forest with two DCs.

It sounds like this server is the owner of all the FSMO roles on your domain (each of the five FSMO roles can only be on one server at a time).

For info about FSMO roles: http://technet.microsoft.com/en-us/library/cc773108(WS.10).aspx

You can determine if your problem server holds the FSMO roles like so on the command prompt:

dsquery server -hasfsmo rid
dsquery server -hasfsmo pdc
dsquery server -hasfsmo name
dsquery server -hasfsmo schema
dsquery server -hasfsmo infr

If your problem server holds all the roles above, I would transfer the roles to your good DC, as per: http://technet.microsoft.com/en-us/library/cc781578(WS.10).aspx

This will probably solve the problems you get when the problem server drops out. Once you have transferred the roles, you can take the problem DC offline and do some diags on it, or as a last resort rebuild it.

share|improve this answer
    
+1 couldn't have answered this better myself. –  Kyle Nov 11 '10 at 13:59
    
Thanks very much, very informative. is there any way to have a high availability setup? like when one serves fails the other takes the roles automatically?, i have updated the questions with the corresponding server roles –  Hugo Garcia Nov 11 '10 at 14:03
    
Regarding the virus scan, i have just finished a new one, and there isn't any threats on this server. what else could cause this behavior? also the server is whit all the latest security and critical updates installed –  Hugo Garcia Nov 11 '10 at 15:40
    
Ok so your problem server has three of the FSMO roles (pdc emulator, schema master, naming master). You can transfer them to SSCZDC02 quite easily using the details in the second link I posted. Then as Shial said, i'd start by seeing if there are new NIC drivers for your server. Also check the system event log. If something looks odd, google the event ID. –  simon Nov 12 '10 at 22:01

Take a look at the network drivers and see if there are updated ones. It could be a bug in them that triggers it.

Do you see anything in the event logs during the restart? there probably isn't especially if it occurs before the logging service gets started but you never know.

We had something similar to a couple of laptops once where it completely lost the network and it would occur (eventually like a month later) even after a reinstall. Finally figured out since it was a group of them with sequential serial numbers that it was bad components that were somehow screwing with the OS.

share|improve this answer
    
Interesting note on the Laptops hardware failiure, could it be a hardware failiure of the network card?. lets find out ill replace the NIC an will post an uptade. –  Hugo Garcia Nov 12 '10 at 18:39

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.