VMware View 4.6 Client lost connectivity ( VM's OK)

[kkish]

I have a user who's view session work fine on any system but hers.  Had been working fine. Uninstaleld and reinstalled the VIew Clinet with no effect. Does not matter PCoIP or RDP the user discoonects after a few seconds ~10 to 20 seconds of use.   RDP to the VM works just fine.  Ohers users on the same View session suffer  the same fate. So what ever it is is on the client side.  Any ideas?  

[Villag3Idiot]

When connecting via PCoIP or RDP through the View client, do you get just a black screen and then it disconnects? Or can you actually log in and manipulate the desktop before it kicks you off?

Im guessing that connecting through Mircosoft´s RDP client works fine?

[Villag3Idiot]

have you checked through the view client log files on this PC for anything that looks out of the ordinary?

Check this KB for the location of the log files...

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102774...

[kkish]

Thaks to the log fiel pointer that may be of use... When they come in ot he office wil look..

[kkish]

Using View BOth RDP and PCoIP session last for a short period of tiem with full functionality but simply drop. No mesage no erro whole session jsut goes poof ..

Normal RDP to the same VM works fine ...Stable etc.

[KipsDK]

Has anyone found a solution to this.

Iv been experiencing the same issues where you can log on, using pcoip, and then after a few seconds/minutes lose connectivity. 

The problem seems random at best seeing as its only a handful of people who have been experiencing this. Iv searched through the logs, but there is nothing out of the ordinary.

[WilliamReid]

Hi there,

I've seen this issue and in some cases it's due to a wrong userinit entry on the agent.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102897...

Wm

[kkish]

The reg entry was ok and the same as other workig VM's.  Worht noting that the client can be used from a different host system ok so the VM side is OK.

The cleint log fiel on the brokne Win system ->

14:35:16,711 INFO  <14376> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=15520, buildtype=release, usethread=0, closeafterwrite=0
14:35:16,836 INFO  <14376> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=15520, buildtype=release, usethread=0, closeafterwrite=0
14:35:17,164 INFO  <DesktopWindow> [wswc_ui] Connecting client to agent via socket channel
14:35:56,527 INFO  <MessageFrameWorkDispatch> [wswc] VMware View Windows Client received shutdown signal
14:35:58,324 INFO  <Main Thread> [wswc] VMware Windows Client stopped (exit code 0)
14:36:03,684 INFO  <13244> [MessageFrameWork] Program 'wswc - VMware View Client' started, version=4.6.0 build-366101, pid=14212, buildtype=release, usethread=1, closeafterwrite=0
14:36:03,699 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_command - VMware View Connection Server Command Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,699 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_http - VMware View Client HTTP Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,699 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rdp - VMware View RDP Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,715 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rsa - VMware View RSA Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,715 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_tunnel - VMware View Secure Tunnel Client' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,715 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_ui - VMware View Client UI handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,715 INFO  <logloaded> [MessageFrameWork] Plugin 'wssm_uimanager - VMware View Framework UI Host' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,730 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_usb - VMware View Virtual USB Device Service' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,730 INFO  <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=4.6.0 build-366101, buildtype=release
14:36:03,730 INFO  <Main Thread> [wswc] Windows Client started
14:36:26,264 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_PCOIP - VMware View Client PCoIP Interaction Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:36:26,764 INFO  <15700> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=15504, buildtype=release, usethread=0, closeafterwrite=0
14:36:26,904 INFO  <15700> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=15504, buildtype=release, usethread=0, closeafterwrite=0
14:36:27,264 INFO  <DesktopWindow> [wswc_ui] Connecting client to agent via socket channel
14:37:13,283 INFO  <MessageFrameWorkDispatch> [wswc] VMware View Windows Client received shutdown signal
14:37:15,455 INFO  <Main Thread> [wswc] VMware Windows Client stopped (exit code 0)
14:37:17,893 INFO  <16280> [MessageFrameWork] Program 'wswc - VMware View Client' started, version=4.6.0 build-366101, pid=11184, buildtype=release, usethread=1, closeafterwrite=0
14:37:17,908 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_command - VMware View Connection Server Command Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,908 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_http - VMware View Client HTTP Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,908 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rdp - VMware View RDP Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,924 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rsa - VMware View RSA Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,924 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_tunnel - VMware View Secure Tunnel Client' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,924 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_ui - VMware View Client UI handler' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,940 INFO  <logloaded> [MessageFrameWork] Plugin 'wssm_uimanager - VMware View Framework UI Host' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,940 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_usb - VMware View Virtual USB Device Service' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,940 INFO  <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=4.6.0 build-366101, buildtype=release
14:37:17,955 INFO  <Main Thread> [wswc] Windows Client started
14:39:10,458 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_PCOIP - VMware View Client PCoIP Interaction Handler' loaded, version=4.6.0 build-366101, buildtype=release
14:39:10,942 INFO  <13084> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=13524, buildtype=release, usethread=0, closeafterwrite=0
14:39:11,067 INFO  <13084> [vmware-remotemks] Program 'vmware-remotemks - VMware Workstation Remote MKS' started, version=7.1.0 build-340165, pid=13524, buildtype=release, usethread=0, closeafterwrite=0
14:39:11,411 INFO  <DesktopWindow> [wswc_ui] Connecting client to agent via socket channel
14:39:50,738 INFO  <MessageFrameWorkDispatch> [wswc] VMware View Windows Client received shutdown signal
14:39:53,144 INFO  <Main Thread> [wswc] VMware Windows Client stopped (exit code 0)

Is not verry informative...
 

[WilliamReid]

Hi there,

Doesn't look like there is an issue with the View client from what you're posting, it's starting and exiting cleanly.

What happens if you perform a cleanboot of the affected system and then try the View Client?

Wm

[alelondon]

We've had the exact same issue and it turned up to be a known issue with 4.6 and Zero clients. So not sure if this would apply to you but in my case it was OK in 4.5 and got the symptoms in 4.6 (only on Zero clients with the Teradici chip though)

Cheers