WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I have been reading these forums for months now, but this is my first post so please bear with me.
I have got Remote Desktop to work within my LAN (using 192.168.x.x) between my Vista Business laptop and my XP pro Desktop with either computer acting as client or host on separate occasions. I cannot, however, successfully get RD to work via my public IP address.
I have forwarded the RD port on my Belkin router as per the instructions at portforward . com (3389, done once for TCP and again for UDP-no option for both in this router). I only forwarded the port to the desktop, the one I want to act as host.
I then setup my desktop with no-ip to publish my address--no success with connection attempts. I then setup my router with DynDNS (as it natively has the option to publish my address with that site)--still yielding no success.
In Remote desktop whenever I type in any one of my addresses (IP or published DDNS): 76.189.xxx.xxx, xxxcomputer.no-ip.org, xxxcomputer.dontexist.com, I get the same error message:
"This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
I have double checked that within the Windows firewall there is an exception for remote desktop, and have also tried disabling the firewall, both in Windows and on my router.
I still receive this error message weather I am connected via LAN and trying to connect via my public IP, or if I am 30 miles away and trying to connect via public IP/Domain name. Even with all firewalls turned off and the ports forwarded I get the same error message listed above
Any help is greatly appreciated at this point.
Didn't find the information you thought to find? Check out these Similar Threads
From both sites I am using cable internet (service by WOW at laptop site [remote] which modem is Scientific Atlanta's Webstar, model number DPX100, and by Time Warner at another site with a motorola modem (I can check the model number in a day or two when I get there)).
I have tried using each site as host and client (having multiple computers at each site) but can only get the RD LAN connection to work (using local IP).
At each site I am behind a Belkin Wireless Pre-N Router: model-F5D8230-4, with firmware version- 1.01.03.
So what I'm using now is:
Laptop (Vista-Business)-Belkin Router - Webstar Modem- 30 miles away....-Motorola Modem - Belkin Router - XP Pro Dekstop
I hope this supplies all the info. Let me know if there's anything else.
To test port forwarding use another (would work from same computer you wish to connect to but better another one) computer and do the following to the computer that you want to connect with.
go to mywanip.com get you public wan ip
first ping you dynamic ip by name
ping mywanip:3389
then
ping actual wan public ip:3389
let me know what happens
If you want to PM me the IP and NAME I will test it from here. But do not post these in the thread.
Hi mflynn,
I am away from my computer until Tuesday but I will definitely check the ping for both the public IP and the domain name for that IP when I get to my apartment.
(I should just run command prompt and type "ping mywanip:3389" for the domain name and "ping xx.xxx.xxx.xxx:3389" for the public IP and report each, right??)
Yes it but would be a better idea to do it while away from home if you can get to a computer! You do want to come from the outside in to your computer correct!
Do it now if you can and post results so I will have it when you get home!
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Vikram>ping xx.xxx.xxx.xxx
Pinging xx.xxx.xxx.xxx with 32 bytes of data:
Ping statistics for xx.xxx.xxx.xxx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 58ms, Average = 44ms
C:\Users\Vikram>ping vikcomputer.no-ip.org
Pinging xxxxxxxxxxx.xx-xx.xxx [xx.xxx.xxx.xxx] with 32 bytes of data:
Ping statistics for xx.xxx.xxx.xxx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 55ms, Average = 43ms
Personally, I would never open up the RDP ports through the router/NAT/firewall. Why would you want to make it so easy for anyone on the internet to access your desktop with only your normal login name and password between them and total control of your PC.
If you want remote desktop connection, connect to your network via a VPN. VPN consist of an encrypted and authenticated tunnel through the internet. Once you have a VPN connection, you'll then be able to use RDP over the VPN to get remote desktop.
If you don't want to go to the trouble of setting up a VPN, then use one of the dedicated service that will provide you with a secure way to get a remote desktop. For example, logmein.
