ajohnsonNBT
Contributor
Contributor

View disconnect error

I have been through about 3 months of troubleshooting on this and still have no resolution to it. Has anyone or is anyone experiencing issues with disconnects from thin clients back to virtual XP builds? The disconnects are completely random, all my software is up to date on all vm's. Any advice?

DISCONNECTED:Server:cn=9fc97162-8583-46ce-8799-e40badddd7a9,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=wwvxp1-pool,ou=server groups,dc=vdi,dc=vmware,dc=int;DNS:WWVXP21.NBT.local;IP:10.100.1.16;USER:NBT\user;USERDN:cn=s-1-5-21-416116911-1437686249-1819828000-1924,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int;BROKERUSERSID:S-1-5-21-416116911-1437686249-1819828000-1924;</log>

<log date="2009-09-01" time="13:11:08,000" type="INFO " module="PoolManager" thread="PoolManager">User NBT\user disconnected from machine WWVXP21 for desktop wwvxp1-pool - session allocated at September 1, 2009 8:07:08 AM EDT, connected for 303 mins 55 secs</log>

<log date="2009-09-01" time="14:17:00,139" type="INFO " module="WinAuthFilter" thread="TP-Processor2">(SESSION:75E4C82ADE5988D8748B6B788B30F1E0 user) User NBT\user has successfully authenticated to VDM</log>

<log date="2009-09-01" time="14:17:00,139" type="INFO " module="Audit" thread="TP-Processor2">(SESSION:75E4C82ADE5988D8748B6B788B30F1E0) BROKER_LOGON:USER:NBT\user;USERSID:S-1-5-21-416116911-1437686249-1819828000-1924;USERDN:CN=S-1-5-21-416116911-1437686249-1819828000-1924,CN=ForeignSecurityPrincipals,DC=vdi,DC=vmware,DC=int;</log>

<log date="2009-09-01" time="14:17:08,280" type="INFO " module="Audit" thread="TP-Processor2">(SESSION:75E4C82ADE5988D8748B6B788B30F1E0;C4650A46E0921C4136AF566C4F1812FA) ALLOCATED:Server:cn=9fc97162-8583-46ce-8799-e40badddd7a9,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=wwvxp1-pool,ou=server groups,dc=vdi,dc=vmware,dc=int;USER:NBT\;BROKERUSERSID:S-1-5-21-416116911-1437686249-1819828000-1924;USERDN:CN=S-1-5-21-416116911-1437686249-1819828000-1924,CN=ForeignSecurityPrincipals,DC=vdi,DC=vmware,DC=int;</log>

<log date="2009-09-01" time="14:17:08,389" type="INFO " module="Audit" thread="PoolManager">PENDING:Server:cn=9fc97162-8583-46ce-8799-e40badddd7a9,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=wwvxp1-pool,ou=server groups,dc=vdi,dc=vmware,dc=int;DNS:WWVXP21.NBT.local;IP:10.100.1.16;USER:NBT\user;USERDN:cn=s-1-5-21-416116911-1437686249-1819828000-1924,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int;BROKERUSERSID:S-1-5-21-416116911-1437686249-1819828000-1924;</log>

<log date="2009-09-01" time="14:17:37,015" type="INFO " module="Audit" thread="PoolManager">RECONNECTED:Server:cn=9fc97162-8583-46ce-8799-e40badddd7a9,ou=servers,dc=vdi,dc=vmware,dc=int;Pool:cn=wwvxp1-pool,ou=server groups,dc=vdi,dc=vmware,dc=int;DNS:WWVXP21.NBT.local;IP:10.100.1.16;USER:NBT\user;USERDN:cn=s-1-5-21-416116911-1437686249-1819828000-1924,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int;BROKERUSERSID:S-1-5-21-416116911-1437686249-1819828000-1924;</log>

0 Kudos
7 Replies
JMHorne
Contributor
Contributor

We've just start seeing this exact same issue here - did you end up having any luck resolving the issue? I notice that this is from nearly 2 months ago now...

0 Kudos
mikebarnett
VMware Employee
VMware Employee

This issue may be related to a bug that was found in View 3.1 that caused random disconnections from desktops. Upgrading to View 3.1.1 (the Connection Server is the most important upgrade for this bug) resolves that issue.

Let me know if it works.

Mike

Twitter: @MikeBarnett_
0 Kudos
JMHorne
Contributor
Contributor

We are using 3.1.1 build-175957 - was the bug resolved in this version, or later?

0 Kudos
mikebarnett
VMware Employee
VMware Employee

That particular bug was resolved in View 3.1.1.

What clients are being used to connect to your View environment and are they connecting from inside our outside?

Mike

Twitter: @MikeBarnett_
0 Kudos
JMHorne
Contributor
Contributor

The users are simply using the View Client application on existing PCs (XP Platform) with a customised setup (client as shell) - we are currently trialing the software. They are accessing the system through our internal LAN - in the same L3 domain as the connection server/vCenter. The users are told they have lost their connection after a period of time - from a couple of minutes to twenty-five mintues. It seems completely random. From the View Con Server events it seems as if the users are ending their session (at least that's how the log reads - I'm not sure what it's telling me tbh!) but this is not the cas.

We haven't seen the issue up until this point, having used the setup for a couple of weeks prior to it occurring.The only change has been the reduction of the automated pool's desktop sources (by 1 desktop) and the creation of another pool containing 1 desktop source (this is to test a persistent setup for one user). Could any of this changes cause an issue? Would is be best to destroy the pool and recreate it with the lower number of desktop sources?

0 Kudos
mikebarnett
VMware Employee
VMware Employee

To be honest, it doesn't sound like any of those things would have any effect on the connection issue.

Is your connection server running on a vSphere VM?

Can you confirm the versions of the View Client, Agent and Connection Server components?

Mike

Twitter: @MikeBarnett_
0 Kudos
JMHorne
Contributor
Contributor

The Virtual Center and view connection servers are seperate VMs on the same ESXi hostand managed through the Virtual Center instance.

Versions:

View Connection Server 3.1.1-175957

View Agent 3.1.1-175957

View Client 3.1.1-175957

View Composer 1.1.0-161885

vCenter 2.5.0 build 119598

0 Kudos