Loading...
Loading...
A Client Error message will appear as you fail to connect to a horizon desktop:"VDPCONNECT_GATEWAY_ERROR: The connection to the remote computer encountered a gateway error. This could be because the agent is not reachable from the gateway or the protocol service port is blocked by a firewall. If the issue persists, please contact your system administrator." Horizon Client logs and Horizon MKS logs, with the latest cross-platform client release, contain a keyword Blast_Connect_Failure_Alert to aid in expedited failure diagnosis.Log Location: Location of Horizon (VDM) log files (1027744) vmware-mks-<pid>.log 2023-02-24T20:30:38.989Z In(05) blastSocket [BlastSocketClient] BlastSocketClientConnectFailureAlert: Could not connect to Desktop. 2023-02-24T20:30:38.989Z In(05)+ blastSocket Blast_Connect_Failure_Alert: Reason: VDPCONNECT_GATEWAY_ERROR (39) 2023-02-24T20:30:38.989Z In(05)+ blastSocket Blast_Connect_Failure_Alert: host:X.X.X.X port: 8443 httpProxy:null fqdn: uagfqdn 2023-02-24T20:30:38.989Z In(05)+ blastSocket Blast_Connect_Failure_Alert: error: 6 detailed: 0 httpStatus: 502 ClientContext:1516F6B89C0 vmware-horizon-viewclient-<nnn>.txt 2023-02-24T12:30:38.991-08:00 WARN (01) [libsdk] : RMKSWindow::OnConnectionStateChanged:2352: Blast_Connect_Failure_Alert: (16E55639E80) disconnected with VDPCONNECT_GATEWAY_ERROR error: 'VDPCONNECT_GATEWAY_ERROR: The connection to the remote computer encountered a gateway error. This could be because the agent is not reachable from the gateway or the protocol service port is blocked by a firewall. If the issue persists, please contact your system administrator.'.
VDPCONNECT_GATEWAY_ERROR is typically encountered when the Blast Secure Gateway (BSG ) encounters a response where it is unable to connect to the agent. This error will be triggered if BSG does not receive ICMP host/port unreachable or TCP RST when the agent is unreachable/down or a firewall blocks the port. NOTE: The Windows agent firewall does not send ICMP unreachable or TCP RST messages. See Disable stealth mode in Windows
Ensure all basic connectivity checks are performed between the components involved: Horizon Client & agent machine and any devices in its path. Make sure that the hostnames and IP addresses are correct and can be resolved properly.Ensure any global proxy settings are correct and all appropriate ports are open. For the latest Ports guidance please refer to Horizon - Ports and Protocols. - Focus on ensuring the path from the device where your BSG is configured has access to the agent machine and this traffic is correctly routed internally.Ensure that an appropriate client-accessible external URL is configured for the BSG. If you have your environment configured to support a direct connection, you can isolate the behaviour by testing without the BSG set. Broker: Configure the Blast Secure Gateway UAG: Configure Horizon Settings Our Techzone Resources on Understand and Troubleshoot Horizon Connections and Network Ports in Horizon offer greater detail than the brief summary below and are also excellent reference material to ensure stakeholders can be dialled in quickly.
This is a child article of Enhanced Horizon Blast Error Codes with Horizon Client 2303 and Later (91013)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.