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

Verifying virtual machine TCP/IP settings (1007875)

Last Updated: 9/5/2017Categories: TroubleshootingTotal Views: 64505Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Purpose

This article provides steps to verify TCP/IP settings and to verify that the NIC is communicating with the host.

After you complete the steps in this article, see Troubleshooting virtual machine default gateway connection issues (1007910) to confirm the LAN connection.

Resolution

Verifying TCP/IP configuration

When the TCP/IP protocol is used, incorrect TCP/IP settings (such as an incorrect IP address or an incorrect subnet mask) can cause communication problems. For example, a virtual machine may not be able to ping its own IP address.

If you are having communication problems, verify your TCP/IP settings.

To verify TCP/IP settings:

To determine basic TCP/IP settings for Windows, run the command:

ipconfig

You see output similar to:

Ethernet adapter Local Area Connection 1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.10.10.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.1

On a Linux virtual machine, run the command:

# ifconfig

You see output similar to:

eth0 Link encap:Ethernet HWaddr 00:0C:29:9E:78:5F
inet addr:192.168.48.128 Bcast:192.168.48.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2080 (2.0 KiB) TX bytes:7037 (6.8 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1453 errors:0 dropped:0 overruns:0 frame:0
TX packets:1453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2294308 (2.1 MiB) TX bytes:2294308 (2.1 MiB)

Note: If the ipconfig or the ifconfig command does not produce any output, ensure that the NIC is enabled.

From the output of the ipconfig or the ifconfig command, verify that the IP address and subnet mask are correct.

Note: If you are unsure of the correct values, contact your network administrator.

If DHCP is configured, confirm that DHCP is assigning the IP address correctly by renewing the IP address. From the command prompt in Windows, run the command:

ipconfig /renew

From a Linux virtual machine renew the DHCP address with:

# dhclient -r
# dhclient eth0

Where eth0 is the network interface from the ifconfig output using DHCP. If the dhclient command is not available or does not work, see your Operating System documentation for the procedure to release DHCP address on your version on Linux.

Note: lo is a loopback interface and will have the IP 127.0.0.1 which is normal.

Pinging the virtual machine IP address

If you can successfully ping the loopback address, try to ping your own IP address. From a command prompt, run the command:

ping IP_address, where IP_address is your computer's IP address

For example:

ping 10.10.10.30

The output of the ping looks similar to:

Pinging 10.10.10.30 with 32 bytes of data:
Reply from 10.10.10.30: bytes=32 time=2ms TTL=128
Reply from 10.10.10.30: bytes=32 time<1ms TTL=128<br>Reply from 10.10.10.30: bytes=32 time<1ms TTL=128<br>Reply from 10.10.10.30: bytes=32 time<1ms TTL=128</span>

Note: If you receive an error message when you try to ping your own IP address, there may be a communication problem between the host and your NIC. For more information, see Verifying virtual network adapter is present and connected to the virtual machine (1003786).

Related Information

For related troubleshooting information, see Troubleshooting virtual machine TCP/IP connection issues(1007842).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

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 Workstation Player

VMware Workstation

VMware vSphere ESXi

VMware View

VMware vCenter Server

VMware vCenter Lab Manager

VMware Server

VMware Player

VMware Fusion

VMware ESX Server

VMware Cloud Director

VMware ACE

view all

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