Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting virtual machine network connection issues (1003893)

Last Updated: 5/4/2023Categories: TroubleshootingTotal Views: 181356Language:
SpanishEnglish

76 like this article

Subscribe to get an email
newsletter with new updates

76 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Virtual machines fail to connect to the network

There is no network connectivity to or from a single virtual machine

You cannot connect to the Internet

A TCP/IP connection fails to and from a single virtual machine

You may see one or more of the following errors:

Destination Host Unreachable

Network error: Connection Refused

Network cable is unplugged

Ping request could not find host (IP address/hostname). Please check the name and try again.

Unable to resolve target system name (IP address/hostname).

Resolution

Process to troubleshooting virtual machine network connection issues:

Important Note: Validate that each troubleshooting step below is true for your environment. The steps provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

Ensure that the Port Group name(s) associated with the virtual machine's network adapter(s) exists in your vSwitch or Virtual Distributed Switch and is spelled correctly. If not, correct it using Edit Settings on the virtual machine and ensure that the Connected checkbox is selected.

Note: On a virtual standard switch, virtual machines cannot be placed on a vmkernel port group. Standard switches require that each vmkernel has its own port group.

Ensure that the virtual machine has no underlying issues with storage or it is not in resource contention, as this might result in networking issues with the virtual machine. You can do this by logging into ESX/ESXi or Virtual Center/vCenter Server using the VI/vSphere Client and logging into the virtual machine console. For more information, see Troubleshooting a virtual machine that has stopped responding (1007819).

Note: If you are experiencing network connectivity issues with the ESX/ESXi host or with multiple virtual machines, see ESX/ESXi hosts have intermittent or no network connectivity (1004109).

Verify that the virtual network adapter is present and connected. For more information, see Verifying virtual network adapter is present and connected to the virtual machine (1003786).

Verify that the networking within the virtual machine's guest operating system is correct. For more information, see Verifying the networking within a Windows based guest operating system (1003899) for Windows and Verifying the networking within a Linux based guest operating system (2022022) for Linux.

Verify that the TCP/IP stack is functioning correctly. For more information, see Troubleshooting virtual machine TCP/IP connection issues (1007842).

If this virtual machine was converted from a physical system, verify that there are no hidden network adapters present. For more information, see Networking Error: IP address already assigned to another adapter (1179).

Verify that the port group of the virtual machine is configured with two vNICs to eliminate a NIC or a physical configuration issue. To isolate a possible issue:

If the load balancing policy is set to Default Virtual Port ID at the vSwitch or vDS level:

Leave one vNIC connected with one uplink on the vSwitch or vDS, then try different vNIC and pNIC combinations until you determine which virtual machine is losing connectivity.

If the load balancing policy is set to IP Hash:

Ensure the physical switch ports are configured as port-channel. For more information on verifying the configuration on the physical switch, see Enable EtherChannel / Link Aggregation Control Protocol (LACP) in ESXi/vCenter and Example Configuration of LACP on VMware, Cisco, and HP switches

Shut down all but one of the physical ports the NICs are connected to, and toggle this between all the ports by keeping only one port connected at a time. Take note of the port/NIC combination where the virtual machines lose network connectivity.

You can also check esxtop output using the n option (for networking) to see which pNIC the virtual machine is using. Try shutting down the ports on the physical switch one at at time to determine where the virtual machine is losing network connectivity. This also rules out any misconfiguration on the physical switch port(s).

Note: ESXi does not log VM connectivity or communication (outside of port or physical link failures seen at the host level), so it is important to perform the troubleshooting steps in this article during the time you are experiencing the issue to be able to determine the cause.

Related Information

Note: If connection to the default gateway is successful, but connections to other subnets are unsuccessful, then there is an issue in routing/Layer 3. Please contact your network team to determine why the Layer 3 connections are failing.

For more information, see:

VMware Skyline Health Diagnostics for vSphere - FAQ

Network cable of a virtual machine appears unplugged

Understanding guest operating system support levels

For translated versions of this article, see:

Solucionar problemas de conexión de red de la máquina virtual

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
SpanishEnglish

Attachments

Additional Resources

KB
•
Verificação da integridade de arquivo da máquina virtual hospedada (1003846)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant