Remote Desktop Error Message

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

Guest

Here is my setup...
2 win xp pro sp 2 computers in two different locations.
1 computer setup as host and is connected to the internet via cable modem
1 computer trying to become the client also connected to the internet via
cable modem.

Using another computer as the client on the same local network as the host -
remote desktop works fine.

Used "Open Port Check tool" as suggested by another poster, found out that
according to that port 3389 is being listened to by my cable ISP At the same
time, the "Open Port Check Tool" also gave me an IP address.

So - on the client computer I run "remote connection"
for computer I type in IP address from "Open Port Check Tool" and nothing
entered for the Domain - and I get the following error message----

"The client could not connect to the remote coputer. Remote Connections
might not be enabled or the compter might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator."

I tried entering the login and password as well before hitting "connect" but
the same error message comes up.

If the client computer is hooked into a router before the cable modem, would
this create this issue. If so - what can I do to the client router to allow
this connection

I must be missing something simple. I have tried making sure all antivirus
software is disabled on the client computer, windows firewall disabled on
client computer and I still get the same message. I know I must be getting
close. I got the remote desktop to work on the local LAN so I think it must
be a setting I am not seeing.

Please - some assistance would be appreciated.

Thank you,
Todd
 
Can you telnet port 3389? If not, make sure the port 3389 point to the host computer.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Here is my setup...
2 win xp pro sp 2 computers in two different locations.
1 computer setup as host and is connected to the internet via cable modem
1 computer trying to become the client also connected to the internet via
cable modem.

Using another computer as the client on the same local network as the host -
remote desktop works fine.

Used "Open Port Check tool" as suggested by another poster, found out that
according to that port 3389 is being listened to by my cable ISP At the same
time, the "Open Port Check Tool" also gave me an IP address.

So - on the client computer I run "remote connection"
for computer I type in IP address from "Open Port Check Tool" and nothing
entered for the Domain - and I get the following error message----

"The client could not connect to the remote coputer. Remote Connections
might not be enabled or the compter might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator."

I tried entering the login and password as well before hitting "connect" but
the same error message comes up.

If the client computer is hooked into a router before the cable modem, would
this create this issue. If so - what can I do to the client router to allow
this connection

I must be missing something simple. I have tried making sure all antivirus
software is disabled on the client computer, windows firewall disabled on
client computer and I still get the same message. I know I must be getting
close. I got the remote desktop to work on the local LAN so I think it must
be a setting I am not seeing.

Please - some assistance would be appreciated.

Thank you,
Todd
 
See this page for troubleshooting help...

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

Make sure you call using the public IP of the remote PC or the firewall. If
it works over the local LAN from another PC then it comes down to an
addressing issue or a port not being opened on a firewall/router.

--

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