|
Hello all, Looking for any advice in setting up a remote desktop connection. I have been using remote desktop for quite some time across my local network. Works great for that purpose. Lately, I've wanted to set it up to run over the internet. Here's what I have done:
That's where I'm stuck. I don't have a clue about what to do from here. Does anyone have any ideas? Thanks in advance, |
|
Have you tried the Open Port Tool to check if the port seems to be correctly forwarded to your computer? The Open Port Tool shows it open. I have one router; a D-Link DIR-655. the computer is running Vista Ultimate, SP2. My internet connection is a Hughes satellite system. My second connection is a verizon (tethered phone/modem).
Feb 08 at 04:13 AM
Don Fink
|
|
Comments:
|
|
Try TELNETTing to the computer on port 3389 telnet yourdomain 3389 Check that your router is port forwarding port 3389. I don't think I'm using this forum correctly, so I apologize. I don't think Vista has telnet. I know my XP netbook has it, but none of my Vista machines do. There's another program out there (forget its name off hand) that I could install and try.
Feb 08 at 04:24 AM
Don Fink
You can install telnet via the instructions in this web link: http://www.tech-recipes.com/rx/1793/vista_install_telnet_client/
Feb 08 at 05:18 AM
JHPArizona
Adding telnet in the Windows components list, takes forever to complete. Personally I would much rather just download and use Puttytel instead.
Feb 08 at 11:05 AM
VikingTiger ♦
|
|
On your PC, check your Remote Desktop & Windows Firewall settings. They should be set ALLOW incomming connections on Port 3389 from "Anybody" (not just your local LAN). Also you might try turning "off" Windows Firewall TEMPORARILY and/or physically connecting the PC directly to the WAN or using your router's "DMZ" feature, if available. If that works, you can then concentrate on setting your router, Windows Firewall and Remote Desktop to allow only "YOU" (or others you authorize) from your location outside the LAN. Some good ideas here. My Windows firewall is off, preferring instead to use the router's firewall. I placed the computer in question in the DM Good comments. My Windows firewall is off, preferring instead to use the router's firewall. I did place the computer in question in the DMZ. It made no difference. My issue appears to be that I don't understand how IP addresses resolve to individual computers when data moves from outside the LAN to inside, through the router. I believe I need to learn that part of networking before this can be solved. I'll read on...
Feb 08 at 01:55 PM
Don Fink
Regarding your question about IP address. The capability of a router to direct (route) IP packets to/from selected LAN-side PC (hosts/clents) is referred to as NAT from from the phrase "Network Address Translation". Rather than explan the details of NAT in this comment, I'll gladly recommend this excellent place to learn more: Go to http://www.grc.com
Feb 12 at 05:39 AM
dm90621
|
|
I had a similar experience with Hughes. Since they also use NAT on their satellites, I will be impossible to use Remote Desktop from outside your local network since your system's IP address changes with each and every session. You need to purchase a static IP address from them. With a static IP address, you won't need DynDns, or the updater software. Just connect to the static IP address they give you. Do not use the TS gateway option on your client. Another less expensive option is to use a third-party remote access server that supports an RPC service. http://access-remote-pc.com comes to mind. If Hughes do not provide public and routable IP addresses, then it is impossible to connect to them from the Internet. That has however nothing to do with the fact that the IP address is dynamic (changing regularly). Most home users have dynamic IPs, and with the help of dynamic DNS, that's not an issue.
Oct 15 at 05:26 PM
VikingTiger ♦
|
Well, I appreciate the answer below. When I turned off TS Gateway, I then get the "This computer can't connect to the remote computer" error window. I tried it on two different machines, and two different networks to be sure. I can still ping the machine in question, and I can still connect to it locally.
Still at a complete loss. I hate to have to go to the commercial stuff when this is supposed to be built right in...
Ping simply pings your router, not the computer. As for the TS Gateway, I have never needed to set that (indeed until you mentioned it I didn't know it existed).
However your problem may be related to your use of satellite. What is your inbound connection type?
This is where my limited knowledge begins to break down, and is probably the cause of my siiue here. My connection type is, I think, "Dynamic IP (DHCP)". At least, that's how the router is set. The only reason I know this is because that's where the router is set for "Connection Type". The router is the DHCP server for the LAN.
I guess that what I'm not getting is how an internal ip address is resolved by the router. It seems that when I ask for my IP address from the various web sites, I get the same IP from each machine behind the firewall. I need to figure out how it resolves to 1 computer