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 th...
See more...
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???
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...
See more...
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!
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 conne...
See more...
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