Rendezvous v1 Connections fail after setting PortNumber argument on VDA Command Line Installs

Rendezvous v1 Connections fail after setting PortNumber argument on VDA Command Line Installs

book

Article ID: CTX692089

calendar_today

Updated On:

Description

After installing VDA with a custom port number with the commandline argument:  /portnumber NNNN where NNNN is the port number, and running xaxdcloudproxy.exe -VDAPORT NNNN on the cloud connectors, Rendezvous v1 connections to VDA fail.

Network traces show that Cloud Connector attempts to reach iLaunch interface at port 80 still 

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Set the below reg key on each cloud connector.

NOTE: this setting will persist during cloud connector updates.

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XaXdCloudProxyPersist
Name:WorkerPortNumber
Type:REG_DWORD
Value: PORT_NUMBER_CUSTOMIZED

Problem Cause

When the listener port on the VDA is customized, VDA communicates to DDC about the customized port during registration and DDC then uses it to communicate with the VDA. However, this only applies to any calls from the DDC i.e. DDC->CC->VDA.

Rendezvous launch traffic does not originate on the DDC, it is coming from NGS i.e. NGS->CC->VDA. In this case CC does not know about VDA's listener. The registry value WorkerPortNumber can be used in these scenarios

Powered by Wolken Software