Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Remote desktop won't connect over internet

15 Nov 2011   #1
woodart

Windows 7 Professional 64-bit
 
 
Remote desktop won't connect over internet

I have a laptop running Win 7 Home Premium that will connect to my desktop (Win7 Professional) while connected to the LAN but won't make the same connection over the Internet using the IP address. I'm able to connect both machines with remote assistance over the Internet but not the Remote desktop.

Can someone point me in the right direction?


My System SpecsSystem Spec
.
15 Nov 2011   #2
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by woodart View Post
I have a laptop running Win 7 Home Premium that will connect to my desktop (Win7 Professional) while connected to the LAN but won't make the same connection over the Internet using the IP address. I'm able to connect both machines with remote assistance over the Internet but not the Remote desktop.

Can someone point me in the right direction?
If the target machine to which you want to connect is behind a router, does that router have the correct "port forwarding" configuration to let Remote Desktop from your PC to the target PC through the router's firewall (from outside its LAN)?

Remote Desktop uses port 3389.

Furthermore, if you are running with Windows Firewall also active then it, too, needs to be configured to allow Remote Desktop to reach it. I'm guessing it already does, since you say you can get to the desktop from the laptop when both are behind the router on your LAN.

So my guess is that you simply need to add port forwarding for 3389 (call that service "Remote Desktop" in the ADD dialog for the router) to the IP address of your desktop. Hopefully that IP address for the desktop remains constant, but otherwise you can set fixed IP addresses for your PC desktop in the router and then the port forwarding for 3389 to that IP will never fail.
My System SpecsSystem Spec
16 Nov 2011   #3
woodart

Windows 7 Professional 64-bit
 
 

I set the router port forwarding to 3389 for both "start port" and "end port" but still couldn't get through. I checked the Win Firewall and found the settings shown in the attachment.


Attached Thumbnails
Remote desktop won't connect over internet-firewall.jpg  
My System SpecsSystem Spec
.

16 Nov 2011   #4
PooMan UK

Windows 7 Ultimate 64bit
 
 

Maybe TeamViewer might be a solution
My System SpecsSystem Spec
17 Nov 2011   #5
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by woodart View Post
I set the router port forwarding to 3389 for both "start port" and "end port" but still couldn't get through. I checked the Win Firewall and found the settings shown in the attachment.
You've highlighted the wrong item in that screenshot. You highlighted "routing and remote access (Gre-in)". You should be looking earlier in that same screenshot, at "remote desktop (TCP-in)" for Public networks. It's DISABLED. I may be wrong, but I think enabling it should do the trick. Same way "remote assistance (TCP-in)" is enabled for both public and private networks right above it.

Your Private network option (just above the Public one in the screenshot) is already ENABLED which is why you can remote desktop from laptop to desktop behind the router."

The easiest way to enable either/both is through the simple "allow programs to communicate through Windows Firewall" dialog and check the proper network box:

My System SpecsSystem Spec
17 Nov 2011   #6
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

In passing, I don't use Remote Desktop, nor TeamViewer.

I use RealVNC to get to my own computer from remote around the world, as well as to support the remote computers of friends and family from my home. It's not free, but it's excellent (and has an enormous user community in the "enterprise" world).
My System SpecsSystem Spec
17 Nov 2011   #7
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

One further thought...

You say when you "try to connect over the Internet"... exactly what IP address or host URL are you trying to connect to? Do you have a "fixed IP" address?

Or, like most of us home users, do you have a DHCP-assigned IP address from your cable system or DSL provider? This DCHP-assigned IP address has a "lease period" associated with it and will change periodically (at least theoretically it can change periodically) when the "lease is renewed" and your provider assigns a new IP address to your modem.

Unless you have a fixed IP address you cannot successfully connect to any given IP address and have it be successful (even potentially, assuming your firewall problems are resolved) indefinitely. The best you can hope for is temporary success, until the IP address is changed.

An excellent solution is to use something like DynDNS Hosts, as an intermediate hostname/IP-address re-direct/relay system. You define a symbolic "host name" that's maintained on their server. And you install a client program (DynDNS Updater) on the machine you want to set up as a "host server" for remote access, which every 10 minutes updates the DynDNS server's hostname/IP table with whatever that machine's current IP address is (as currently "leased" to it by the ISP).

