The connection to the remote computer ended.

[vivekrishna]

In the events showing The pending session on machine xxxx for user xxxx has expired

-----  Its a linked clone dedicated pool. All other machines are able to get connected, only one user is having the issue connecting the machine.

------- He is getting the :The connection to remote computer ended" error message.

No blocking in Network side, all ports are open to this same subnet.

Thanks, what can be the reason ?

[surajr04]

Is the user trying to connect from internal or external network?

Which Protocol he is trying?

Are you using UAG or Security server

[vivekrishna]

Through UAG

[surajr04]

There are several reason

Session Persistence issue in LB if there any in front of UAG

If UAG HA is configured, it can be due to misconfiguration.

Try to bypass external LB and test from client machine in same subnet as UAG and check if the issue is reproducible.

[BarryUWSEFS]

We had some similar issues after switching from Security server to UAG last year. Had a case open with VMware but never really got a definitive answer. Out of a 100 or more users 2 or 3 had issues. With one user it only happened from his Mac, when he used a windows client it worked fine, so that was the work around for him. With another user it was fixed by updating his Horizon client to the latest version. Another user was able to use the HTML client to get around it. Pretty random solutions but the initial issue for all was the same, the events showing the user was connected then within a minutes or so disconnected, expired like you see. From the end user perspective they never were connected.

[surajr04]

BarryUWSEFS​ from description, it seems it was client related issue. However, it would have been worth running wireshark on impacted machine and tcpdump on UAG and also make sure the Log Level on the UAG is set to Debug and reproduce the issue.

[BarryUWSEFS]

I was having some issues getting cooperation from the end user once a work around was found! The only thing that VMware suggested to look at this value on the VM: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\userinit

and change it from C:\Windows\system32\userinit.exe,"C:\Program Files\VMware\VMware View\Agent\bin\vmlm_helper.exe","C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe",0x80004005

to C:\Windows\system32\userinit.exe, "C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe",

Apparently the helper was suspect. We did change that later on master mage and have not had any issues since.