Quantcast
Channel: Astound forum - dslreports.com
Viewing all articles
Browse latest Browse all 2000

RCN: Inbound Port 3389 (Microsoft Remote Desktop)

$
0
0
I've had RCN for a decade and always had an inbound connection, via port 3389, to my desktop computer at home that I accessed from work. The connection stopped working in the past two weeks and I am wondering if this is RCN or not, just really curious. There are three variables in play here all inside of the past two weeks: 1. I moved from the 50/5 to 155/15 package about two weeks ago. Called RCN, they switched me over the phone, and had new speeds. 2. I upgraded the firmware to my Netgear Nighthawk R7000 AC1900 router. I made sure all port mappings carried over and weren't messed with. 3. I upgraded my desktop from Windows 7 to Windows 10 (Pro) -- clean install. One of the first things I did was to enable remote access and make an exception in Windows firewall. So it stopped working and I spent an entire 30 minutes troubleshooting. I could RDP from inside my network just not outside. I validated the IP didn't change and my Dynamic DNS was still updating. Totally at a loss and triple checked everything. Then it hit me.... So I changed the port mapping from 3389 (external) > 3389 (internal) ....to.... 3000 (external) > 3389 (internal) and boom, it worked again from outside the network. Did RCN start blocking 3389 inbound traffic? That's the only reasonable explanation I have at the moment. :) -- When judgment day comes, I'm confident I will end up in a place that's quite comfortable, very well deserved, and truly reflects how I strive to live my life. It's amusing certain groups feel the need to tell me their place will be better than mine.

Viewing all articles
Browse latest Browse all 2000

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>