Problem Configuring VMNet1 IP on Win 7 Host

[AshishK20111014]

Hi,
I am trying to run a SLES10 SP3 as Guest OS using VMWare Workstation 7.0.1 on Windows 7 Ultimate(32-bit) host.
The VM is configured for Host Only networking and the IP address assigned to the Guest OS is 192.168.71.128.
By default the VMnet1 adapter on the Host shows a different IP address. So I tried to change the IP of the VMnet1 adapter to 192.168.71.1. In windows it allows me to assign the required IP to the adapter but when I check using "ipconfig -all", the vmnet1 adapter still shows the same auto assigned IP and not the manually assigned one. As a result, the Host and Guest are not able to communicate with each other.
If I try running the same VM image on a Windows XP machine, I can change the vmnet1 adapter's IP to 192.168.71.1 and the host and guest can communicate with each other without any problem. But I need to get this running on the Windows 7 host. The Host is a personal desktop with full admin access.
Can anyone shed some light on this.. pls...

[ItsMeHere]

Can you please provide the following:

- a screenshot of the Virtual Network Editor, with VMnet1 selected (here at the bottom, you should be able to set the Subnet IP, which also updates VMnet1 for the host OS)

- the auto-assigned IP address of your VMware Network Adapter VMnet1

- What are you referring to with "it" in "In Windows it allows me"?

I think it won't work to alter the IP address in Windows' Network Connections; you will have to use VMware's Virtual Network Editor.

[AshishK20111014]

Hi,

Here are the details:

- a screenshot of the Virtual Network Editor, with VMnet1 selected (here at the bottom, you should be able to set the Subnet IP, which also updates VMnet1 for the host OS) - Attached File

- the auto-assigned IP address of your VMware Network Adapter VMnet1 - Attached File

- What are you referring to with "it" in "In Windows it allows me"? - What I mean is that when I use Windows XP I am able to set the IP address manually to 192.168.71.1 and when I run "IPCONFIG -all" the same address is displayed. However, when doing the same in Windows 7, "IPCONFIG -all" returns a different IP address as you might have noticed in the attached file even though the defined subnet is different in the Virtual Network Editor.

[ItsMeHere]

I just checked it in my Win7 installation with WS 7.1.3, and was quite astonished: Right like you I only get an APIPA address 169.254.x.x for VMnet1, although this network is automatically set for 192.168.75.0...

As I wrote in my last reply, you might not be able to successfully set the IP address for VMnet1 virtual adapter in Windows's settings, but rather by changing the subnet IP for VMnet1 in Virtual Network editor.

If I do so in Win7 (x64-SP1-localized German), and change 192.168.75.0 to e.g. 192.168.76.0, my VMnet1 gets the expected 192.168.76.1. But when I change this parameter back to 192.168.75.0, this network card does not get 192.16.75.1, but gets an APIPA address again. Strange...

VMnet8 is not affected, and this issue also does not occur in Vista-32 running WS 7.1.4...

Sorry, I don't have a cure for that. Perhaps it's a bug, and VMware needs to fix it. Or it's something going wrong in Win7...

Although the release notes do not seem to indicate something related, I'll check this after an update to 7.1.4. Will report result later; you know, it's a time consuming process with some reboots...

[AshishK20111014]

thanks for confirming my issue as I was begining to think I was doing something wrong.

As for the version, the screenshot I sent was for vmware 7.1.4 and my windows 7 ultimate is 32 bit.

For the time being I have changed the ip of my sles10 sp3 vm image to match the default ip subnet of vmnet1 I.e. 192.168.75.128 and they are able to communicate. My concern is that I am using the vm image to host business objects server. Generally BI tool servers don't take the IP change very nicely and cud cause problems with the services, but looks like SAP has fixed some of those issues with Business Objects and therefore I am lucky to be able to keep the services running inspite of changing the VM's IP.

Sent on my BlackBerry® from Vodafone

[WoodyZ]

Looking a your VMNET1.jpg the Internet Protocol Version 4 (TCP/IPv4) properties for VMnet1 are not properly set.  Have a look at my attached image to see what is missing on yours.    Note that my IP Address is different but you'll see what is missing on your's so if it was like that on mine I'd manually configure it.

[ItsMeHere]

Now, that's even stranger...

I just updated my WS 7.1.3 to 7.1.4, and the problem is gone.

But I can still confirm that changing the IP address of adapter VMnet1 in Win7's network settings does not get reflected in VMware's Virtual Network Editor. Perhaps because the accompanying DHCP server does not get sent a hint. This would explain why host-only-VMs set for DHCP do not get a working connection to the host, after the IP address had been changed manually in Win7's network settings.

Just a sidenote: my Win7 network settings (after update to 7.1.4) do not show the host's VMnet1 adapter as DHCP; they show it with a fixed network address. Maybe this could cure your situation, too.

[ItsMeHere]

Ahh, I see that WoodyZ came to the same conclusion. So I assume this definitely can be considered a solution to the issue.

And he was surely quicker than me...

[gggeek]

It seems I have the same - or similar problem: win 74 64 bit host, using vnment1 for host-only networking. VMW Player 401.

Looking at vment1 adapter config on the windows side, it says ipv4 on (I disabled ipv6), fixed IP address of 192.168.40.1/24 (no dhcp).

Whatavere I try to run on the cli (ip onfig variations), that adapter touts an "automatically assigned" address in a completely diferent range. I also tried to disable + reenable the adapter many times, to no avail.

The only workaround I found so far was:

- moving the adapter to dhcp

- it will get the correct IP assigned from vmware dhcp service (dhcp config sets a fixed ip address for that card based on its mac address)

- moving the adapter back to a fixed ip config

Unluckily, this being a laptop, as soon as my wifi network card found a new network, the vmnet1 card went bonkers again.

I found this page describing the exact same bug: http://hydra.geht.net/tino/howto/vmware/vmwareplayer/

Is this a known bug? Is there an ETA for a fix?

[jbhall56]

This problem seems to have come back with Workstation 11.  I just upgraded from 10 to 11 and I cannot get back to 192.168.137.1/24 for VMNet1. I checked the adapter properties and it shows a static address of 192.168.137.1/255.255.255.0 which is the same as it is in the Virtual Network Editor just like in Workstation 10.  However, when I execute an ipconfig command, it shows VMNet1 as having an IP address of 169.254.63.129. Any ideas as to how to fix would be appreciated as the VM I run with the 192.168.137.x address block needs to have an address in this IP range in order for it to be licensed correctly by the vendor.

[jbhall56]

Found that the Windows 7 bug posting Vmware Player also fixes this issue.

[Dekernel0]

I seem to be having the same issue with Workstation 12. When I look at what IP Windows is configured for VMnet1, I don't see that IP when I do an ipconfig on the host system. See screen shot. Is this what you having the issue with?