Remote Desktop will not connect on port 3388

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

1 Answer

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.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like