I have a problem connecting to Windows 10 Pro with RDP
I have new computer with Windows 10 Pro installed. Updated fully with Windows Update.
I configured RDP access to this computer. It works fine from LAN but I cant connect from Internet. I'm sure that it is this computer problem.
I have another server Windows Server 2012 in the same network and I can connect without problem.
More details:
WS2012 has address 192.168.1.1
Win10 computer has address 192.168.1.2
Ports redirection configured
TCP/UDP 3389 to 3389 on 192.168.1.1
TCP/UDP 12345 to 3389 on 192.168.1.2 (if I switch redirection to 192.168.1.1 I can connect on port 12345 so redirecting works fine)
I can connect from my own laptop to WS2012 through Internet
I can't connect to Win10
Port testing shows that it is closed from outside.
In local network both servers can connect without problem and my own laptop can connect to both servers too (from LAN).
I changed IPs, changed ports redirecting, disabled firewall, checked policies, disabled antivir, uninstalled almost all software.
I can connect to windows server and cant connect to win 10 with the same configs and tools.
I have no idea what can I try more.
Tried everything.
Any clue to test?
Best Answer
It's likely NOT the Windows 10 system. If it were, RDP would not work on the LAN side either.
Since it works from a LAN but not remotely, there's two possibilities - 1) ingress forwarding is busted, and/or 2) egress forwarding is busted.
One, the router/gateway is not forwarding requests to it properly.
Two, the system is unable to respond back out the router to world+dog, so any connection attempts time out waiting for a client response.
Since you also have a Windows 2012 Server running, using the default port (3389) for RDP, it would seem that your redirected port 12345 is not being passed across the router properly. Try disabling RDP on the 2012 system, setting your Windows 10 desktop to use the default port, and swapping the IP's so that the router directs RDP traffic to the system you're testing.
Once you're sure it works using the default port, then try setting up the redirected port to the same IP. The process is simply a matter of changing one thing at a time, then verifying the change worked.
Once you get external RDP to the Win10 system set on your custom port, then you can put in a second redirect rule for the default port, aimed at your 2012 Server.