Networking Issue

[sdaniely]

I am running ESX 3.01 and VC 2.1.

I needed to create an isolated resource pool that would not be able to access the rest of my images/domains so I created a new Virtual Switch named NAP. I added 3 images to this Reasource Pool and edited the Network Properties of the 3 images to use this Vswitch. When I assign a static IP, the images can communicate with each other fine.

I configured DHCP on one of the images and as far as it looks, DHCP is active, authorized and should be assigning IP's however my client image is not recievibg an IP from it. The client is VISTA.

Is there anything with the VSwitch properties that I need to edit/enable to allow DHCP?

Thanks -

Sean

[sbeaver]

Do you have a nic assigned to that vSwitch?

[sdaniely]

..just checked. I do have a physical adapter assigned but it is disconnected (red X).

[Texiwill]

Hello,

If the DHCP server is not one of the three VMs on that vSwitch, then there is no path to reach the DHCP server as the Physical NIC is inactive (red X). THat is most likely a cabling issue. Fix that and your problem is most likely fixed.

Best regards,

Edward

[sdaniely]

DHCP is configured on one of the 3 images within NAP.

[jjohnston1127]

Under the VM settings (Right click it, edit settings) for the virtual NIC, do you have the checkbox selected for "Connect at Power on" and "Connected?"

That's a DUH! that I've encountered a few times.

[sdaniely]

Done that before too. Yes they are enabled. I think I resolved the issue with another Duh...the scope IP range I was using was 190.168.0.3 - 10\24...as soon as I changed it to 192.168.0.3 - 10\24 it began issuing IP's. The static IP of the DHCP was a 190 address so not enirely sure this was it.....

[sdaniely]

Just wanted to update you on this. It WAS NOT an ESX issue, it was a NAP configiration issue that was blocking DHCP address distribution.