VMware View Client with dual Virtual NICs unable to connect to virtual desktop

Rate this Article
Average: 1 (1 vote)

August 27, 2018

Last modified: 09/03/2023, 6:12 pm

Knowledge Base Article Troubleshooting Performance Third Party Enhancements Zero Clients

Scenario

A VMware View Client with dual virtual NICs configured may not be able to connect to the virtual desktop. 

Note: this article does not apply to PCoIP Zero Clients.

Dual Virtual NICs Configured on the View Client

 

Cause

If the client has been configured with 2 virtual NICs, the VMware View Agent will seem to randomly pick the NIC to bind to and can result in the client not being able to connect to the VMware View virtual desktop. 

 

Resolution:

If the Guest operating system has more than one virtual NIC, you must configure the subnet that the View Agent uses. To accomplish this, you must set the value of the HKEY_LOCAL_MACHINE\Software\VMware, Inc\VMware VDM\Node Manager\subnet registry key to  n.n.n.n/m (REG_SZ), where n.n.n.n is the TCP/IP subnet and m is the number of bits in the subnet mask.

For more details see VMware KB# 1026498.

 

See also:

Incorrect network configuration on the VMware View Server can also impact clients (VMware View Client and PCoIP Zero Clients) from connecting - see  VMware KB# 1026498 for more detail.