Re: Cannot Remote Desktop to home PC after installing XP SP3

Is the PC listening on the rdp port? When you type "netstat -an"
(without the quotes), do you see something like:

Prot. Local address Ext. address Status
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

or whatever port you have configured for rdp?

Are there any Events in the EventLog on the PC which can't be
reached?
Are you connecting from a client which runs rdp 6.x? What are the
settings under Advanced - server authentication?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?RXZhbiBLYXll?= <Evan Kaye@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 18 aug 2008 in
microsoft.public.windows.terminal_services:

I know Remote Desktop isn't strictly speaking "Terminal
Services", but it seemed to be the closest match. After
installing Windows XP Service Pack 3 on my home system, I cannot
connect to it by Remote Desktop. The client seems to be trying
to connect for a moment, and then automatically cancels less
than a second later, with no error message (whereas I DO get an
error if I try to connect to the wrong machine or port). I have
tried connecting from outside my home network, from another PC
on my network over the router's WAN interface, from the other PC
directly to the local network address, and from the PC in
question itself to the WAN interface (it won't let me try to
connect to its own local address); same result every time.
Remote Desktop worked fine before I installed SP3.

I have rebooted my system, disabled and re-enabled Remote
Desktop in System Properties, and added accounts explicitly to
those allowed to logon over Terminal Services using secpol.msc
(they were already members of Remote Desktop Users). I used to
connect over a non-standard port for security reasons, which was
mapped to 3389 by the router. I changed it so the non-standard
port is passed straight through the router, and changed the PC's
RDP port in the registry; issue unchanged. Windows Firewall was
and is disabled.

Using Wireshark, I can confirm that the RDP client packets are
reaching the serving PC. If I post the capture here, will
someone be able to look into it and tell me what's wrong?
.

Relevant Pages

  • Re: Cannot Remote Desktop to home PC after installing XP SP3
    ... Remote Desktop unless a registry tweak is made. ... Are you connecting from a client which runs rdp 6.x? ... machine or port). ...
    (microsoft.public.windows.terminal_services)
  • Re: REMOTE DESKTOP NOT WORKING ANY LONGER PLEASE HELP!
    ... If the Vista machine is listening for incoming rdp traffic (on ... whatever port you configure), it sounds to me as a firewall issue. ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP-TCP Listener Down State
    ... If the RDP is not listening on port 3389 or is reported as down there are ... RDP listen or is it reported as down? ... control if the port is really 3389. ... Reboot Server. ...
    (microsoft.public.windows.terminal_services)
  • Re: XP Remote Desktop and SSH
    ... TELNET is port 23 ... the Remote Desktop XP RDP client is port 3389 but that CAN be changed in the ...
    (microsoft.public.windowsxp.security_admin)
  • Re: TS service not listening on port 3389
    ... If the RDP is not listening on port 3389 there are several issues that could ... RDP listen or is it reported as down? ... control if the port is really 3389. ... Reboot Server. ...
    (microsoft.public.windows.terminal_services)
Quantcast