Windows 10: Changing RDP port after upgrade

I had my port set to 443, and it worked. I cannot seem to RDP on that port, or the default port. The firewall is OFF. Any ideas? The port was changed in registry already when I went to double check, rebooted a few times, still no luck. Does the new smart filter thingy block something?

Did some quick troubleshooting. I disabled remote desktop, and watched netstat -a, and it stopped listening on 443. I then enabled it on 443, and it started listening again, so I know the port is indeed open on the box, and not in use. I am trying to RDP over the LAN, not internet too! The box responds to pings.

:)

 

Default Printer changing to Printer that's first in the "Port Name" List

Hi All,

I have an issue where the default printer keeps changing to the Printer that's Port Name is first in the "Port Name" List in ascending order, whenever I RDP into it.

Some Note:

• The default printer changes on the remote PC (The PC I RDP into).
• All OS's involved are Windows 10 Pro x64.
• I unchecked the "Printers" checkbox on the saved .RDP file.
• I have turned the "Let Windows manage my default printer" option on and then printed from the correct default printer but then when I RDP into it from home it changes to the Printer that's Port Name is first in the "Port Name" List in ascending order.

I cant rename the Port Name without re-adding the printers which I really don't want to have to do.

Thanks in advance for any help.

 

Windows 10 Remote Desktop Change Port Problem

Windows 10 RDP works with standard port 3389. I have been trying to change a to a NEW port for additional security. I have done the standard changes and entered the NEW TCP port via regedit "TCP port". I have also changed my router NAT to the NEW port.
I have changed the logon to include the NEW port. I have rebooted the W10 host and W7 remote client. I have tried different unused ports. The RDP logon always fails unable to locate.

Any ideas? Has anyone done this successfully in W10?

 

I assume you're setting it to 443 in order to bypass firewall rules at work or school so you can remote to your home PC. This is a lot easier to set in your internet gateway/router if it supports it. Many GW/Firewalls have an option to specify the external and internal port of forwarded ports.

Have you verified that Remote Desktop is enabled? By default, it's off in 10 after an upgrade.

 

I've enabled and disabled a few times. It is clearly registering the change as netstat showed listening on 443. I've tried default as well with no luck.

 

To add, I am running Windows 10 pro. Do I need to have remote assistance checked? If I recall, it was not, but I never thought that was a requirement before.

 

If you can see 443 is listening, and your windows firewall is off, then your problem is with your router. Perhaps your IP address changed (internal IP) and your router is no longer forwarding to the right IP.

 

It responds to pings, resolves on hostname though. I have tried connecting based on IP and hostname for fun.

 

That's your external router responding to the ping, not your internal computer.

 

Hmmm, what? I checked my router's mac list, it is showing the right box still. This only started right after the upgrade to win 10.

 

What does your mac list have to do with anything? I'm talking about the port forwarding.

 

You said that was my external router responding to pings, and not my computer? My external router is hooked directly up to the computer in question. I unplug the ethernet, and it does not respond to pings. I said the MAC list on the router is correct, because I assumed you thought my router 10.10.5.1 didn't know where my server was, 10.10.5.20 (static).