SailingNut
Active Member
Hi, I'm new here and a very novice server admin. (Calling myself an admin is a loose use of the word!)
I have a W2K8 server acting as a file server and AD controller.
It began locking up on me and I thought it was heat related on the CPU so I pulled the case open and put a large fan blowing directly into the case.
That seemed to stop the lockups but the server seemed really slow.
A few days later the server began locking up again.
If I reboot the server (I have to power fail it once it is locked up) it will run for a little while (maybe 30 min) before locking up. However, I just figured out that even though it appears locked up, the TCP/IP stack is still working because it will respond to pings. That has the side effect of making PCs that are members of the domain to take a VERY long time to log in because the server is there from an IP perspective but the DC service is not there so the authentication has to time out.
Any ideas what might be going wrong? I really need to revive the server long enough to pull the files from it and then I'm going to get rid of having a DC (I really don't need it) and just set up a box to share the drive space. (I might re-use the hardware if that is not the cause of the problem.)
TIA for all help/advice/suggestions!
I have a W2K8 server acting as a file server and AD controller.
It began locking up on me and I thought it was heat related on the CPU so I pulled the case open and put a large fan blowing directly into the case.
That seemed to stop the lockups but the server seemed really slow.
A few days later the server began locking up again.
If I reboot the server (I have to power fail it once it is locked up) it will run for a little while (maybe 30 min) before locking up. However, I just figured out that even though it appears locked up, the TCP/IP stack is still working because it will respond to pings. That has the side effect of making PCs that are members of the domain to take a VERY long time to log in because the server is there from an IP perspective but the DC service is not there so the authentication has to time out.
Any ideas what might be going wrong? I really need to revive the server long enough to pull the files from it and then I'm going to get rid of having a DC (I really don't need it) and just set up a box to share the drive space. (I might re-use the hardware if that is not the cause of the problem.)
TIA for all help/advice/suggestions!
