Lost connectivity in VMware view 4.6

[Ryszard]

I have a user whose view session work fine on any system but hers. Had been working fine. Uninstalled and reinstalled the View Client with no effect. Does not matter PCoIP or RDP the user disconnects after a few seconds 15 to 25 seconds of use. RDP to the VM works just fine. Others users on the same View session suffer the same fate. So whatever it is on the client side. Any ideas?

[Benedykt]

When connecting via PCoIP or RDP all the way through the View client, do you obtain just a black screen and then it disconnects? Or can you actually log in and influence the desktop previous to it kicks you off?

[MahaGuru]

Using View Both RDP and PCoIP session last for a short period of time with full functionality but simply drop. No message, no error whole session just goes spoof .Normal RDP to the same VM works fine.

[Neutrals]

I have been experiencing the same matter where you can log on, by means of pcoip, and then following a few seconds drop connectivity.

The problem seems random at most excellent considering as it’s only a handful of people who have been experiencing this. I have search through the logs, nevertheless there is nothing out of the ordinary

[Gunilla]

check my log

18:36:17,955 INFO  <Main Thread> [wswc] Windows Client started
18:38:10,458 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_PCOIP - VMware View Client PCoIP Interaction Handler' loaded, version=4.6.0 build-366101, buildtype=release
18:38: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
18:38: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
18:38:11,411 INFO  <DesktopWindow> [wswc_ui] Connecting client to agent via socket channel
18:38:50,738 INFO  <MessageFrameWorkDispatch> [wswc] VMware View Windows Client received shutdown signal
18:38:53,144 INFO  <Main Thread> [wswc] VMware Windows Client stopped (exit code 0)

[Czeslaw]

I don’t think there is any trouble with view client
What happens if you carry out a clean boot of the exaggerated system and then attempt the View Client?

[GeforceUser]

We've had the precise same matter and it turned up to be a recognized matter with 4.6 and Zero clients. So not convinced if this would be appropriate to you nevertheless 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)

[Proteus]

Thanks everyone for helping me throughout my difficulty. I have contacted VMware support system and I am waiting for their response.