Available article translations:

How to restrict RDP connection to Terminal Servers for Parallels Client users

  • Parallels Remote Application Server 15.5
  • Parallels Remote Application Server 15.0


I would like to restrict Parallels Client users from accessing Terminal Servers through Native RDP.


In order to be able to launch published applications users have to be added to "Remote Desktop Users" group. This will allow users to access Terminal Servers using Native RDP.


Such restrictions are possible to be made using Windows Firewall with Advanced Settings.

  1. Navigate to the Terminal Server and access Windows Firewall with Advanced Settings

  2. Highlight Inbound Rules and locate inbound rule for Remote Desktop connections

Inbound rule for RDP connections

  1. Right-click this rule and select Properties.

  2. In opened window navigate to "Scope" tab.

  3. Depending on the location of Remote Application Server Gateway select "These IP addresses" checkpoint either in "Local IP address" or in "Remote IP addresses" field and click "Add" button. (The choice should depend on if the Gateway Server is located in internal or external network)


  1. After clicking "Add" button one will be prompted to specify the exact IP addresses from which RDP connection to this Terminal Server will be possible. Please type the IP address of Remote Appication Server Gateway and press "OK" button. In case if your RAS Environment have multiple Gateways please specify IP Addresses of all Gateway Servers

Specify IP addresses

  1. Click "OK" button and Apply setting changes.

Applying this settings to inbound rule for RDP Connection will restrict users from direct access to this terminal server, however will allow Parallels Client users to launch applications published from this server.

PLEASE NOTE: If such changes will be implemented - only users who use Gateway connection mode in Parallels Client will be able to launch published applications.

1d70d1f9c41d01c5f7202a4290e434e1 17333b9b93206d7dd8962eace050749d e672fec7c544b9c6972eababa324d634 e9df64665e7346a300c1e6d8fac71c28 4a54b6f3e325683094bb814b9bc24cd3

Was this article helpful?
Tell us how we may improve it.
Yes No