Vista hosting VMWare gets IP address conflict when MS Guest OS is running

I have a physical machine running Vista Ultimate 64bit.  This machine has a static IP of  There are maybe 10 nodes on the entire network, and the DHCP scope runs from .75-.99 off of the gateway, which is, is a PIX, and it's a /24 network

On this machine, I have have VMware Server 2.0.0, Build 122956.  I have 2 Ubuntu VMs, an XP Pro VM, a Server 2008 VM, and a Server 2003 VM all created on this machine.  I have not had an issue with the Ubuntu VMs, though I do not use them frequently.  I built VMs for XP, 2003, and 2008 for studying/testing purposes.  The servers have static IPs, and they are .10 and .11.  XP is DHCP.

Anytime I leave the XP VM or the Server 2003 VM running for any length of time (sorry, I do not know precisely how long, but I'd say longer than 20-30 minutes), my Vista OS loses at a minimum, internet connectivity, DNS resolution, and I get a Network Error, "Windows has detected an IP address conflict."  I have not tested the XP VM, but the 2003 VM still has internet connectivity.  It cannot ping the Vista host by name or IP.

This ONLY happens on this Vista machine when the VM hosts are running.  Once I close the hosts, I can reset the adapter, and everything is fine again.

Any ideas?
Who is Participating?
jasondimaioConnect With a Mentor Author Commented:
Well, I was not able to determine why I have to use DHCP on Vista, and not on Server 2008.  Closing this question.
Would you be using bridged networking for your VM and use a wireless adapter on the host?
If that's the case, it is normal that both the host and guest get the dame IP from DHCP since most wireless adapters cannot send ethernet packets with a MAC address different than their own.

If you really want to use bridged networking, use a static IP.
I'd consider using NAT instead.
jasondimaioAuthor Commented:
Thanks for taking time to reply, qualipsoft.

I did set up bridged networking on all of the guests, but the host is not wireless.  Also, the host has a static IP address, as mentioned in the original post.  The Server VMs have static IPs.  It still happens.

I changed the configuration of the 2003 Server VM for the NIC to be NAT'ed, and now I have no network connectivity on the VM.  I can ping nothing with the NAT configuration.

I do confess, I do not know how to properly use NAT as it pertains to configuring VMware.
John HurstBusiness Consultant (Owner)Commented:
Bridged Networking gets its IP from the DHCP source, in this case the PIX gateway. I do not see why this should cause a loss in connectivity and indeed, if my host machine is wirelessly connected, any VM in bridged mode will get a different IP than the host machine.

You can try NAT to see if it helps. VMware uses NAT Networking when it provides its own internal DHCP server. You go into the VM Machine Settings before starting the machine and set the networking to NAT. You need to (initially at least) set your VM's to use DHCP so they can get an IP address. It will look like where 045 is assigned by NAT.
... Thinkpads_User
Have you tried changing the way the networking works in VMWare? If you're using bridged mode right now, perhaps you could try using NAT instead?

John Jennings
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.