How To Open Port 22 On Windows Server 2012

June xviii, 2018
Concluding updated on July 20, 2020

Windows Server 2008 R2 onwards Firewall Configuration for Parallels RAS

To use Parallels RAS on Windows Server 2008 R2 upwards to Windows Server 2019 with Windows Firewall enabled, several ports must exist opened for the Parallels RAS components to communicate.

List of TCP and UDP Ports Used past Parallels RAS

The figure below shows the most common ports used by the Parallels RAS component to communicate when running on dissimilar machines:

Figure i

Note: In Effigy 1, the ">>" implies direction. If Server A is connecting to Server B, information technology will testify "A >> B." Therefore, you lot should open the following ports for the Parallels RAS components to work:

Gateway

TCP Ports 80 and 443

UDP Port 20000

Publishing Agent

TCP Ports 20001, 20002 and 20003

TS Agent

TCP Port 30004

UDP Port 30004

VDS Amanuensis

TCP Port 30007

UDP Port 30007

For a detailed and complete listing of all the ports that the Parallels RAS components use to communicate, please refer to the Port Reference section in the Parallels Remote Awarding Server Administrator'southward Guide.

Start your free Parallels RAS 30-day trial today!

Default Windows Server Firewall Configuration

The Windows Firewall is enabled by default on all profiles on a Windows Server operating system. The default configuration has the post-obit rules:

• Inbound connections that practise not match a rule are blocked.
• Outbound connections that exercise not match a dominion are immune.

The Windows Firewall configuration is already set up to allow all outgoing connections; therefore, merely ports for incoming connections should be opened. These must exist configured in the "Entering Rules," as explained below.

Windows Firewall Configuration

There are 3 different means to open up ports in Windows Server 2008/2012 R2/2016 and Windows Server 2019. You tin can do so by using either:

• MMC
• The control line (netsh)
• PowerShell commands (only for 2012R2 and 2016)

Opening Ports on the Windows Server Firewall Using GUI

To open a port in the firewall using the GUI in Windows Server 2008/2012 R2/2016 and Windows Server 2019, follow the steps below:

1. Log in using an administrator account.
2. ClickStart > Administrative Tools >Windows Firewall with Advanced Security

Figure 2

3. Click on Inbound Rules on the left of the MMC (Figure iii), and so on New Dominion on the Right of the MMC (Effigy 4).

Figure 3                                                                                Effigy iv

There are five steps to open a port and have incoming connections with the wizard:

• Rule Type
• Protocol and Ports
• Action
• Profile
• Name

For this case, we will open TCP port 20002 on servers that are running the Parallels RAS Publishing Agents part:

4. Dominion Type section – select "Port" and click "Side by side".
5. Protocol and Ports section – select "TCP" every bit the type of protocol and type "20002″ in the "Specific local ports" input field:
6. Action section – select "Allow the Connection" and click "Next".
7. Profile section – select all iii options and click  "Adjacent".  If you wish to limit the connection to a item profile,  select only the profiles that are appropriate to your setup. For this example, we will open the port on all profiles.

8. Name section – enter a "N ame" for this rule. It is recommended to list the port number in the name, so the rule is easily recognizable. For example, the new rule could exist named "Pub_Agent_20002_IN". Click "Finish" when ready.

R epeat the to a higher place process for each additional port and/or protocol you'd similar to open in each server.

Opening Ports on the Windows Server Firewall Using Command Line (netsh)

To open a port on the Windows Firewall using the netsh command line, follow the process below:

1. Login to the server using an administrator account.
2. Run the Control Prompt as Ambassador.
3. Execute the following control to open up the TCP port 20002 on the servers running the Publishing Agents role:

Below is an explanation of the format of the netsh command: Note: By default, netsh opens the specified port on all profiles. If you desire to specify a specific profile, use the profile parameter: profile=public|private|domain

To open additional ports, repeat the in a higher place procedure for each additional port and/or protocol y'all'd like to open up in each server.

Opening Ports on the Windows Firewall Using PowerShell

To open a port in the Windows Firewall using PowerShell commands, follow the process beneath (merely applies to 2012 R2 and 2016 Windows Server OS):

1. Log in using an ambassador account.
2. Run the Windows PowerShell as Administrator.
3. Execute the following command to open the TCP port 20002 on the servers running the Publishing Agents role:

Below is an caption of the format of the New-NetFirewallRule PowerShell command:

Annotation: Default New-NetFirewallRule opens the specified port in all profiles. To specify a specific profile, add the –Profile parameter to the command with one of the following options:

-Profile=public|private|domain

Repeat the higher up process for each additional port and/or protocol you'd similar to open in each server.

How to check if the Port is Open

To check if a port is open up or not, you need to activate Telnet, which by default is non installed in Windows Server 2008, Windows Server 2012, Windows Server 2016, and Windows Server 2019. The easiest fashion to install the Telnet client is via the command line as follows:

1. Launch the command prompt as an Administrator

two. Execute the command beneath:

dism /Online /Enable-feature /FeatureName:TelnetClient

You can also activate Telnet via GUI if yous follow the steps outlined in this link.

3. Next, check if a port is open by typing the command using the format below:

telnet [IP accost] [port]

In the above command specification, the IP address is the IP address of the server hosting Parallels RAS. At the same fourth dimension, the port is the port number, which in this case tin be 20002. You tin check the IP accost of the local server by issuing the command below:

ipconfig

For example, if y'all execute the above control and discover that your IP address is 173.20.39.40, you can check if a port 20002 is open or not by issuing the command below:

telnet 173.20.39.40 20002

When you meet a blank screen, information technology indicates port 20002 is open on the server—meaning the exam is successful. However, when you see receive a "connecting …" or an error message, it indicates port 20002 is not open on the server.

Start your free Parallels RAS thirty-day trial today!

---

References

Windows Server 2012 Firewall | https://support.rackspace.com/how-to/managing-the-windows-server-2012-firewall/

Windows Server 2008 R2, 2012 Firewall | https://technet.microsoft.com/en-us/library/cc753558(five=ws.xi).aspx

Opening ports in the Windows Server firewall | https://technet.microsoft.com/en-us/library/ms345310(v=sql.100).aspx

Fasthosts Windows Server Firewall | https://assist.fasthosts.co.uk/app/answers/detail/a_id/2032/~/setup-a-windows-server-firewall

Rackspace | https://back up.rackspace.com/how-to/managing-the-windows-server-2012-firewall/

Source: https://www.parallels.com/blogs/ras/configuring-windows-server-firewall-for-parallels-ras/

Posted by: burkesiry1989.blogspot.com

Share this post