vmnet adapters and virtual machine adapters

[kevintb231]

I had a great network set up until my ,otherboard died this wek and now after replacing it nothing worlks and it has caused me business and clients. I am trying to et it set back up. Here is what I had:

http://communities.vmware.com/message/1855651#1855651

Question are the MAC addresses the same for vmnet0 as virtual eth0 ISP, vmnet2 as virtual eth1 192.168.0.254, vmnet3 as virtual eth2 10.10.5.1, vmnet4 as virtual eth3 172.168.0.1? I can't figure out why the 192 netwrok does not get recognized at all unless I bridge eth1 (192.168.0.254) and have no connection to vmnet2 but either way I still do not get internet connection.

This setup does not work anymore:

host

physical nic to ISP = vmnet0 - host uses NO IP for this
physical nic to Cradlepoint = vmnet2 - host uses 192.168.0.3
vmnet1 = IP does not matter - not used for this scenario
vmnet8 = IP does not matter - not used for this scenario

firewall
ethernet0 = vmnet0 --- assigned by ISP
ethernet1 = vmnet2 --- 192.168.0.254
ethernet2 = vmnet3 --- 10.10.5.1
ethernet3 = vmnet4 --- 172.168.0.1

ns1.centos.local
ethernet0 = vmnet3 --- 10.10.5.2

mail.centos.local
ethernet0 = vmnet3 --- 10.10.5.3

webserver
ethernet0 = vmnet3 --- 10.10.5.4

honeypot
ethernet0 = vmnet4 --- 172.168.0.2

cradlepoint
connected to vmnet2 --- 192.168.0.1

I can connect the 10,10.5.0 172,168.0.0 networks and just this IP from the 192.168.0.0. network 192.168.0.254 and ping all but I can't get to the rest of the 192.168.0.0 network which includes the rest of my household. If I connect 192.168.0.0 network I lose 10.0.0.0, 172.168.0.0 networks and 192.168.0.254 IP. I reset everything up the same the only thing I can figure is that MAC addresses got change in replacing the motherboard. Any direction would be more that greatly appreciated.

Thanks

kevin

[continuum]

Hi again 😉

did you reinstall the host operating system and VMware after the mainboard change ?

MAC address changes should play no role at all in this story unless your Internet connection is tied to a MAC address ?
Did you check wether you assigned vmnet0 and vmnet2 to the same nics as before ?

[kevintb231]

Yes I had to reinstall the host OS and Workstation 8 all over again. I followed everything I did last time (I made good notes). I have time today to see if I can figure out what I am missing. I will post back with more questions I am sure. This is really irritating because I had a really great network setup. Everything was working perfectly.

Thanks

Kevin

[continuum]

take it as a free lesson in VMware network  configuration 😉

I will help you if necessary 😉

[kevintb231]

I have:

virtual eth0 vmnet 0 ISP working

virtual eth1 vmnet 2 192.168.0.254 does not communicate with anything, router pickes it up sometimes but nor always, this is the gateway to my home network

virtual eth2 vmnet 3 10.10.0.5.1 comunicates with all goes online and is the webserver

virtual eth3 vmnet 4 172.16.0.1 (I changed the number because of interference with something else, did this before motherboard mishap so I know it's ok) communicates with all and gooes online and runs honeypot and can be accessedf rom outside like it should.

It's go something to do with my cradlepoint router. I get nothing no ping between 192.168.0.254 (vmnet2) and anyother machine on my home (192,168.0.0) netwrok nor can they ping it. I had to change the gatway on all home netwrok machines last time to 192.168.0.254 so they would go online but they can't see it now. It has to be something with router.

[continuum]

some routers use a MAC-filter - did you check that ?

[kevintb231]

Yes MAC filtering is turned off. For some reason I can not get the 192.168.0.254 adapter to be recognized by the rest of my 192.168.0.0 network. Could it have something to do with the DHCP in workstation 8 that controls the IP's for the vmnet adapters? Like the vmnet2 3 and 4 attached to my virtual adapters?

[continuum]

the VMware DHCP should never be used to work with a bridged vmnet - can you attach a current screenshot of vmnet.cfg ?

[kevintb231]

Here is the screenshot for netgear adapter that is bridged to 0 so virtaul machine has control. Host machine is set to only vmware protocol.

Here is setting for the other vmnet adapters in virtual config editor. This is where I was curious on the DHCP.

Here are adapter setting for virtaul machine settings eth0/ vmnet0 actual ISP NIC box:

Here are settings for other virtual adapters: 10.10.5.1, 172.16.0.1, 192.168.0.254 (this netwrok I can not get recognized at all, the host machine NIC is (192.168.0.3)

Thanks a bunch for your help!

Kevin

[kevintb231]

This is what got me. It all works again. Thanks!