firewall port inbound windows terminal server

If you want to know more about the feature, read this article: Windows Defender Firewall with Advanced Security: What is it? How to open it? What can you do with it? Windows Defender Firewall is a simple tool for managing incoming and outgoing connections on your Windows device. Open the Windows Defender Firewall using the search

If you do not know which version of Windows you have, read this tutorial: How to tell what Windows I have (11 ways). NOTE: This guide covers Windows 11 and Windows 10. Do you use the Windows Defender Firewall?.Use Command Prompt, PowerShell, or Windows Terminal to open the Windows Defender Firewall Start the Windows Defender Firewall using the Run window Open Windows Defender Firewall using the Settings app Start the Windows Defender Firewall using Control Panel

Make sure you modify the port number to match your own. These two commands add rules to allow inbound traffic on the custom RDP port number.

New-NetFirewallRule -DisplayName 'Custom RDP Port (UDP-In)' -Direction Inbound -LocalPort 50102 -Protocol UDP -Action Allow Use the following PowerShell commands to add the rules: New-NetFirewallRule -DisplayName 'Custom RDP Port (TCP-In)' -Direction Inbound -LocalPort 50102 -Protocol TCP -Action Allow Now that the RDP port number has changed, you need to adjust the Windows Defender firewall to allow your new custom RDP port. Adding firewall rules for custom RDP ports ^ Some people even like using a port number from the IANA suggested range (49152–65535), since it is not likely to conflict with other well-known or custom services. You can use any port number, but it is recommended to use one between 105. When you change the RDP port number using this command, both the TCP and UDP endpoints will be changed to the same port number. This command uses the Set-ItemProperty cmdlet to change the port number to an ephemeral port ( 50102, in our example).

Firewall port inbound windows terminal server