Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am unable to remote desktop to our Windows Storage Server 2003 R2 machine.

There are a few people about with similar issues but no answers around. Symantec End Point is installed but no network protection.

Using rdesktop in Linux I receive:

ERROR: send: Connection reset by peer
ERROR: Connection closed

Where the "PDU XX" number changes on each connection.

In windows using the latest mstsc I receive:

The connection was lost due to a network error. Try connecting again. 
If the problem persists, contact your network Administrator.

Any ideas?

share|improve this question
Have you tried turning Symantec completely off temporarily? – Wesley Oct 30 '09 at 15:19
unfortunately not something I can try at the moment but will asap – Antitribu Oct 30 '09 at 16:00
Are there any errors in the Application or System Event Logs? – Sim Nov 21 '09 at 23:47

Drivers. Check for the latest drivers, DISABLE TCP OFFLOADING / CHIMNEY. Some drivers around are crappy like hell.

share|improve this answer
I've thought along similar lines for another issue, I'll try this here, thanks! – Antitribu Sep 17 '10 at 8:48

First try remoting in with a windows machine using the latest RDP client (found in windows update or available here). If that doesn't work I'd remove symantec endpoint protection (on a side note I'm suprised endpoint protection actually installed at all on storage server as storage server is missing alot of core windows functionality but it's good to note that it apparently can be installed)

share|improve this answer
sorry; should have been clearer. MSTSC == RDP client, and unfortunately the comments regarding me been unable to stop endpoint at this point are still true. – Antitribu Nov 2 '09 at 9:22

is port 3389 open? If you have nmap open you can scan the machine, but if not you can run telnet machinename 3389 from within cmd.exe. If it's not open, it'll say "Could not open connection to machinename on port 3389: Connection Failed", but if successful it'll give you a blank window.

share|improve this answer
Port 3389 is open, it allows me to connect to RDP, just not see anything. – Antitribu Sep 17 '10 at 8:46

It sounds like your server ports are being closed by something. Check all your security settings.

share|improve this answer

Your Answer


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.