Remote Desktop

[Guest]

Hi,
I've got xp pro at home behind a Belkin wired/wireless router. I also have a
dynamic IP address. I've enable remote desktop at systems properties.
Internally, I can access the host and the applications, but outside I can't
get in. The error I get from work is
"The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be tto busy to accept new
connections."
Thansk

 

[Robert L [MS-MVP]]

Have you opened the port 3389 on the router? this troubleshooting may help,

Troubleshooting terminal server issues When trying to access TS (administration mode), you may get this message: "The client could not connect to the remote computer. Remote connections might not ...
www.chicagotech.net/troubleshootingts.htm


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
Hi,
I've got xp pro at home behind a Belkin wired/wireless router. I also have a
dynamic IP address. I've enable remote desktop at systems properties.
Internally, I can access the host and the applications, but outside I can't
get in. The error I get from work is
"The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be tto busy to accept new
connections."
Thansk

 

[Sooner Al [MVP]]

In addition to Bob's advice you can use a service like No-IP.com to call your home PC from a remote location...

http://theillustratednetwork.mvps.o...ktopSetupandTroubleshooting.html#Call_Schemes

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


Have you opened the port 3389 on the router? this troubleshooting may help,

Troubleshooting terminal server issues When trying to access TS (administration mode), you may get this message: "The client could not connect to the remote computer. Remote connections might not ...
www.chicagotech.net/troubleshootingts.htm


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
Hi,
I've got xp pro at home behind a Belkin wired/wireless router. I also have a
dynamic IP address. I've enable remote desktop at systems properties.
Internally, I can access the host and the applications, but outside I can't
get in. The error I get from work is
"The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be tto busy to accept new
connections."
Thansk

 

[Guest]

I will try it out tonight.

If I had a static IP, would I have to go through with this extra step?
Thanks.

 

[Sooner Al [MVP]]

You mean a static IP from your ISP? If so, then no. Keep in mind the
No-IP.com service is *FREE*... I use it and like it very much...

You do need a static IP for the PC on your LAN in order for port forwarding
through your router to work properly...

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

 

[Guest]

Hi,
I've tried the following
1) Use No-IP.com because I have a dynamic IP address. Typed in
name.no-ip.org. The error was the same.
2) I have gone to http://www.ChicagoTech.net for troubleshooting help
(http://www.chicagotech.net/remoteissues/rdc2.htm). There suggestion was
related to Norton and MacAfee which I don't have installed.
3) I went to http://www.HowToNetworking.com. This website did not have a
solution to the problem. Basically try connecting at a later time or contact
the server admin.
4) Port forwarded 3389 to the server IP address - No luck.

This might give you a hint. I went into the security log of the router and
it stated that the "RoS connection" was refused.
Any feedback would be appreciated.
Thanks

 

[Sooner Al [MVP]]

Well if you can connect locally from another PC over your local LAN then it
comes down to either an addressing error, a port forwarding issue or your
ISP is blocking the incoming RDP traffic which is unlikely.

On the PC you want to remotely control what happens if you go to the
http://www.canyouseeme.org site and run the test on TCP Port 3389?

There is logging help on this page...

http://theillustratednetwork.mvps.o...teDesktopSetupandTroubleshooting.html#Logging

What kind of broadband ISP do you use, ie. cable or DSL? If its DSL its
possible the DSL modem is also a router and either needs to be put into a
bridge mode or you need to setup port forwarding in 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...

 

[Guest]

Hi,
I've gone to http://www.canyouseeme.org on the remote computer and it can
see port 3389.

I've also typed in netstat -a and 3389 is listening.

I have DSL. Not sure if the modem is actually a router. I will look into it.

As for port forwarding in my router (Belkin), I've typed in 3389 for the
ports and typed in the IP address of the PC to be accessed.

What is RoS connection refused mean? I went into the router security log and
that's what was stated.

 

[Sooner Al [MVP]]

If the canyouseeme.org test passes then it may come down to an addressing
issue. Are you sure your calling the correct public IP from the remote PC?
Go to http://whatismyip.com and get your public IP. Use that to call from a
remote location. Note that if your ISP assigns you a dynamic IP the IP may
change over the course of the day or week or month or etc...

I suppose you could have some weird MTU issue. I don't use DSL so I really
can't help with that... Maybe someone else can...

I have absolutely no idea what that "RoS" error means. Perhaps you need to
contact Belkin for help with 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...

 

[Sooner Al [MVP]]

One other thought... Are you running any personal firewall software on that
PC? If so its possible the firewall is configured to only allow Remote
Desktop access from your local LAN versus any IP on the public internet. I
know I can configure the XP SP2 Windows Firewall like that and in fact do
that, ie. limit Remote Desktop access to specific IP addresses...

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

 

[Guest]

Hi,

I am having exactly the same issue, but with Cable. I have a Belkin
Wireless router that I have set up to forward port 3389 to the IP address I
desire. I also run Checkpoint Firewall, and have set that up to allow access
on port 3389 in all areas. I can see port 3389 on www.canyouseeme.org .

Any help would be greatly appreciated!

 

[capilson]

Hi,

I am having exactly the same issue, but with Cable. I have a Belkin
Wireless router that I have set up to forward port 3389 to the IP address I
desire. I also run Checkpoint Firewall, and have set that up to allow access
on port 3389 in all areas. I can see port 3389 on www.canyouseeme.org .

Any help would be greatly appreciated!


-Andrew

 

[capilson]

Hi,

I am having exactly the same issue, but with Cable. I have a Belkin
Wireless router that I have set up to forward port 3389 to the IP address I
desire. I also run Checkpoint Firewall, and have set that up to allow access
on port 3389 in all areas. I can see port 3389 on www.canyouseeme.org .

Any help would be greatly appreciated!

Since you are behind a router make sure that your local IP address to
the computer you are attempting to connect to isn't changing. If so,
assign it a permanent address such as: 192.168.0.5 Also make sure that
when you open your port 3389 on the router, it is checked and applied
to the IP address of your local computer. Also, may want to check
windows firewall and make sure that it isn't blocking the 3389 port.
When you are outside of your lan you will type in the IP address from
your ISP plus the port, so it would look something like
24.87.25.99:3389, and on the lan 192.168.0.5:3389. I also use NO-IP and
it works great. Hope this helps.

-Andrew

 

[sbtiti]

You could have some problem with the client you are using. Can that client
access other remote hosts? Can other clients access from the Internet the
host you cannot access?