Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
A Client Error message will appear as you fail to connect to a horizon desktop:"VDPCONNECT_CONN_TIMEDOUT: The connection to the gateway or the remote computer could not be established in a reasonable time period. This could be because the gateway or the remote computer is not reachable, not responding, 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. These files are included in a Horizon Client Diagnostic BundleLog Location: Location of Horizon (VDM) log files (1027744) drive\%username%\AppData\Local\Temp\vmware-mks-<pid>.log 2023-01-18T19:22:36.661Z In(05) blastSocket [BlastSocketClient] BlastSocketClientConnectFailureAlert: Could not connect to Desktop. 2023-01-18T19:22:36.661Z In(05)+ blastSocket Blast_Connect_Failure_Alert: Reason: VDPCONNECT_CONN_TIMEDOUT (33) 2023-01-18T19:22:36.661Z In(05)+ blastSocket Blast_Connect_Failure_Alert: host:X.X.X.X port: 22443 httpProxy:null fqdn:null 2023-01-18T19:22:36.661Z In(05)+ blastSocket Blast_Connect_Failure_Alert: error: 6 detailed: 10060 httpStatus: 0 ClientContext:2C79C723260 %ProgramData%\VMware\logs\vmware-horizon-viewclient-<nnn>.txt 2023-01-18T11:22:36.662-08:00 WARN (01) [libsdk] : RMKSWindow::OnConnectionStateChanged:2346: Blast_Connect_Failure_Alert: (216A2509820) disconnected with VDPCONNECT_CONN_TIMEDOUT error: 'VDPCONNECT_CONN_TIMEDOUT: The connection to the gateway or the remote computer could not be established in a reasonable time period. This could be because the gateway or the remote computer is not reachable, not responding, or the protocol service port is blocked by a firewall. If the issue persists, please contact your system administrator.'.
VDPCONNECT_CONN_TIMEDOUT, in most scenarios, translates to a Windows Sockets Error Code of - WSAETIMEDOUT. 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 encounters a timeout while connecting to a peer. due to the agent side firewall blocking Blast port 22443 or an agent host being down Typically, an ICMP WSAETIMEDOUT response is received because communication is not established in a timely fashion.
The VDPCONNECT_CONN_TIMEDOUT error typically indicates that a socket connection attempt has not been completed in a timely manner. 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 typos 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, and telnet.Check for delays utilizing network tools such as tracert.Verify DNS Resolution utilizing tools such as nslookup .Check network device settings: Verify that any firewall, VPN, load balancer, and network device in the path of each component can effectively route client traffic. If this is isolated to a particular client machine and the 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 the 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.If the issue is intermittent, focus on hardware, configuration, or congestion problems. Tools like WireShark can aid the investigation.
This is a child article of Enhanced Horizon Blast Error Codes with Horizon Client 2303 and Later (91013)