VMware View Desktops not connecting

We're running a VMware View 5.2 environment. Hopefully we'll have it upgraded yet this year.

We have always had a small issue with problem desktops and mostly they take care of themselves. The usual message associated with them is an Agent Unreachable.

What we're starting to see is more desktops just showing an error and we drill down on the error it says: "No network communication between the View Agent and Connection Server. Please verify that the virtual desktop can ping the Connection Server via the FQDN."

If I go and look at the virtual desktop itself in the vSphere manager, it shows that it has a bogus 169.x.x.x IP and when I go to the console for that desktop, it shows the NIC as disconnected with a Windows message of cable unplugged.  So the error message is correct that the agent can't talk to the connection  server.

I have checked the NICs on the hosts and they are all fine. While I have a handful in this state, I also have several hundred that are working just fine. I've also checked the DHCP server the there are more than enough IP addresses to hand out and there are no errors on the server. Usually if I remove them and let them rebuild they rebuild OK... although that's not 100% true' occasionally they will come back from the rebuild in that state.

Anyone have a thought on what might be happening?
LVL 28
jhyieslaAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jhyieslaConnect With a Mentor Author Commented:
I think I figured this out.

We were using one connection server, even though I had three because the other two were built much later and my users aren't real conducive to change. Anyway, I wondered if perhaps that server was just getting over run, even though I have it sized well. I found a way to point the zero client devices at one of the other connection servers and now I have about 30-40% of them going to the other two.  Ever since making that change, the number of problem desktops I have had dropped significantly from around 20-40/day to maybe 1-2.  This has remained consistent ever since I made the change.
0
 
Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
i had something similar a long time ago
remove the horizon agent and vmware tools; then reinstall vmware tools then the agent
create a new snapshot and try that for the pool

also want to do a sanity check to make sure the virtual network card is connected else it will show in windows as 'cable unplugged'
0
 
jhyieslaAuthor Commented:
I've already checked the virtual NICs and everything there appears to be OK. Is there somewhere to check outside of the hosts?  As I said I have several hundred desktops running across 5 hosts and mostly they work OK. I don't disagree with your initial suggestion, but this is happening across at least three separate pools so I doubt that it's a pool issue. Plus one of the pools was rebuilt in the last week.

I am looking at my desktops right now and, although I am running less now than in the heat of the day, I have none showing the error from lack of network connectivity.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Seth SimmonsSr. Systems AdministratorCommented:
but this is happening across at least three separate pools so I doubt that it's a pool issue

might not be the pool itself; could be the golden image it is using
0
 
jhyieslaAuthor Commented:
each pool has it's own master
0
 
jhyieslaAuthor Commented:
Found solution myself, but gave some points because the solution given seemed like a very reasonable approach.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.