At that point, you need to figure out why the Horizon Connection server cannot “see” the agent. If the agent is unreachable, the client will never be able to connect. Note what the status is for the Desktop machine configured for the desktop pool. Next, look at the specific Desktop pool > Machines.

If you have already ruled out the obvious reasons for connectivity issues, such as changing a firewall rule and other clients are connected just fine, you most likely do not have a global issue with the environment. There are a few obvious things to check when users have VMware Horizon Client error couldn’t connect to server. Horizon client connecting to UAGs VMware Horizon Client Error Couldn’t Connect to Server In the first image, we have a Horizon Client connecting directly to Horizon Connection Servers. How does traffic flow from the outside to your Horizon desktop? Are UAGs in play, Load Balancers, VIPs, multiple Horizon connection servers? Also, what is the state of the agent on the endpoint machine.Īlso, just basic troubleshooting methodologies here, but was the target machine working and then stopped? What has changed, anything? Note the architecture of the below diagrams. In order to troubleshoot Horizon effectively, you need to know your architecture in the Horizon environment. Let’s take a look at VMware Horizon Client Error couldn’t connect to server and see some common troubleshooting steps you may need to take to resolve your connectivity issue. With that being said, issues may arise from time to time where your end-users may not be able to connect to the target machine in their desktop pool, whether virtual or physical. VMware Horizon is able to connect remote workers to VDI environments and even physical machines. Many organizations are making use of VMware Horizon as the solution to enable a successful, effective, and efficient remote work environment.

Vmware horizon login