OPERATIONAL DEFECT DATABASE
...
...
A Client Error message will appear as you fail to connect to a horizon desktop:"VDPCONNECT_HOST_UNREACHABLE: The local computer is unable to reach the gateway or the remote computer while attempting a connection. This could be because the gateway or the remote computer is down or not responding. 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-28T03:34:11.246Z In(05) blastSocket [BlastSocketClient] BlastSocketClientConnectFailureAlert: Could not connect to Desktop. 2023-02-28T03:34:11.246Z In(05)+ blastSocket Blast_Connect_Failure_Alert: Reason: VDPCONNECT_HOST_UNREACHABLE (38) 2023-02-28T03:34:11.246Z In(05)+ blastSocket Blast_Connect_Failure_Alert: host:null port: 22443 httpProxy:null fqdn:null 2023-02-28T03:34:11.246Z In(05)+ blastSocket Blast_Connect_Failure_Alert: error: 14 detailed: 113 httpStatus: 0 ClientContext:5649FB70A3D0 vmware-horizon-viewclient-<nnn>.txt 2023-02-27T15:56:35.528+08:00 WARN (01) [libsdk] : RMKSWindow::OnConnectionStateChanged:2352: Blast_Connect_Failure_Alert: (22AF1B202A0) disconnected with VDPCONNECT_HOST_UNREACHABLE error: "VDPCONNECT_HOST_UNREACHABLE: The local computer is unable to reach the gateway or the remote computer while attempting a connection. This could be because the gateway or the remote computer is down or not responding. If the issue persists, please contact your system administrator."
VDPCONNECT_HOST_UNREACHABLE, in most scenarios, translates to a Windows Sockets Error Code of WSAEHOSTUNREACH. Please see Windows Sockets Error Codes for a full description of this return code.Scenarios that could trigger this error include, but are not limited to, the Horizon Client connection failing because no route was found to the designated target. Typically, a ICMP host unreachable response is received because the host is not responding
The VDPCONNECT_HOST_UNREACHABLE error typically indicates that a socket connection attempt has failed because the host is unreachable. Here are some steps to troubleshoot this error:Client Side - End User Perspective: Do you have general internet or intranet connectivity on the device?Are other corporate resources available and accessible?Can you reach the address configured for your horizon client via a Browser?Is the address correct ? No typo's or partially complete addresses? Troubleshooting Steps for a Horizon Administrator: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.Check the network connection utilizing tools such as ping , telnet.Verify DNS Resolution utilizing tools such as nslookup .Check network device settings: Verify that any firewall, load balancer, every network device in the path of each component can effectively route client traffic.If this is isolated to a particular client machine and connection is successful with different machines on the same network, verify the Clients guest o/s proxy configurations, local firewall and antivirus setups.Similarly , 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.Check all the relevant hardware involved in the connection path utilizing event viewer and system logs to ensure no faulty cable, network port or system hardware on the client or along the connection path is contributing to the issue.
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.
