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 VM TCP/IP ping connection issues (1007842)

Last Updated: 3/26/2024Categories: TroubleshootingTotal Views: 99896Language:
English

18 like this article

Subscribe to get an email
newsletter with new updates

18 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

A virtual machine will not ping.

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

Cannot establish a TCP/IP connection. For example, a virtual machine is no longer pingable or cannot ping other virtual machines.

Purpose

This article provides steps to troubleshoot virtual machine network communication problems over a TCP/IP network protocol, such as with the ping command.

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.

Resolution

Note: Validate that each troubleshooting step is true for your environment. These 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.

Troubleshooting virtual machine TCP/IP connection issues

Check the VM's network configuration in the guest OS and verify TCP/IP functionality. For more information, see Verifying virtual machine TCP/IP settings (1007875).

Check for duplicate IP addresses and resolve TCP/IP driver issues. For more information, see Resolving virtual machine IP address conflict issues (1008177).

Ping another VM that is on the same host and in the same port group on that host.

If pings to another VM on the same host same port group are not successful, then the issue is within the VM itself (in the guest OS or VM adapter settings).

Next ping the loopback address to verify that TCP/IP is working correctly. For more information, see Troubleshooting virtual machine TCP/IP issues by pinging the loopback address (1008206).

Check firewall configuration. For more information, see Troubleshooting network connection issues caused by firewall configuration (1007911).

If pings to another VM on the same host same port group are successful, then the issue usually lies in the port group's configuration or in the physical networking. Continue following the troubleshooting steps below.

Verify the default gateway and try to ping it. For more information, see Troubleshooting virtual machine default gateway connection issues (1007910) .

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. Contact your network team to determine why the Layer 3 connections are failing.

You can also check the 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).

Check the virtual switch VLAN configuration. For more information, see VLAN configuration on virtual switches, physical switches, and virtual machines (1003806).

Clear the Address Resolution Protocol (ARP) cache. For more information, see Troubleshooting network connectivity issues using Address Resolution Protocol (ARP) (1008184).

Verify physical switch port security. For more information, see Loss of network connectivity when Cisco port security is configured on the physical switch (1002811).

If the above troubleshooting does not find the answer, use the pktcap-uw tool to packet capture on the physical NIC or on the VM adapter. For more information, see Using the pktcap-uw tool in ESXi 5.5 and later (2051814).

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

For more troubleshooting information, see:

Troubleshooting virtual machine network connection issues (1003893).

Loss of network connectivity when Cisco port security is configured on the physical switch

VLAN configuration on virtual switches, physical switches, and virtual machines

Verifying virtual machine TCP/IP settings

Troubleshooting virtual machine default gateway connection issues

Troubleshooting network connection issues caused by firewall configuration

Resolving virtual machine IP address conflict issues

Troubleshooting network connectivity issues using Address Resolution Protocol (ARP)

Troubleshooting virtual machine TCP/IP issues by pinging the loopback address

Collecting diagnostic information for VMware products

仮想マシンの TCP/IP 接続の問題のトラブルシューティング

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

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