How Are Commander VM Access Proxy Sessions Connected?

Title

The image below illustrates the port requirements necessary for successful connections between end-users and target VMs using the VM Access Proxy. The details in this article compliment those in the Set Up VM Access Proxies documentation, by providing a step-by-step walkthrough of how the sessions are established.

The Service Portal on the Commander application server is published through the firewall on TCP port 443. When a Service Portal user logs in and requests a secure connection to one of the VMs inside the network, the following takes place:

Commander responds by sending the user's browser a token identifying the request and the URL configured for the VM Access Proxy, as shown on the Integrations page in Commander.

The user's browser next creates a session to the VM Access Proxy, published through the firewall on TCP ports 443 and 8443.
The VM Access Proxy contacts Commander on TCP port 443 with the token and requests the connection details. The response provides the target VM's addresses and the protocol to use for the session.
If the protocol is:

RDP: The VM Access Proxy establishes the session to the cloud account, creating an in-browser RDP session over TCP port 8443 between the VM Access Proxy and the user's browser.
SSH: The VM Access Proxy establishes the session to the guest operating system, creating an in-browser SSH session over TCP port 8443 between the VM Access Proxy and the user's browser.
VNC: The VM Access Proxy establishes the session to the cloud account, creating an in-browser VNC session over TCP port 8443 between the VM Access Proxy and the user's browser.
VMware console: The VM Access Proxy proxies the session between the cloud account (vCenter server) and the user's browser over TCP port 443.
SCVMM console: The VM Access Proxy proxies the session between the cloud account (Hyper-V server) and the user's browser over TCP port 8443.

In all connection scenarios, routes must exist between Commandxer and the VM Access Proxy. For vCenter and SCVMM, routes must exist between Commander, the VM Access Proxy, and the host (either Hyper-V or ESXi). For RDP, SSH, and VNC connections, routes must exist between Commander, the VM Access Proxy, and the target VM.

Important! If users will access their VMs from inside and outside of the cloud account (vCenter/SCVMM) network, DNS must be configured with addresses that will resolve correctly in both zones. Internal requests must get a responses with private addresses, external requests must get responses with public addresses.

Was this helpful?

Support Hub

Product

Snow Commander

Solution Area

VM Access Proxy

Deployment type

On-premises

Visibility

Guest

URL Name

Detailed-Commander-VM-Access-Proxy-Networking

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Related Articles

Please wait...

Case id: 00001065