VMware Communities
HotstartJustin
Enthusiast
Enthusiast

VM's resolving incorrect IP Address

Hello all,

The issue I am having is this.  I am running 2 windows7 VMs called Win732-Package & Win732-Capture, they are both linked clones and are using NAT(192.168.10.X) for the network connection.  When I attempt to ping each other they resolve the following address (10.1.X.X) which is the address of my physical NIC they are natting to.  This causes issues when resolving shares between the VMs.  Also I am using NAT because these machine DO need access to the internet.  I need both these machines to resolve to the addresses they receive from NAT (192.168.10.X).  Thank you in advance for any help/comments/feedback.

Justin

Justin Allen
Reply
0 Kudos
6 Replies
HotstartJustin
Enthusiast
Enthusiast

ping.JPG

Justin Allen
Reply
0 Kudos
julienvarela
Commander
Commander

Hi,

Try nslookup command, i think you need to correct your entry in your DNS.

If you cannot change this , you can edit your host in your VMs c:\windows\system32\drivers\etc\hosts and add this 192.168.10.X Win732-Package.

Julien.

Regards, J.Varela http://vthink.fr
HotstartJustin
Enthusiast
Enthusiast

Thank you Julien, I thought about editing the host record before but I would like to keep these VMs on DHCP.  For whatever reason, I suspended the VMs last night before going home and now showing up today I ran NSLookup and everything was showing fine, ping was also coming back correctly.  after a reboot everything came back up okay...  "Ghost in the Machine".  Thank you again for your input Julien!

Justin Allen
Reply
0 Kudos
julienvarela
Commander
Commander

Sure,

You're welcome.

Regards,

Julien.

Regards, J.Varela http://vthink.fr
Reply
0 Kudos
sathishhcl2006
Contributor
Contributor

If These VM's haves another NIC and It is configured with 10.X.X.X IP's. Go to Network Properties of the Second NIC -> Advanced -> DNS

Uncheck the " Register This Connection address in DNS"Capture.JPG

Regards Sathish VCAP-DCA,VCP-DV 4/5, VCP5-DT, RHCE
Reply
0 Kudos
HotstartJustin
Enthusiast
Enthusiast

Thank you for the reply.  In this scenario I was only running 1 NIC and they were in NAT mode.  I will keep this suggestion in mind with future situations with DNS resolving incorrectly.

In this situation, the problem resolved itself.  I suspended the guest and when I unsuspended the next day, no more dns issues.  Maybe this is an issue with Workstation running on Windows 8???

Justin Allen
Reply
0 Kudos