Testing Remote Desktop Connection

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I use to connect my home XPP computer using remote desktop connections, but
now I can't. I have gone thru every step by step configuration instruction
that I can find including the article
http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx.
I have tested the connection on the local LAN using the local IP address and
computer name. I tried using the Remote Desktop Connection and the Remote
Desktop Web Connection. Nothing seems to work. I definely have the "allow
users to connect...." selected on the host computer. I have added all the
users that I can. I always get the error "The client could not connect to
the remote computer." Is there some new security feature here that I am not
aware of? I have the firewall exceptions configured as per articles.
Thanks for any help as I am now to the frustration phase of this project.
 
This page has some troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

Are you saying that testing over the local LAN fails? Or is it failing when
you try to connect from a remote location?

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I am saying that testing over the local LAN fails. I haven't even got to
testing remotely thru my router. I have been through the troubleshooting
help page earlier with no luck. There has got to be a "gotcha" here
somewhere.
 
Is the Remote Desktop host PC listening on TCP Port 3389?

If not, is the Terminal Services service running? If not you need to start
it...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I have the sort of same problem. I have teh remote connection enabled.
terminal services are running.yet none of the machines in teh local network
are able to find it through remote connection
 
Any firewall software running on the Remote Desktop PC?

Some folks report NAV 2005 worm protection kills Remote Desktop on a PC.
Check to see if your running anything like that, that maybe causing the
problem.

Are you calling the correct static LAN IP?

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Iit does not work whetehr it is connected through a wirless ip or wired
ethernet ip. I also do not think i have nav2005 software. The sp2 firewall
says everything should be ok as far as remote connection is concerned.
 
So is the PC listening on TCP Port 3389?

If not, is the Terminal Services service running? If not you need to start
it...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I ran NETSTAT -a and it came back with results that the PC was listening to
Port 3389 as well as Port 51126 which is the one that I configured for my
desktop web connection as per instructions from
http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx.

Terminal Services status was "started".

I am definitely calling the correct static LAN IP. I tried both the IP
address and computer name.

I tried connecting with the firewalls turned off. I tried connecting with
the Norton Antispam shut down. I tried connecting with the Norton Antivirus
turned off. No success.

Just to make sure it wasn't just me, I set up a remote desktop connection
with a different host PC on my business LAN but using the same laptop as the
remote client. No problem. Connected on my first try. So it can't be a
problem with the client computer.

Do think something got corrupted on this host PC? Should I try reloading
any Windows components from my original XPP CD?

Still trying..... but running out of ideas.
 
Did you use the form http://IP_Address:Port/tsweb to call the PC?

What happens if you don't use the web method and only use the normal Remote
Desktop connectoid...can you connect?

What happens if you run the PortQry test? If the test reports a "Filtered"
result then there is a firewall issue on the Remote Desktop host.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I finally got back to the problem and ran portqry. I tested Port 3389 and
the result was "NOT LISTENING". I uninstalled Norton Antispam and turned off
the firewall and got the same results. Any suggestions? I am also running
Norton Antivirus but am running NAV on a PC that works.
 
The only thing I can suggest is Norton may be killing the connection. Have
you tried stopping Norton? Does Norton have worm protection turned on? I
don't happen to use the product so I can't give you further advice about
Norton, but something is obviously killing RDP since you get the not
listening condition from the PortQry test...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Well, we have made good progress. With your hints, I was able to
re-configure Norton and get TCP Ports 3389 and 51126 (my web site
identification port) to LISTEN. However, we aren't quite there yet. My
Remote Desktop Web Connection now seems to be working because when I launch
it, the connection screen comes up and this never happened when the ports
were NOT LISTENING. When I hit the Connect button, the screen blanks and
seems to be off trying to communicate with the host computer. However, after
about 30 seconds, I get the message from VBScript:Remote Desktop Disconnected
"The remote connection has timed-out. Please try connecting to the remote
computer again." I have tried with Norton auto-protect and internet worm
protection turned off with identical results.
 
Test using the normal RDP connectoid, not the web based method, just to see
if you can get a basic RDP link connected from another PC on your local LAN.
Over your local LAN make sure you use the local LAN IP of the desktop.

If you get that working, next test the normal RDP connectoid, not the web
based method, from a remote PC. Use the public IP of your router so you can
verify that TCP Port 3389 port forwarding is working correctly.

Its best to test one step at a time...as they say..."Patience is a
virtue"...:-)

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Sorry Al. I tried using the normal RDP connectoid over the local LAN and got
identical results. That is, I get the same timed out message. I do use the
local LAN IP of the desktop when trying to connect over local LAN and the
router IP when testing over the Internet. I was able to successfully connect
to another desktop on my work LAN using the same laptop as a client. So the
problem must be with the desktop (host) on my home network. If the ports are
listening and remote connections permitted is enabled, it is hard to imagine
what else it could be.

This is a tough one. I have been connecting to this host for over two years
without a problem and now all of a sudden it quicks working. I will keep
plunking away but will welcome any new hints. I am assuming that it quit
working when Norton worm protection was installed. However, this is the same
version of Norton that I have installed on my work computer and I didn't have
to do any special NAV configuration to get the RDP working.
 
The only thing I can suggest is to see if Norton had any support forums that
you might post this issue to or contact their customer support folks.

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Back
Top