1

I use Remote Desktop to visit the desktops of other computers on my network. I have been also using Remote Desktop to access one of my computers from outside the network by using DynDns, port forwarding the router and then entering the external IP address of my network into Remote Desktop. This has been working fine for a while.

Now I want to be able to access another computer on the network from outside the network. I have followed instructions I have found online ( http://www.guidingtech.com/24155/remote-desktop-multiple-computers-network/ ). However I am still not able to access the computer via RD.

Here is what I have done:

  1. Changed the port of RD on the second computer to 3388 from 3389.
  2. Set up port forwarding on the router so that connections on 3388 are sent to the correct computer.
  3. Allowed sharing in the network adapter preferences.
  4. Added a firewall exception for port 3388 as a TCP connection.
  5. Added the correct :3388 suffix to the External IP address I am using to remotely access the network.
  6. I have made sure the IP address I am using is correct - The same IP address with suffix :3389 brings me to the first computer on my network.
  7. I have checked that RD connects correctly when accessed from within the network.

Is there anything I have forgotten to do?

UPDATE: To be clear, I am trying to connect from a Windows 7 system to a Windows 10 system, in case that makes any difference.

UPDATE: Here is a screen print of the port forwarding configuration. enter image description here

18
  • Have you checked that RD is correctly set up, by checking it on the internal network, using its intranet address from one of the other computers on the network?
    – AFH
    Jun 15, 2016 at 14:47
  • Yes, it works fine when accessed from within the network.
    – Matthew
    Jun 15, 2016 at 14:51
  • Sorry, I've just read your point 7, so I needn't have asked: I don't know how I overlooked it before. Have you checked port 3388 in the firewall on the machine outside the network? It has in the past been used by Trojans, so outgoing traffic may be blocked by default. But you do seem to have covered most of the bases.
    – AFH
    Jun 15, 2016 at 15:05
  • 1
    Try temporarily disabling the firewall on the target computer, then connect from outside the network. If the connection still fails you know the problem is with the port-forwarding on the router. If the connection succeeds you know the problem is with the firewall configuration on the computer. Jun 15, 2016 at 15:10
  • 1
    Can you configure your router to forward port 3388 on the outside to port 3389 on the inside? Jun 15, 2016 at 17:17

1 Answer 1

1

Try temporarily disabling the firewall on the target computer, then connect from outside the network. If the connection still fails you know the problem is with the port-forwarding on the router. If the connection succeeds you know the problem is with the firewall configuration on the computer.

Because you can connect locally, I suspect the router current port-forwarding configuration is at fault. Try configuring your router to forward port 3388 on the outside (Internet) to port 3389 on the inside (LAN). You'll of course need to reconfigure your (second) target machine to once again listen on the default port of 3389.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .