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 cannot connect via RDP to a win2003 server. Terminal services say that they're started, but a netstat shows nothing to do with port 3389. Any ideas?

share|improve this question
Are you using the -a switch with Netstat? If not, it's only showing you active connections (vs. all listening). Are you testing RDP from the same subnet? – techie007 Apr 26 '10 at 15:46
I'm using the -an switch. I'm also testing on the same subnet. – direMonky Apr 26 '10 at 15:48
up vote 4 down vote accepted

Incoming RDC isn't enabled by default. You need to ensure that "enable remote desktop on this computer" is checked on the computer's properties dialogue. You also need to ensure that the firewall exception is turned on too (enabling the checkbox will add this if it is not present, but I don't think it selects it by default).

share|improve this answer
That was the problem. Thanks! – direMonky Apr 26 '10 at 16:32
Is there a possibility for any reasons(besides user intervention) for the "enable remote desktop on this computer" to be unchecked after a server restart? – sc_ray Feb 25 '11 at 16:36
@sc_ray: I've never seen that happen. Installing or changing 3rd party firewall or firewall management software might cause disruption, as may errant patches from Windows Update (but that will be something that is heavily tested before updates are released: it would be very embarrassing if they released an update that accidentally removed access to everyones remote servers! – David Spillett Feb 26 '11 at 1:32

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.