Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Issue with View and NIC connectivity

Posted on 2016-10-19
1
Medium Priority
?
64 Views
Last Modified: 2016-10-21
We have a View 5.2 environment with 5 ESXi hosts. We have had something new happening. We will get throughout the day a number of View desktops that go into the Problem Desktop queue. When we check them they will almost all have the same issue. They have a 169.x.x.x IP and when the look at the NIC, it says to connect on power on, but the Connected checkbox is not checked. Checking that will sometimes fix the issue, other times not and then we have to refresh them, which usually works.

I have determined that this is happening on only two of the 5 hosts. I have looked at those hosts and their network cards and the settings all look OK.  I've also checked their connections to the main switch and those look OK as well. Plus we do have a large number of desktops running on each host successfully.  I do see, on at least a couple I've looked at, a message in the Events log for the machine. It reads that there is a warning on the desktop on this host in this site that Virtual device Ethernet0 will start disconnected.
0
Comment
Question by:jhyiesla
1 Comment
 
LVL 28

Accepted Solution

by:
jhyiesla earned 0 total points
ID: 41853829
I think I have found the problem. It appears that those two hosts are running out or free network ports for the vswitch. I found some machines that were hung logging off Windows and after restarting them so that they went into a provisioned state instead of a connected state, the number of problem desktops just disappeared. I'm going to schedule a time to increase the available network ports on all of the hosts.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…
Suggested Courses

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question