Error trying to connect pc

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

Guest

Hi all,

Running XP pro at home with firewall off, and Allow Remote Users to connect option is checked.
Also running Linksys Router with port forward option is set to the correct machine and using
correct port number. My work machine is XP pro and I'm trying to connect and I get this error message.
"Client could not connect to the remote computer"

please help

Gerry Viator
 
Trying to connect from...the local LAN?...a remote location?

To test over the local LAN from another local PC use the local LAN IP of the target PC... You can't
call from a local PC using the public IP of the router to test from the local LAN...

To access over the public internet use the ISP assigned IP of the Linksys router? If your sure of
the public IP, run this telnet test to see if you can pinpoint a possible cause......ie. is
something blocking TCP Port 3389 for example.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

--
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 get that message typically the initial time I try to
connect. If I try again, it connects fine. It seems like
the first attempt seems to wake-up the remote system, the
the 2nd attempt works.

- Dave
-----Original Message-----
Hi all,

Running XP pro at home with firewall off, and Allow
Click to expand...
Remote Users to connect option is checked.
Also running Linksys Router with port forward option is
Click to expand...
set to the correct machine and using
correct port number. My work machine is XP pro and I'm
Click to expand...
trying to connect and I get this error message.
 
I get connect failed.

thanks
Gerry




Sooner Al said:
Trying to connect from...the local LAN?...a remote location?

To test over the local LAN from another local PC use the local LAN IP of the target PC... You can't
call from a local PC using the public IP of the router to test from the local LAN...

To access over the public internet use the ISP assigned IP of the Linksys router? If your sure of
the public IP, run this telnet test to see if you can pinpoint a possible cause......ie. is
something blocking TCP Port 3389 for example.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

--
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...

and I get this error
message.
Click to expand...
 
thats not it

thanks
Gerry




DaveB said:
I get that message typically the initial time I try to
connect. If I try again, it connects fine. It seems like
the first attempt seems to wake-up the remote system, the
the 2nd attempt works.

- Dave
Remote Users to connect option is checked.
set to the correct machine and using
trying to connect and I get this error message.
Click to expand...
 
So where did you test from?

If you got the fail message while testing over the public internet from a remote location then
something is blocking TCP Port 3389, ie. your router or your ISP.

If you fail testing on your local LAN make sure Remote Desktop is enabled on the host PC and
listening...

Have you checked to see if RD is actually listening on TCP Port 3389 on the host PC? On the host XP
Pro machine go to "Start -> Run", type 'cmd' (without the quotes). At the command line type the
command 'netstat -a' (without the quotes). Look for a line like this.

TCP <Your PC>:3389 <Your PC>:0 LISTENING

For example on my XP Pro desktop, Ashtabula, the line looks like this using the default port 3389.

TCP ashtabula:3389 ashtabula:0 LISTENING

The line should be present...If the Remote Desktop host is not running, then you will not see a line
like that and you will not be able to connect. If you run services.msc on the target machine is the
"Terminal Services" service started? Also, check the Event log to see if anything stands out when
you try to connect.

--
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...
 
Thanks for your help,

I have a Linksys router and I added the machines ip address to the port
forwarding option
using port 3389 and selecting UDP and TCP, And I powered off the router and
turned it back on.

Remote Desktop is Enabled on that machine, I can Remote from my home to
work.
But, not the other way like I have mentioned.

When I ran that test with telnet I typed this in a command window from my
work XP machine:
telnet 169.169.169.169 3389

169.169.169.169 = my routers IP address from ISP

How do I check a router to see if it's listening?

Thanks again for your help

Gerry
 
Well, its possible your work is blocking TCP Port 3389 outbound. I would ask the local work network
administrator about that. You can also test that theory by going over to a friends house, or some
remote location other than work, and seeing if you can RD into your home PC from there. If you can,
that pretty much tells you something on the work end is blocking the traffic.

What model Linksys router do you have? Are you running the latest firmware? Its also possible that
dropping back to an earlier version of the firmware may help.

--
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