After replacing my Dylink router with Pfsense I can no longer RDP to my Windows
-
Damn that guy can type fast….
-
Thank you Guy - will try and get back to you soon with outcome.
-
Hi Guys,
I changed TCP to TCP/UDP and rebooted pfSense. Same outcome.
The WAN port is picking up a Public IP and the RDP request is visible in the pfSense Log with a green triangle next to it … but I can not trace it to the State Table.
Any ideas?
Thank you
-
Try it from something other than a cell based connection.
-
Filtering Diagnostics > States on :3389 while attempting to connect should certainly show something.
I know you state it worked with the d-link, but are you sure the target server has pfSense as its default gateway? Are you sure it's not a software firewall issue on the target server?
-
Hi Derelict
Thank you for pointing me in the right direction.
I stated that I did not make any changes on my network and obviously I had to make one simple but very important change.
D-Link was on IP 192.168.1.1 and pfSense is on 192.168.1.3. On the Server the Gateway was 192.168.1.1. The Workstation that I use I have a static IP. When I connected pfSense I changed the gateway to point to 192.168.1.3. I intended to go and make the change on the Server. You reminded me to do just that.
Changed the Gateway on the Server and the RDP connection works!
A beginner’s mistake is fixed.
Thank you again,
-
-
You can see what's being use like this:
(UDP being used since RDP 8.0 - W7 with KB2592687 and any later versions. It should fallback to TCP but someone @M$ obviously finally realized that TCP sucks for RDP over WAN…)
-
Ill give it a try… I find other solutions for remoting in have always been a little better. Id like the MS version to be similar in performance.
:)
-
Yeah - over a long haul, having that UDP port open SHOULD knock off alot of laggyness.
I use UDP VPN myself. I'm not a big fan of opening ports on the wan for RDP directly.
