...
A Client Error message will appear as you fail to connect to a horizon desktop:"VDPCONNECT_CONN_ACCESS_DENIED: The connection to the gateway or the remote computer was denied access, perhaps by the local host 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-07T01:45:42.844Z In(05) blastSocket [BlastSocketClient] 2023-02-24T20:47:58.316Z In(05) blastSocket [BlastSocketClient] BlastSocketClientConnectFailureAlert: Could not connect to Desktop. 2023-02-24T20:47:58.316Z In(05)+ blastSocket Blast_Connect_Failure_Alert: Reason: VDPCONNECT_CONN_ACCESS_DENIED (36) 2023-02-24T20:47:58.316Z In(05)+ blastSocket Blast_Connect_Failure_Alert: host:X.X.X.X port: 22443 httpProxy:null fqdn:null 2023-02-24T20:47:58.316Z In(05)+ blastSocket Blast_Connect_Failure_Alert: error: 6 detailed: 10013 httpStatus: 0 ClientContext:1E975826130 vmware-horizon-viewclient-<nnn>.txt 2023-02-24T12:47:58.318-08:00 WARN (01) [libsdk] : RMKSWindow::OnConnectionStateChanged:2352: Blast_Connect_Failure_Alert: (22FA63EF5A0) disconnected with VDPCONNECT_CONN_ACCESS_DENIED error: 'VDPCONNECT_CONN_ACCESS_DENIED: The connection to the gateway or the remote computer was denied access, perhaps by the local host firewall. If the issue persists, please contact your system administrator.'.
VDPCONNECT_CONN_ACCESS_DENIED, in most scenarios, translates to a Windows Sockets Error Code of WSAEACCES (10013). Please see Windows Sockets Error Codes for a full description of this return code.A local firewall rule blocks the agent's IP address or port, causing errors on Windows. Essentially, an attempt was made to access a socket in a way forbidden by its access permissions.
The VDPCONNECT_CONN_ACCESS_DENIED error is typically seen when the Horizon agent software returns an error forbidden when establishing a connection to network concerns. Here are some steps to troubleshoot this error:Client Side - End User Perspective: Ensure your antivirus and windows firewall has appropriate exceptions for Horizon. Antivirus executable exclusion list for VMware Horizon (2082045)If you have an active proxy or VPN on your client machine, test without it. Troubleshooting Steps for a Horizon Administrator: For a full overview of considerations with Anti-Virus and Horizon, please see our TechZone Whitepaper on the topic: Antivirus Considerations in a VMware Horizon Environment Ensure all basic connectivity checks are performed between the components involved: Horizon Client & agent machine and any devices in its path. 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.Utilize tools such as WireShark to identify if there is excessive retransmission of data which can lead to this event.
This is a child article of Enhanced Horizon Blast Error Codes with Horizon Client 2303 and Later (91013)