Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VM lost network access

Status
Not open for further replies.

KRPGroup

MIS
Jun 22, 2005
317
CA
I have a VM 2003 server, before promoting it to a DC I changed to a Static IP. The VM is set to NAT.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-7A-70-BC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 127.0.0.1

At this point I was able to ping the internet, etc.
I then promoted it, installed DNS, ran windows updates, installed email services. All was working fine.

Today I am unable to get to the internet, the host is connecting fine. From the VM I can not ping my DFG but I can ping 192.168.0.1. From the host I can ping the server 192.168.0.10.

On the Host I have 2 VM Adapters, put there by VM.
Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.214.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Any suggestions?
 
Hi

Not absolutly sure about this, but shouldn't your gateway be 192.168.0.1 and not 192.168.0.2 - normally when you ca not get off you segment then it is a routing issue. ie the packet does not know where the gateway is so it can not get off the segment.
Anyone else got any ideas ?

Regards

Dave
 
thats what I thought too and tried.. doesnt seem to help. I read others had this issue and had to reinstall VMware to resolve.
My system is multihoned but the 2nd card is not used and I read this also may be causing the issue. Not sure why it worked for serveral days now its not.

I can ping the hosts IP from the VM server not sure what is stopping it from routing out?
 
Hi

Did you happen to put SP1 on the server ?

It has a built in firwall or the firewall is activated when SP1 is put on a server - may it has stopped some common ports. There is a wizard to run to see what is set and what is not set by SP1 - google it and you will find more about it.

Regards

David
 
The server was SP1 from the CD and the Firewall is not currently on, it is just showing as connected.

I decided to unistall the local Vmnet adapters on the host, I then reinstalled VMServer and VMnet1 & 8 were recreated (not sure why there is 2 of them vmnet1, vmnet8). (See below)
What is the difference between these 2 Vm nics and are they used together etc..??

Now that the adapters are there again (on the host) can I edit these adapters to be in the same subnet as my Vm Server. The server is DC with DNS running and I didn't want play with it's nic settings.

If so which one do I change vmnet1 or wmnet8?


IPconfig /all - on Host system
Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.222.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.145.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
 
I went into the vmnet8 via the Manage Virtural Networks admin tool and changed the settings on the Subnet & NAT dialog boxes to match my VM server current IP config.

Its working now but i am not sure why VM creates 2 vmnetx cards?
 
I am having a similar issue.

1. I also noticed that about the .2 being used as the DFG.
I corrected that.

2. The connectivity issue I had in the NAT was that incorrect mac address for the DFG was being sent out.

3. Wierd thing is the MAC that was working was not the mac of the VMNET8 interface which defaults to : 00-50-56-C0-00-08.

4. The MAC that my natted VM's are getting and using is :
00-50-56-F2:0B:7E

Anyone have similar issues?


Gb0mb

........99.9% User Error........
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top