Configuring the Windows Server 2008 R2 Firewall to Open Ports for 2X Parallels Remote Application Server Solutions

Share on FacebookTweet about this on TwitterShare on LinkedInShare on Google+Email this to someonePrint this pagePin on PinterestShare on TumblrBuffer this pageShare on RedditShare on StumbleUpon

To use 2X Parallels Remote Application Server products on Windows Server 2008 R2 with Windows Firewall enabled, a group of ports must be opened for the services to communicate. The figure below shows the ports in use by 2X Parallels Remote Application Server Software to communicate between 2X Parallels Remote Application Server Services on different machines:

Sebastian 4.28.10 Figure 1

Figure 1 – please click to enlarge


Note: In Figure 1, the “>>” implies direction, so that if Server A is connecting to Server B, it will show “A >> B”.

There are two ways to open ports in Windows 2008 R2: either using the MMC or by using the command line. To open a port in the firewall using the GUI, please do the following:

  • Open Port TCP 20002 on a Windows Server 2008 R2.
  • Logon using an administrator account.
  • Click Start and type “Firewall Advanced” in the Search box, or choose Start > Administrative Tools > Windows Firewall with Advanced Security.
  • If you use the search box, a list containing “Windows Firewall with Advanced Security” will appear; click on “Windows Firewall with Advanced Security” and the MMC will appear (Figure 2)

Sebastian 4.28.10 Figure 2

Figure 2 – please click to enlarge


By default, the Windows Firewall will be enabled, and the following rules established: “Inbound Connections that do not match a rule are blocked,” and “Outbound connections that do not match a rule are allowed.”

Since the firewall configuration is already set to allow all outgoing connections, ports to be opened must be configured using the “Inbound Rules” option, by clicking on Inbound Rules on the left of the MMC (Figure 3), and click New Rule from the Right of the MMC (Figure 4).

 >Sebastian 4.28.10 Figure 3

Figure 3 – please click to enlarge

Sebastian 4.28.10 Figure 4

Figure 4 – please click to enlarge


The resulting wizard has five steps: Rule Type, Program/Protocol and Ports, Action, Profile and Name.

In the Rule Type section, select Port and click Next.

In the Protocol and Ports section, select the type of port (ex: TCP or UDP), using Figure 1.

Select the specific local ports and enter the port you wish to open, according to your scenario setup and Figure 1 (ex: Port 20002); then click Next.

In the Action section, select Allow the Connection, and click Next.

In the Profile section, make all three selections and click Next. If you wish to limit the connection to a particular profile, you can do so by selecting only the profiles you think are appropriate to your setup. As this section is somewhat unclear, it may be best to leave the port open in all profiles.

In the Name section, enter “2X Port number 20002”. You may change the 20002 to the port number you entered in the “Specific local ports” section. Include a description of the port, and why the selected port was opened (Ex: “Port in use by 2X to connect to 2X Publishing Agent”). Then click Finish.

Repeat the procedure above for each port and/or protocol you’d like to open. You’re now free to communicate safely!


Sean Bianco is the marketing documentalist and technical writer at Parallels. With a bachelor’s degree in Information Technology and Networking and a three year background in software quality assurance testing and usability engineering, Sean is a subject matter expert in mobility and smartphone, app and device management. He is well-versed in developing technical articles and determining market trends. His excellent analytical and problem-solving skills, with emphasis on understanding relationships between technical problems, result in sound and effective business solutions.

  • Pingback: 2X Blog – Cloud Computing, Virtual Desktop Infrastructure (VDI) & Application Delivery, Server Based Computing (SBC) » Installing 2X Software Components()

  • John

    I cannot get any simple apps like calc.exe to function after upgrading to server 2008 ent (not R2)

    I need to upgrade our server to at least 2008 but not R2 at this time due to the applications not being certified by the vendor for R2.

    The simple issue is that I cannot even get CALC to work on a 2008 server using the published application agent etc. I’ve read all that I can find on the 2x support site and have not found any answer. Firewall exceptions, remote app allwed etc. all seem to do nothing. Help!

  • davidsaliba

    Thanks for your comment but please use the forum for this type of issue.

    If you just purchased or have email support you can open a ticket and support team will be glad to give you recommendation to trouble shoot

  • my music

    Hello from across the sea! This is just what I was hunting for, and you did it well. Thanks

  • Yogesh

    Very straight forward, Thanks for sharing this.

  • Deidre

    Good web site you’ve got here.. It’s difficult to find quality writing like yours nowadays.

    I seriously appreciate individuals like you! Take care!

  • Pingback: How To Fix Cannot Start Windows Firewall Server 2008 R2 Errors - Windows Vista, Windows 7 & 8()