RD Error - Works on local net but not internet ????

[Andre Uys]

I have a local PC that can connect to my Remote Desktop session, both hooked
to the same MS MN700 wireless router.

I use the PC Name instead of the IP, and it works great.

When I try and connect to the IP from a internet connected machine (my
laptop at work) I get the following error:
The Client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connection. 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.

Remote Desktop sharing has been enabled on the host.
The remote XP Pro machine is idle. Nothing is running on it, I just rebooted
before I left for the office.

I am able to ping my IP address and I have enabled port forwarding on 3389
to the local IP address of my XP Pro box.

The IP address I am pinging and trying to connect to was provided by my ISP
(They call it a Routable IP Address), so I am 100% sure I am pinging the
correct IP.

I have looked at the "Event Viewer" but don't see any reason for this
problem. I used to have a ZA Pro firewall, but un-installed as I could not
get my router configured running the firewall.

Thanks for any help

 

[Sooner Al]

Try this telnet test to the port that is failing to see what happens...

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

Use the command string 'telnet tserv 3389'...

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

 

[Andre Uys]

I get "Connecting to server IP address" and then it clears. So that works
OK

I am at a loss of what else to do, maybe there are some services that should
be running on the box. Any ideas what services are all required ?

Thanks
Andre

 

[Sooner Al]

If you get the "Connecting to" message the port is not open or the port forwarding is not working or
the target PC is not listening.

If the port is open and forwarding correctly and the device is listening then you would get a blank
window and a blinking cursor.

So, it looks like you calling the wrong IP (WAN IP), or TCP Port 3389 is not forwarded/opened on the
router or the port is being forwarded to the wrong private IP or the target PC is not listening on
Port 3389. From your description it seems the router is not forwarding correctly...

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

 

[Andre Uys]

Thanks again for the help on this.

How do I determine the IP I need to forward to?

When I goto Network Connection and I click on my "Lan or High-Speed Port" I
get and IP address.Is this my local machine IP ?

Port forwarding is set to this IP address. Port forwarding only allows me to
forward to 192.168.2.___ and then the fourth digit(s) of what I assume to be
my local range. Forwarding is set to 192.168.2.x (same as reported by
network connections.)
Persistent Port Forwarding is set to

Inbound port - 3389 - 3389, type - TCP, Pirate IP address - Same as above
192.168.2.x, Private Port - 3389-3389

What else do need to do here. This just so frustrating....

Funny thing, when I go to ShieldUp ( http://grc.com/x/ne.dll?rh1dkyd2 ) and
I probe my ports, it reports my an IP address totally different from what I
see anywhere, and I am not able to forward to this IP as it is not the
specified Private IP Address range allowed under Persistent Port Forwarding.

Still using ShieldsUp, I probe 3389 and it reports that it is open....

Thank for your help

 

[Sooner Al]

That is one way to get the private LAN IP address. Another is to go to "Start -> Run" and type "cmd"
(without the quotes) at the command window. Next use the "ipconfig /all' command (without the
quotes) at the prompt. Note port forwarding works better if you use static IPs on your LAN, simply
because a DHCP assigned IP can change if you reboot/restart the PC. That effectively negates your
port forwarding scheme.

The real question is are you calling using the correct IP for your router when you call from work?
That is the IP assigned by your ISP. Use the http://www.whatismyip.com site to get the IP. That is
also the IP being reported by Shields-Up. If your ISP assigns dynamic IP addresses, and most do,
then that IP probably will change every time you reconnect to your ISP. You might consider using one
of the dynamic DNS services that map an alias, usually of your choice, to the IP address. Then you
would call using the alias. I use a FREE service from No-IP.com for this. Go to http://www.no-ip.com
for further details. Others, some free and some $$$$, are listed on this page...

http://www.remotenetworktechnology.com/ow.asp?Remote_Network_Home/Connections

You could then use the alias to call your home PC from work.

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

 

[Andre]

Thanks,
After messing around last night, I was finally able to get
connected do the desktop using a PC on my local home network, calling the
local PC IP. (This did not previously work, could only call using the Name
of the PC, not the IP)

I was hoping that this would have worked from my PC at the office. Now I am
getting a "Remote Connection had Timed Out" error. At least the error has
changed from "The Client could not connect to the remote computer. Remote
connections might not be enabled or the computer might be too busy to accept
new connection. 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."

Regarding my IP address, my ISP at an additional charge has given me "A
Non-Routable" IP address. I guess that would be a static IP then ?

I will try your suggestions tonight and report back.

Thanks for you help, much appreciated !

That is one way to get the private LAN IP address. Another is to go to "Start -> Run" and type "cmd"
(without the quotes) at the command window. Next use the "ipconfig /all' command (without the
quotes) at the prompt. Note port forwarding works better if you use static IPs on your LAN, simply
because a DHCP assigned IP can change if you reboot/restart the PC. That effectively negates your
port forwarding scheme.

The real question is are you calling using the correct IP for your router when you call from work?
That is the IP assigned by your ISP. Use the http://www.whatismyip.com site to get the IP. That is
also the IP being reported by Shields-Up. If your ISP assigns dynamic IP addresses, and most do,
then that IP probably will change every time you reconnect to your ISP. You might consider using one
of the dynamic DNS services that map an alias, usually of your choice, to the IP address. Then you
would call using the alias. I use a FREE service from No-IP.com for this.

Go to http://www.no-ip.com