Unsolved
This post is more than 5 years old
19 Posts
0
4029
December 21st, 2011 08:00
PE2950 Random reboot and No Remote Desktop access once it comes back up
Hello,
My company has been experiencing a strange problem recently with two of our servers. We have two terminal servers that are running 24x7, one is a PE2950 and the other a PET710. Both of them have been experiencing random crashes/reboots and that is an ongoing problem. We reformatted the PE2950 about 2 months ago and the random crashes stopped until just last night. We got a random crash and when the server came back up, it refused to allow remote desktop connections. The server was up and you could Remote Desktop to it and get to the point where it asks for credentials but then it would deny you with a very generic error message, something like "Remote desktop connection failed".
Anyways, I found a way to fix this was to take the server off of our domain, reboot, put it back on the domain, and reboot. Then Remote desktop worked fine.
Can anyone provide insight into why this is happening? We have the servers set to reboot in the event of crash so that in case they go down they can be back up within 10-15 minutes for our workers to use. However, if they are refusing RDP connections upon rebooting that isn't doing much good.
Also, no dumps or event viewer help with the crash. All Remote settings seem correct upon the reboot.
Our T710 experienced this Remote Desktop problem about a month ago and thats when i figured out the domain fix, now our PE2950 is experiencing it.
MikeLApprise
19 Posts
0
December 22nd, 2011 06:00
Thanks for the response pcmeiners,
It's Windows Server 2008 32-bit, No TS gateway we are using 3389, We have a central McAfee Anti Virus system that monitors this system as well as all of our others. I haven't run any intensive scans other than constant monitoring of our entire company's AV health. I just launched a full scan on that machine now and I'll see if that comes back with anything.
I'm not sure what DcDiag /v and NetDiag /v are so I have not run those
thanks
pcmeiners
6 Operator
•
1.8K Posts
0
December 22nd, 2011 06:00
Windows 2003 or 2008?
Are all hardware firmwares/drivers upto date?
Do you have a TS gateway or are you using port 3389?
Have you run multiple virus scanners on the server, malwarebytes, and multiple root kit scanners?
Have you run DcDiag /v and NetDiag /v ?
pcmeiners
6 Operator
•
1.8K Posts
0
December 22nd, 2011 07:00
To insure there is no virus/malware/keyloggers/rootkits you need to scan the machines with more then Mcaffee. Google "free virus scan" and google root kit removal.
DcDiag.exe is used to extensible test AD health on the servers, NetDiag.exe does the same for the network interface, both should be run on all servers in an AD environment after initial setup and if issues occur. NetDiag.exe is not included on the 2008 disk, but the version from Win 2003 works. After you run these correct all errors found.