The Virtual Access Suite is a product that contains many different sub products that all communicate with one another. This article discusses all the ports used in the Virtual Access Suite and how they are used. I guess it goes without saying that these ports should be open for smooth sailing. The image below shows what components can exist in a VAS infrastructure and how they interact.

Data Collector Service

This is a Windows service runs inside each managed desktop and VAS-enabled Terminal Server and communicates back and forth with the Connection Broker. It listens for Connection Broker service connections on 5203/tcp. When the Provision Tools for the Managed Desktop is installed onto a desktop, a Windows Firewall port exception rule is automatically added to allow incoming connections on this port.

Connection Broker

This service communicates back and forth with the Data Collector running inside each managed desktop and/or VAS-enabled Terminal Server. It listens for Data Collector service connections on 5201/tcp. It also listens for incoming client connection requests on a configurable port (default is 8080/tcp). Optionally, the Connection Broker can be configured to require SSL encryption (using 443/tcp as a default).

Password Management Service

This service accepts SSL-protected client password reset requests on a configurable port (default is 443/tcp).

Web Interface

The Web Interface, being a web service, uses HTTP and/or HTTPS application protocols. Although the default port numbers are 80/tcp and 443/tcp respectively, any ports can be used.

SSL Gateway

The Provision Networks SSL Gateway acts as an SSL proxy for Connection Broker, Web Interface, and RDP communications and by default listens on 443/tcp.

RDP	Microsoft RDP (Remote Desktop Protocol) is used for connections from VAS Clients to Terminal Servers and/or managed desktops. RDP listens on 3389/tcp by default.

This pretty much covers the default ports that can be found in a VAS infrastructure. Again, all of these ports need to be open for smooth sailing. Network connectivity issues have a big impact on proper VAS operations. One of the easiest ways to check for proper connectivity is to use good old Telnet. See the VAS Infrastructure diagram to determine from where to where you need to check the connectivity.

That’s it for now. Remember, if you need help, just go to our forums at https://www2.provisionnetworks.com/forums/Default.aspx.

You can leave a response, or trackback from your own site.