We help IT Professionals succeed at work.

Windows Server 2003 R2 keeps removing itself from domain

I have a Dell PowerEdge  R515 running Windows Server 2003 R2 (x86) with SP2 that keeps removing itself from the domain. All the firmware and drivers are up to date. There are no missing MS patches. I can reboot the server and it'll connect to the domain but after a few hours it'll disconnect again yet I can RDP to it and login as a local admin but not a domain admin.

I have tried removing it from the domain, removing the TCP/IP stack, disabling the NICs, deleted the machine in Active Directory, I even used the W2K3 R2 SP2 DVD to run the installer to Repair the OS. Once I rejoin it to the domain it'll connect but again fail after only a few hours.

Has anyone else encountered anything like this? What can I try doing?
Watch Question

Try doing an Msconfig and disabling all Non - Microsoft Services . See if any one of the Third-party Services is causing the issue .

To open msconfig , goto run type msconfig --> move to Services Tab --. Check the box at the bottom which says " Hide All Microsoft Services" and disable all services which you do not require .
Remember to enable Essential services which are important for your connectivity such as the Logmein , See if it resolves.

Do you see any errors written while it gets disconnect from the domain? I am doubting on some hardware, because of which it fails. Check the cluster and other logs if you get anything.


Here are some of the errors in the Event Log:

Event ID: 1053
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation). Group Policy processing aborted.

Event ID: 5719
This computer was not able to set up a secure session with a domain controller in domain (DOMAINNAME) due to the following: Not enough storage is available to process this command. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact you domain administrator.

The second error occurred when I tried to login as the Domain Administrator on the domain. There's plenty of storage on both the domain controller and this particular server so I'm not sure what storage it's referring to.


Disabling non-Microsoft services did not help by the way.


1. Check whether the server has enough space or not.

2. Since, windows 2003 can only support 2000 processor thread at a given point of time, check what application is running during the time, the error is reported. This can be the reason for EventID 1053, if space is not an issue.

3. Check the maxtokensize for the kerberosis:
Reference: http://support.microsoft.com/kb/935744/en-us

4.   Make sure that your internal DNS server is the server for the domain you are logging in to.

5. Verify the DNS Settings. This will occur if your DNS server is unable to resolve information about your domain.


1. The server has plenty of space, so that can't be the issue.

2. I stopped all Microsoft services in MSCONFIG and still have the issue. I also uninstalled ALL applications and continue to have the issue.

3. The DC is a W2K8 R2 server and this server is W2K3 R2 so this is not applicable.

4 & 5. DNS server and all DNS settings are correct. This is the only server in the environment with this issue.


I have to believe this issue is not related to the OS, but is somehow related to hardware or network somewhere. To rule out the OS I am rebuilding the server completely using Sysprep to use another SID as well, just in case.

okay. Share if doing that solves the problem.


This wasn't exactly the resolution but it ended up being a third party application that removed the server from the domain.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.