BoDEAN Posted August 2, 2015 Share Posted August 2, 2015 Odd. I use No-ip, and have a registered host name that I have used in the past to connect to my Windows 8.1 system Since a clean install of Windows 10, I no longer can connect. I have allowed remote connections, and the port 3389 TCP is forwarded on my router per http://windows.microsoft.com/en-us/windows7/allow-remote-desktop-connections-from-outside-your-home-network I have a static IP on my pc, and the static ip on my router points to that forward port. I also disabled windows firewall. Anyone else having issues with remote desktop connections? Link to comment Share on other sites More sharing options...
RATiO Posted August 2, 2015 Share Posted August 2, 2015 I had this - had to change network profile to private as windows 10 had set it to public binaryzero 1 Share Link to comment Share on other sites More sharing options...
BoDEAN Posted August 2, 2015 Author Share Posted August 2, 2015 I had this - had to change network profile to private as windows 10 had set it to public Where do you do that? Link to comment Share on other sites More sharing options...
BoDEAN Posted August 2, 2015 Author Share Posted August 2, 2015 Actually shows I am private, not public. Link to comment Share on other sites More sharing options...
vcfan Posted August 2, 2015 Share Posted August 2, 2015 (edited) so u did disable firewall for sure? I had the same problem, but I had to toggle private network in windows firewall then it worked. Link to comment Share on other sites More sharing options...
BoDEAN Posted August 2, 2015 Author Share Posted August 2, 2015 so u did disable firewall for sure? I had the same problem, but I had to toggle private network in windows firewall then it worked. Toggle as in what, disable then enable? Link to comment Share on other sites More sharing options...
Aergan Posted August 2, 2015 Share Posted August 2, 2015 RDP works fine here for me but I limit my use to LAN or via a SSH tunnel. Link to comment Share on other sites More sharing options...
vcfan Posted August 2, 2015 Share Posted August 2, 2015 Toggle as in what, disable then enable? just meant I checked it so it became on. by default only public was checked and not private. Link to comment Share on other sites More sharing options...
BoDEAN Posted August 3, 2015 Author Share Posted August 3, 2015 So if i connect to my internal ip address, i can connect. External, no go still. Small progress Link to comment Share on other sites More sharing options...
xendrome Posted August 3, 2015 Share Posted August 3, 2015 Working fine here over the internet. Did you verify your port forwarding is stil intact on your router as well as your static IP on your computer didn't change during the upgrade? Link to comment Share on other sites More sharing options...
BoDEAN Posted August 3, 2015 Author Share Posted August 3, 2015 yes, 3389 is still forwarded to my static ip, protocol TCP Link to comment Share on other sites More sharing options...
xendrome Posted August 3, 2015 Share Posted August 3, 2015 Any you verified the static IP is still set on the NIC? Link to comment Share on other sites More sharing options...
BoDEAN Posted August 3, 2015 Author Share Posted August 3, 2015 SOLVED: I factory reset the router, and all works now. THanks Link to comment Share on other sites More sharing options...
Recommended Posts