Here’s an annoying one that I run into quite frequently. On Windows Server 2012, it appears there’s not a quick and easy way to change the network type for a network connection other than to use PowerShell. The problem that I typically run into, is that firewall rules for a specific program are only set for the “domain” profile, so here’s how to force the network type on some interface. This is just for my own personal reference, but I took this info directly from here. Continue reading “Server 2012 – Force a Network Type with PowerShell”
Remote Desktop Server – Registry Key to Change RDP Listening Port
As you probably already know, by default, Microsoft Remote Desktop listens on port 3389. This is all good, but what if you are behind a firewall and wanted to allow port forwarding to be able to access multiple computers via RDP remotely but can’t because they are all running on the same port?
Well, if you’re crafty and have a decent Linux-based router like Mikrotik that will let you create packet mangling rules to change the destination port number, you can get around this, but in environments where you have little SOHO routers like Linksys or Belkin, typically this is where changing the port number that RDP listens on comes in handy. The only problem then is remembering whatever port you changed it to because then you have to specify it anytime you connect via RDP which can be a pain if you’ve got a bad memory. There are already a thousand and one articles out there to help you change the port number, this is a quick post for future reference for myself.
Continue reading “Remote Desktop Server – Registry Key to Change RDP Listening Port”