How to change RDP Listening Port in Windows

How to change RDP Listening Port in Windows 10/11.  

Using the registry editor to change the listening port will work in all versions of Windows. You will need administrator level permissions to make the change in this branch of the registry.

Using the Remote Desktop feature in Microsoft Windows can be incredibly useful for various purposes. Whether you are working remotely, providing technical support, or accessing files and applications from a different location, RDP offers a convenient solution.

RDP, which stands for Remote Desktop Protocol, is a proprietary protocol developed by Microsoft. This protocol enables users to establish a remote connection with other computers securely. By encrypting the data transmitted between the local and remote machines, RDP ensures that sensitive information remains protected.

RDP Default Port Number

To initiate an RDP session, you need to know the port number associated with it. In most cases, the default RDP port number is 3389. This means that when establishing a Remote Desktop connection, your computer will listen for incoming connections on port 3389.

RDP Access Over the Web

However, it's important to note that using the default port can make your system more vulnerable to potential security threats. Hackers often target commonly used ports like 3389 to exploit vulnerabilities and gain unauthorized access to systems. VPNs are a safer way to augment RDP and security. 

Change the default RDP Port Number

Start registry editor and go to the following key. Double-click to edit, change the port number to another of your preference such as 3390. Just about any number will do as long as it's not a well know port number or a port number used by another windows service or application. Using a high number, usually avoids the situation of overlap. 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

• On the Edit menu, click Modify, and then click Decimal (to change from hex).
• Type the new port number relacing the old, and then click OK.
• Exit the Registry Editor.
• Restart the service for RDP or just restart the computer. 

Two Little Blue Arrows on Folder and File Icons

What do the Little Blue Arrows on Folders and File Icons mean.

Windows will display little blue arrows on folders when the folder and it's file contents are compressed.  This issue with Folders and files on the desktop can be resolved using Online Desktop Support Software. Software that gives technical support the ability to connect remotely to a desktop and control it to fix the problem fast. Access desktops, Servers, Network switches and even firewalls online remotely.  

This can be verified by using a command line executable tool name compact 

Open a command prompt ,  go to the directory or drive letter and run the command  "compact". 

Here's an example using the C drive but it can be any drive such as in the example screen shot it is an E drive of a server  . type compact and hit enter.  

                       C:\>compact  

 

To go through subfolders / directories use the command line option of /s  C:\>compact /s

 

                      

The C next to the folder indicates the folder named active is compressed.  This is from a server I was working on. 

Windows 10 , 11 and expect future releases of Windows automatically begin to compress folders and files when disk space gets low. So even if you've not enabled compression on any particular folder or drive letter, it will turn on automatically. Related post about compression and blue arrows on folders and files Windows File Explore with relevant information. The solution was simple, compression that activates automatically when the C drive of a Windows system desktop runs low on free space.  Hope this helps. 

Access desktops, Servers, Network switches and even firewalls online remotely.  

 

VMware Boot From ISO Image

VMware-boot-from-iso-image-2

One of the nice features of VMware workstation is the feature that gives the user of the the software the ability to boot from an ISO image. This is a great feature and another display of some of the great thought put into this application. If the computer on which VMWare workstation doesn't have a DVD player for example, the ISO image stored on the hard-drive of the host computer or on a network drive can be used to start the installation. The ISO image is read and if it's the installation media for Vista for example, the installation begins. The guest operating system once installed and during the installation doesn't even "know" that's it's being run virtualized. This is a wonderful feature of VMWare workstation and I often find myself asking why didn't this solution come out many years ago as it's a terrific aid for testing and support of applications. With separate operating systems, virtual of course, tests can be run much easier as there's really no restore to perform or drive swapping like in the old days to bring the system back to a state for a re-test.  Some issues can be resolved using RDP. RDS Gateways and Hosts use RDP and permit access to server with RDP enabled