Then, any remote client (be it RealVNC, trying to connect to the VNC Server running on your host machine, or Remote Desktop trying to connect to your host machine) uses the symbolic "host name" (e.g. davidscomputer.dyndns.org) in the connection dialog, rather than a hard fixed IP address. Since "davidscomputer.dyndns.org" is registered to DynDNS, the resolution takes place there and the current (up to the most recent 10 minutes) IP address used to relay the connection to your target machine.

In other words, you don't connect to a fixed IP address. You connect to "davidscomputer.dyndns.org". This really is the only way to get around the renewable and thus periodically changing "leased" DHCP-assigned IP addresses almost always used for home Internet connections.


As expected, I have DynDNS Updater installed on EVERY one of the machines I support remotely (including my own) and that does not have fixed IP addresses (i.e. ALL of them!!). Each of those machines corresponds to a unique "hostname" defined in my account at DynDNS.

And, every one of these "host machines" is running VNC Server, supporting remote access by me through VNC Viewer (i.e. "client") installed on any machine I care to be able to use to connect to any "server" host machine. There is a VNC Address Book at the VNC "client" machine as well, which makes selection and connection (through VNC Viewer) super-simple when there are a large number of target host/server machines that are frequently being connected to, as in my own personal situation.

So each host machine runs both (a) VNC Server, and (b) DynDNS Updater. On any of my VNC client machines my VNC Viewer (i.e. Address Book) connection dialogs for each of these target hosts names their "hostname" as defined in my DynDNS account. Thus connection from any "client" machine I happen to be sitting at to any "host" machine I want to connect to is 100% assured, symbolically via "hostname" (i.e. through DynDNS) rather than through absolute IP address which is not a known value at any given time.


NOTE: DynDNS Hosts is free for 1-2 hostnames. I pay for DynDNS Pro, because for me it's worth the $20/year cost for up to 30 hostnames -> IP, which is what I need.

RealVNC Personal Edition (which provides 256-bit AES secure encryption, which in my opinion is MANDATORY, as well as desktop scaling for use with small monitors, Address Book, file transfer, chat, printing from remote host on client printer, etc.) is $30.
My System SpecsSystem Spec
21 Nov 2011   #8
woodart

Windows 7 Professional 64-bit
 
 

Sorry for not responding sooner but I just got home from spending the past 6 days in the hospital. I'll catch up on the replies in the morning and respond.

Thanks!
My System SpecsSystem Spec
Reply

 Remote desktop won't connect over internet




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Remote Desktop does not connect
I am the administrator for my church's networked computers. My work computer is running Windows 7 Pro. I have a need to access my computer from home. My home computer is running Vista Ultimate 64. I sent an invitation from the work computer which I have received at home. When I double-click on...
Network & Sharing
Question on setting up Win 7 Remote Desktop to connect via internet
I have setup Remote Desktop on two different Windows 7 computers and I am unable to connect to them. I have followed several examples, which are the same on setting this up, but still unable to connect. The examples show trying to connect using the computer name and user name. If you are connecting...
Network & Sharing
Connect two PC using Remote desktop connection over the internet (DSL)
I need help. I want to do some things on my sisters' laptop which is in other country. Here is the situation: My computer has Windows 7 Ultimate (64 bit) installed and I am using ADSL internet connection. My sister lives far away in UK and her lap-top is connected to internet using the...
Network & Sharing
Remote Desktop Access over the internet: "can't connect to the server"
Hello, I am trying to configure Remote Desktop Access to work over the internet. Remote Desktop Access works on my local network. Both of my computers are on Windows 7 Professionnal. My router is a Belkin F9K1002. I followed the official widows tutorial. I forwarded the necessary port...
Network & Sharing
Remote Desktop Client 6.1 Cannot connect to remote computer
We have several remote systems that can all connect fine. I am having an issue with one box. It is a windows 7 home premium machine with netgear wireless nic. When I open mstsc to connect to a remote machine I put in the ip address and click on connect. I receive an immediate failure with the...
Network & Sharing
Remote desktop wont connect to desktop.
I have a desktop HP (windows 7) and a new macbook pro 15 on which i am running both mac os x and windows 7. I can connect from my desktop to my laptop using remote desktop connection but not the other way around. I have a network set up and can see the computers are connected. I opened port 3389,...
Network & Sharing


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:28.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App