
It will either error or give a message that there are no sessions available. Physical machines also do not like to have a user logged into the console and then a connection attempt from Horizon. However, it is worth trying if you are having weird issues not being able to connect to physical workstations with the Horizon agent installed. This has been tested with Horizon 7 only and may not be needed with Horizon 8. With physical machines, I have had to implement a registry key in some environments for connecting successfully to remote physical workstations. Is the agent service running? Is the machine down? If the machine exists on a separate network, do you have network level connectivity to the machine in question? Is NAT in play? Check the status of an agent in the Horizon console VMware Horizon Agent physical machines 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.
#VMWARE HORIZON CLIENT 5.5 3 FULL#
Log Name: Application Source: Application Error Date: 7:56:19 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-3316C8H Description: Faulting application name: vmware-view.exe, version: 8.7, time stamp: 0圆1e1d74c Faulting module name: coreclr.dll, version: 6.0.322.12309, time stamp: 0圆216c9b2 Exception code: 0xc0000005 Fault offset: 0x001bb11b Faulting process id: 0x4c28 Faulting application start time: 0x01d88b4aa3ad647e Faulting application path: C:\Program Files (x86)\VMware\VMware Horizon View Client\vmware-view.exe Faulting module path: C:\Program Files (x86)\dotnet\shared\\6.0.3\coreclr.dll Report Id: b630b850-e465-437d-bfc4-557ea5adbe88 Faulting package full name: Faulting package-relative application ID: Event Xml: "> 1000 0 2 100 0 0x80000000000000 13454 Application DESKTOP-3316C8H vmware-view.exe 8.7 61e1d74c coreclr.dll 6.0.322.12309 6216c9b2 c0000005 001bb11b 4c28 01d88b4aa3ad647e C:\Program Files (x86)\VMware\VMware Horizon View Client\vmware-view.Many organizations are making use of VMware Horizon as the solution to enable a successful, effective, and efficient remote work environment. This error comes seconds before the following error NET Version: 6.0.3 Description: The process was terminated due to an internal error in the. NET Runtime Date: 7:56:17 PM Event ID: 1023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESKTOP-3316C8H Description: Application: vmware-view.exe CoreCLR Version: 6.0.322.12309. Everytime I try to open the remote desktop I get an error saying my connection to the remote desktop has been disconnected.


#VMWARE HORIZON CLIENT 5.5 3 WINDOWS#
I am using a Samsung Go Book 5G with windows 10. I am using the VMware horizon client for a remote desktop.
