Как открыть порт на windows server 2019
(please don’t forget to mark helpful replies as answer)
Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
There is a difference between having a process listening on the port and having the port allowed on the firewall.
To check on the firewall settings which are effective, you can go under Monitoring on Windows Defender Firewall with Advanced Security. If you run netstat then it will list the ports which are listing and the processes which are using them.
In your case, your issue seems to be related to the fact that no processes are listing on the mentioned port rather than the firewalls blocking them. In all cases, and in case your suspect the firewall to be dropping traffic, you can enable logging and check on the logs for the drops.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Открыть порт на Windows Server 2019
Добрый день!
Можете более-менее подробно описать как это сделать? Открытие портов в брэндмаузере не дало результатов.
Это необходимо для запуска определенного ПО.
Здравствуйте.
В сети интернет хорошо описано как отрыть порт в ОС Windows.
Нужно открыть порт и запустить приложение которое его "слушает", иначе его не увидите открытым.
Если приложение вы запустили, то проверьте не блокируется ли порт со стороны фаервола.
Командой netstat –a вы можете проверить какие порты уже заняты, и выбрать любой другой, отличный от этих.
Желательно брать после 10000, там малая вероятность что наткнетесь на занятый.
Если вы все сделали верно обратитесь к разработчику вашего ПО для решения проблемы.
How to Configure the Firewall on Windows Server 2019
Windows Server 2019 contains a firewall program called Windows Defender Firewall with Advanced Security. The firewall filters incoming and outgoing traffic on your Windows Server 2019 instance to safeguard it from common network attacks. By default, the firewall is configured to allow access to all pre-installed system programs.
However, several programs may use multiple different ports for operation, and these will be automatically blocked because they don’t match with the rules in your firewall configuration. In this case, you need to open the specific port on Windows Server.
Prerequisites
Deploy a Windows Server 2019 Instance on Vultr
A Remote Desktop Connection App
Establish a connection to your server by logging in through any remote desktop app or click the console on your Vultr dashboard to access your server. After you connect you can start configuring your Windows server 2019 firewall rules.
Turn Windows Firewall ON
By default, Windows Defender Firewall is turned on, but in any case, you should confirm the current status and turn on firewall. To do this, click the tools node under server manager and select Windows Defender Firewall with Advanced Security from the drop down list.

From the open group policy management window, check the current status of Windows Firewall profiles if it is set to ON; otherwise, click the Windows Defender Firewall properties option and turn the service on per profile.

Firewall Rules
Windows Firewall rules allow you to either permit or block specific incoming and outgoing network packets on your server. You can choose multiple parameters for each inbound or outbound rule. A rule can consist of a TCP or UDP port, program name, service, or a protocol to filter for every server profile.
Windows server profiles are grouped into, Domain, Private and Public. Domain represents your server’s connection to a corporate domain network, Private applies to your home or workplace network connection, and Public represents non-secure public network locations.
Open an Inbound Port (Incoming connections)
Launch windows defender firewall from the tools sub-menu under server manager. Then, select Inbound Rules on the left panel of the Firewall console.
A list of current rules will be displayed. Now, on the left Inbound Rules sub-menu under actions, click New Rule.

Select Port as the rule type in the rule wizard and click Next.

Now, choose whether the new rule applies to a TCP or UDP port on your server. Then, select specific ports and enter your target port number, you can enter a ports range, or multiple ports separated by — and , respectively, then click Next.

Define your TCP or UDP port rule.

Allow the connection will allow incoming connections to the specified server port
Allow the connection if it is secure will authenticate with IP security and either deny or allow the connection. For example, https connections will be allowed and http blocked.
Block the connection will block all incoming connections to your server through the specified port
In this case, choose Allow the connection to open the port.
Click Next to assign the new rule to one or more profiles. You can select between Domain, Private, and Public, or choose all to apply the firewall rule on multiple profiles.
Next, give your new firewall rule a custom name and description for easy identification. Then, Click finish to enable the new rule. Your new Inbound (Incoming) port rule will be enabled, and all connections to the server that match the port will be accepted.
Open an Outbound Port (Outgoing connection)
From the Windows Defender Firewall console, click Outbound Rules on the left pane, and a list of available outgoing connection rules will be displayed.
Now, click New Rule on the right pane under the outbound rules node.
In the new outbound rule wizard, select Port as the rule type and click Next.

Now, let’s choose whether the new rule applies to a TCP or UDP port. Then, select specific remote ports and enter the target server port number; you can enter a range of ports, a single port, or multiple different ports you intend to open.

Next, on the Action page, select Allow the connection, then click next to select the server profile on which the rule should be enabled.
Give the new outbound rule a name and description that uniquely describes it. Then, click Finish to enable the outbound rule for the target port to be open on all selected server profiles.

Open a Port through Windows PowerShell
From the Windows start menu, open PowerShell. Then, edit the following command and replace it with your settings.
New-NetFirewallRule Creates a new Firewall rule.
Enabled This enables the new rule, by default, it will be set to True.
LocalPort Your target port number.
Protocol Specifies the protocol associated with your port number.
Direction Sets your target direction to either Inbound (Incoming) or Outbound (Outgoing).
Profile Assigns the new rule to a server profile; you can choose domain, private, or public.
Action defines the state for the new firewall rule, enter allow.
DisplayName sets a custom name for the new firewall rule
Your Output should be similar to the one below.
Congratulations, you just opened a network port on your Windows Server 2019. The server will accept incoming and outgoing connections through the selected ports, but the firewall will block connections from a profile that doesn’t match the port rule.
How To Open and Change Firewall Ports In Windows Server 2019
Managing your network traffic is essential in securing any device that handles your workloads. One of the primary tools in doing so is a firewall. The Windows operating system (OS) comes prepackaged with the Windows Defender Firewall to assist with this task.
A firewall is an application that will monitor network traffic on an interface, compare it with a set of rules, and decide if that traffic is allowed or not. When you initially set up your server or add any new applications requiring Internet access, configuring your firewall is necessary to allow incoming traffic.
Whether you are configuring your cloud firewall, a hardware firewall, or the one included in the OS, securing network traffic is essential. This article will cover how to open a port in your Windows firewall, close a port, and allow traffic for specific programs.
Requirements
These are the requirements for opening a port or allowing access to applications you configure:
- The port number or application you want to open on your Windows firewall.
- The protocol the application will use — connectionless (UDP) or connection-oriented (TCP).
- The physical path to the application’s executable (if you will be creating a program-based rule).
Typically, your software vendor will provide this information to you if you do not have it. To assist, here is a brief list of common protocols and their associated port numbers.
- File Transfer Protocol (FTP) Data Transfer — 20
- File Transfer Protocol (FTP) Command Control — 21
- Telnet — 23
- Simple Mail Transfer Protocol (SMTP) — 25
- Domain Name System (DNS) — 53
- Hypertext Transfer Protocol (HTTP) — 80
- Post Office Protocol (POP) — 110
- Internet Message Access Protocol (IMAP) — 143
- Remote Desktop Protocol (RDP) — 3389
- Hypertext Transfer Protocol Secure (HTTPS) — 443
- Microsoft SQL (MSSQL) — 1433
Additionally, follow best practices for firewall rules to maintain optimal data security.