Avatar of Yashy
Yashy
Flag for United Kingdom of Great Britain and Northern Ireland asked on

How to get the nested VM windows 2008 to access the internet?

hi guys

I've got a situation where I have a nested environment.

A Vmware Workstation 8.0 running Vmware Esxi 5.0. And on that, is running a Windows 2008 VM.

The IP address of my local PC is 192.168.1.10/24. With a gateway of 192.168.1.1.

The Esxi hypervisor has an IP of 192.168.1.15.

However, the Windows 2008 sitting on there has been given a 192.168.1.20/24 address with a gateway of 192.168.1.1 and it can't access the internet.

I don't know if there are settings I have to play with on the Workstation in order to get the nested VM access to the internet?

Any ideas on how to do this?

Many thanks
Yashy
VMwareVirtualization

Avatar of undefined
Last Comment
Yashy

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Yashy

ASKER
Everything was what you described, other than the VLAN 4095 which I had to do go and do.

For anybody else reading this who doesn't know how to do it, in order to get to the VLAN 4095, you must:

 - Log on to the Esxhi host (with the Vsphere client)
 - Select the Esxi host.
- Go to the 'Configuration' tab on the right.
- Select 'Networking' on the left hand column and then click on the 'Properties'.
- Select 'Management Network' and click 'Edit'.
- Where it says 'VLAN ID', use the dropdown to select '4095 (ALL)' and click OK.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

So it's working now?

and make sure your VMs are also using the Virtual Machine Network 4095 (ALL).

You should find then if you allocate a VM with an IP Address of 192.168.1.x it should be on the same network, from what I recall, there is someting odd with DHCP, so maybe do not expect DHCP from your MAIN LAN to passthrough twice to the nested VMs!
Yashy

ASKER
It's not working sadly:(.

I've selected the 'VM Network' to 4095 (ALL).

I've set the IP address of the VM itself with a static IP and a gateway of my router.

When you said 'make sure your VM's are also using the Virtual Machine Network 4095 (ALL)', did you mean the setting that I've mentioned in the second line above?

Because on the Workstation 8, there isn't any place I can see where I can select the VM's to be on the 4095 (ALL)?
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

okay, I'll need screenshots of:-

VM Settings for ESXi Nested Host

vSwitch and NIC settings of ESXi Host

can you ping host from the nested VM?

can you ping other devices from the nested VM?
Yashy

ASKER
Okay, I've attached all of the necessary screenshots for you.

To answer the questions.

I can't ping host from the nested VM. I get a ping transmit failed. I've attached a screenshot of the IP settings of this VM. I can't ping anything from the nested VM.
Vmware-setting-1.jpg
Vmware-setting-2.jpg
Vmware-setting-3.jpg
Vmare-setting-4.jpg
Vmware-setting-5.jpg
VM-IP-address.jpg
VM-IP-address-2.jpg
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

so the nested ESXi server is able to get an IP Address 192.168.1.15 from your LAN, same LAN as the VMware Workstation host?

I have seen VLAN issues with ESXi 5.1, I'm wondering if it's the same bug.

all looks okay, does your VM if set to DHCP receive an IP Address?

btw 6 vCPU for your VM is far too many, not that's the network issue!
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Yashy

ASKER
Il reduce cpus..hehe.
The esxi host gets its IP via dhcp. And it is on the same network as Workstation on the LAN. The VM however is unable to get dhcp.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Just had another thought ALSO SET THE vSwitch to

ALLOW Promiscious Mode: Accept, either on the vSwitch or Virtual Machine Network.

Promiscuous-mode-network1.jpg
Yashy

ASKER
I tried this also and still doesn't work. I set it to Accept.

The weird thing is that when I add a static IP to the VM, it still sees it as an Unindentified Network. Even if it didn't have internet access, I'd expect the IP address added to make the VM part of an identified network.

Also, I've taken a screenshot for you of something else. In the Vswitch properties, the 'networks' only shows as the IP address range of my own PC (192.168.1.9). Is that correct?
Vmware-setting.jpg
Your help has saved me hundreds of hours of internet surfing.
fblack61
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

I'll need to debug this, and check, ESXi 4.1, 5.0 and 5.1, and see if something has changed or broken in 5.1!
Yashy

ASKER
Hanccocka - you won't believe it.

It was  my own PC's internal firewall driver. I unchecked it in my network settings and hey presto....all is good:).

Thanks so much again for your help.

Happy new year to you sir.