I keep loosing Remote Desktop with Server 2003 on Dell servers
On all of our Dell servers (about 300 1650's through to 2950 III's. Windows NT to 64-bit Windows 2003 R2) we have Remote Desktop enabled. On our Windows 2003 servers, we sometime lose Remote Desktop. Here is the error we get:
The client could not establish a connection to the remote computer.
Reasons:
1) Remote connections might not be enabled
2) Maximum number of connections exceeded
3) Network error
Generally, we reboot the server and it comes back. While we are getting the error, if we go right on the server itself, we cannot even Remote Desktop to itself. I have an open call with Microsoft on this. They are saying it's corruption within Terminal services. They want me to do a whole lot of things to try to fix it (Replace DLL's, change registry keys, boot into safe mode, etc).
Here's what I've established:
1) It only happens on Windows 2003. Not Windows 2000
2) It happens on SP1, SP2, completly patched servers, and servers that haven't been patched in a year.
3) It has happened on all Dell models at one time or another (1650, 1750, 1850, 1950, 1855, 6850, 2950).
4) It happens on 64-bit and 32-bit.
5) It's never happened on our IBM servers or virtual server (Sorry Dell :()
6) We have more virtual servers than physical servers.
7) It happens on servers with and without DRAC cards.
8) The only thing in common is that all the servers were setup with the Dell setup CD. We don't use images.
Has anybody else seen this? Microsoft tells us that we're the only people that this has ever happened to.
Use the pathping command to see if you have packet loss. Needs to be done from the internal network (server) to an external IP best to one of the remotes) and the reverse. Generally a pathping to a website which does not restrict packet size is a fair test, eg
If you have a few percent loss through all routers/gateway/NICs, it is acceptable (approx 5%). If more, devices along the way are dropping too many packets.
Make sure your line speed/duplex setting is hard set, not auto, on both the NIC and switch port. Check the switch port the server is connected to for errors.
Message Edited by pcmeiners on 12-29-2007 07:03 AM
I'm hoping you've already checked this but when you can't get into the server via RDC, get on the console and open Terminal Server Manager. Just make sure there aren't already two sessions running but disconnected. I think you'd see a different error but just in case.
I assume you've already checked the Event Log as well. Other than that, I'd post to the Microsoft forum and see what they say.
It's Open Manage !!! If I uninstall it, Remote Desktop starts working again without even rebooting the server. This solution has worked on 3 servers so far. I haven't tried re-installing Open Manage to see if it breaks it again.
mike crowley
40 Posts
284
0
Posted December 29th, 2007 01:00