Re: How to setup static IP address on guest

Mike101 · ‎02-24-2009

Question:

Using VMnet8. How to setup static IP address on guest ? What need to be done on Virtual Network Editor? Do I need to stop DHCP? Can host Ip address be either dynamic or static?

It worked if I setup both are dynamic IP address. But it did not work if I setup guest network IP address as static one and stoped the DHCP on virtual network editor.

How to fix the issue?

Thanks.

Scissor · ‎02-24-2009

Typically nothing needs to be changed in the Virtual Network Editor. Configure your Guest VM to use Bridged networking. Then boot the Guest and configure it with a static IP address the same why you would a physical machine running the same OS as the Guest.

rkr002 · ‎02-25-2009

I think, you need not to stop DHCP server on the Host, and the Guest can have either static or dynamic IP.

Generally, a guest need not to use a DHCP service, even if it is available.

It can have configured its own static IP, and the only requirements are same as for typical IP configuration (ex. same subnet setting for guest and host).

Mike101 · ‎02-25-2009

Can I use Nat networking? Guest Os is Linux and host is Vista. I was using Nat. When I was using DHCP setting on guest, it worked fine. After I setting up the same IP address as static from linux system, The host and guest could not ping each other even I kept same IP address and subnets on both host and guest. Is that because I did not use bridged?

admin · ‎02-25-2009

You'd configure your guest to use a static IP address as if it were a physical machine behind a router using NAT.

Regardless of whether the router has a DHCP server enabled (or in this case, whether the VMware DHCP service is running on your host) does not require machines (or VMs) to use it.

rkr002 · ‎02-25-2009

Of course, you can use NAT networking, and static IP address of the guest should be visible from the host.

However, the guest's IP address MUST be different from the host's one, and this is critical for any network you use (NAT, Host-Only, Bridge).

NAT is only a "device" which the guest must "connect to" by his settings: gateway, subnet and guest's own IP.

Please also check firewall settings on the host and guest systems, because the firewalls can eventually block some connections (including ICMP ping requests) in both directions.

Mike101 · ‎02-25-2009

It looks like the IP addresses are matched at same sub net. Any thing do I need to changed? But they still can not see each other. I have also turned off firewalls on both side too.

Here are the settings for reference:

Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter

Physical Address. . . . . . . . . : 00-11-50-06-A2-DD

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::c599:c3c7:4e24:5263%18(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.2.3(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Wednesday, February 25, 2009 6:00:59 PM

Lease Expires . . . . . . . . . . : Sunday, April 04, 2145 12:44:11 AM

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet

Physical Address. . . . . . . . . : 00-23-54-1F-C5-36

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

1

Physical Address. . . . . . . . . : 00-50-56-C0-00-01

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::5c58:609e:ac07:bda6%13(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.31.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

8

Physical Address. . . . . . . . . : 00-50-56-C0-00-08

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::bd32:3204:a3b3:398f%15(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.233.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.233.2

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : isatap.Belkin

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : isatap.{49AB6751-5AB2-49ED-8B4E-BD48979D3

7DB}

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : 6TO4 Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : isatap.{27AAA029-01AD-49AD-9DFD-EF4E2C547

822}

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : isatap.{870B8B0C-FAED-42BE-A4E4-C36F67D97

3DB}

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Linux :

eth0 Link encap:Ethernet HWaddr 00:0C:29:9A:48..

inet addr:192.168.233.130 Bcast:192.168.233.255 mASK:255.255.255.0

rkr002 · ‎02-25-2009

As for me, at first look, settings seem to be OK.

Can you check if the NAT service is running on the host ?

(can be checked either in VMware Network editor, or Windows ComputerManagement->Services)

DHCP for VMnet8 does not matter, but NAT service should be up (however I'm not sure).

Check also route table on Linux guest.

If there is no route you can add one:

route add -net 192.168.233.0 netmask 255.255.255.0 eth0

then restarting network on the guest system may be needed.

Mike101 · ‎02-25-2009

That is good points where I am looking for - how to trouble shooting.

I have looked at both host service and vmware network editor: there are three services running on widnow side and I also started VMware agent service and guest side Vmnet8 is started or enabled.

I checked routing table by typing route and it appears that the either installation or configuration has added info in the table as follows:

Destination Gateway Genmask Flags Metric Ref Use Iface

192.168.233.0 * 255.255.255.0 U 0 0 0 etho

link-local * 255.255.0.0 U 0 0 0 etho

loopback * 255.0.0.0 U 0 0 0 lo

Are those data right? Could gateway be *? Use is 0 too. I just changed the guest ip to static 19.168.233.130. Any other thing needed?

Thanks.

rkr002 · ‎02-26-2009

Gateway can be *, but maybe there is lack of the "default" route ?

However I wonder why you have "etho" name for the network interface: "etho" ??

normally the names are eth0, eth1, ...

Could it be a typo in ifcfg-eth0 config file?

There also may be some guest-specific reasons the network does not work.

You could search the forum for similar problems, because there were many discussions about network configuration.

for example

http://communities.vmware.com/message/1068545

http://communities.vmware.com/message/643418

Mike101 · ‎02-26-2009

I believe it is type error since I need to type in the result.

Thanks for the link and I will do some more research.

By the way does the issue to do with some Mac address?

Thanks.

rkr002 · ‎02-26-2009

By the way does the issue to do with some Mac address?

It may depend what Linux distribution you use.

For example in RedHat family the MAC address is also stored in ifcfg-eth0 config file and is used by the system.

So you can also check if the MAC address of the NIC is same as the one stored in the network config file.

All

How to setup static IP address on guest