locked
Router Port Forwarding and RDP with Windows 10 Pro RRS feed

  • Question

  • I have 3 PCs recently upgraded to Windows 10 pro with RDP enabled on the default port of 3389 (do not want to change these because I do not want to mess with new windows security, and to be quite honest, I should not have to, I can make the router deal with it.)


    The 3 PCs have static NAT IP addresses 192.168.1.[250,251,252].


    Within the LAN, I can RDP from any machine to either of the other 2 machines: 250->251, 250->252, 251->250, 251->252, 252->250, 252->251.


    I have 3 TCP port forwarding rules enabled on a Peplink Balance 20 router for inbound ports 3389, 13389 and 23389, pointing to 251, 250 and 252 respectively - the first is a single port 3389->3389 (which I would like to get rid of, in favor of a port mapped one) and the 2 other inbounds are port maps to internal port 3389 on the respective machines (i.e., 23389 port maps to 192.168.1.252:3389)


    In the case of one of the machines, the port mapping work perfectly (i.e., RDP to router internet address @ port 23389 takes me to 192.168.1.252:3389) but the other two do not work with port mapping.


    Additionally, the other 2 machines work with single port mapping (i.e., if I map inbound port 3389 to 250:3389, OR inbound port 3389 to 251:3389, I can set up external RDP sessions.)


    I have checked firewall rules and windows defender on all 3 machines and they are identical.


    So far I have compared the registry entries for Terminal Services on the machine that allows port mapped connections and one of the machines that does not and they are identical.


    Does anyone have any other suggestions on where to look?


    Thanks.


    D
    Thursday, December 24, 2015 2:41 PM

Answers

  • On a non-working machine check Event Viewer (right click start select Computer Management, expand Event Viewer), Application and Service Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS > Operational. Does that show events at connection attempt time? any warnings or errors?

    Other than that resetting the IP and Winsock settings worth a try;

    From an admin command prompt;

    netsh winsock reset

    netsh int ip reset c:\resetlog.txt

    and then as directed restart the PC.

    Monday, December 28, 2015 3:02 PM

All replies

  • Well appreciate you say checked the firewall, but would want to rule that out 100% to be sure, as that would be the only thing I am aware of (beyond third party security software) that would block ports. My thinking perhaps in on the Advanced tab of the 'Remote Desktop - User Mode' rules and perhaps the Edge traversal or the Scope settings tab. Beyond that turning the firewall off and trying would be worth a try IMHO.

    Does the 23389 rule work if you change the target IP to one of the other machines?

    Thursday, December 24, 2015 7:52 PM
  • Per my original post, of the 3 machines, only one machine (252) will work with port mapping using  either the 13389 or the 23389 port

    The other 2 machines only work with a straight port forward external_ip:3389->internal_ip:3389.

    Even with the firewall disabled, I cannot connect.

    D

    Monday, December 28, 2015 1:46 PM
  • On a non-working machine check Event Viewer (right click start select Computer Management, expand Event Viewer), Application and Service Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS > Operational. Does that show events at connection attempt time? any warnings or errors?

    Other than that resetting the IP and Winsock settings worth a try;

    From an admin command prompt;

    netsh winsock reset

    netsh int ip reset c:\resetlog.txt

    and then as directed restart the PC.

    Monday, December 28, 2015 3:02 PM