I've got a PC which basically runs VMWare and have a couple of Windows Server 2003 VM sessions that I use for work. The VM sessions have things like DHCP, WINS and DNS running and I used to run everything on the same network as home PC but this used to cause problems as the ADSL router would sometime allocate IP addresses to XP test workstations which would cause DNS problems.
So I split the LAN into 2 segments, got a second LAN card for the VMWare box and thought I'd simply route between the 2 nets, this is where the problems have started. My home PC and ADSL router sits on 1 LAN, 192.168.0.0 and the VM machines sit on the LAN 192.168.1.0, the 2 LANs are connected together effectively by the 2 LAN cards in the VM box. IP addresses of these cards are 192.168.0.254 and 192.168.1.254, I've also set up routing on this box under the host OS.
Now a proper workstation (not a VM client) connected to 192.168.1.0 can get access to 192.168.0.0 and obviously vice versa after adding static routes but for the life of me I can't get the VMs to talk across the LANs. It seems as if my request goes into the VM machine and then is never forwarded to the relevant gateway. I'm running the VMWare network in bridged mode and have the VMs set with a default gateway of 192.168.1.254.
This is what I have in terms of IP addresses:
ADSL wireless router 192.168.0.1
XP workstation 192.168.0.2 (static IP)
Laptop 192.168.0.10 (DHCP)
192.168.0.0 networks devices are either plugged into the ADSL router or wireless
VMWare PC with 2 NICS, LAN1 192.168.0.254, LAN2 192.168.1.254, the host OS (W2K3 server) also runs routing and remote access so routes between the 2 LANS
VMWare machine running W2K3 192.168.1.200 (DC runs DHCP, DNS, WINS)
VMWAre machine running W2K3 192.168.1.201 etc... (Member, used for file/print sharing)
XPClient 192.168.1.200 (DHCP from the VM above)
XPClient 192.168.1.201 (DHCP from the VM above)
192.168.1.0 network devices are plugged into a 3Com 8-port switch
The 2 LANS are physically connected together via the 2 physical NICs in the VMWare host box.
Now I can configure the XPClients above with either static routes or via DHCP routes and I can ping the ADSL router and the XP PC on the 192.168.0.0 network so this proves that the routing config is working. If I make the similar config changes on the VM virtual machines the machine can't ping the ADSL router or the XP PC on 192.168.0.0, it seems as if the traffic never leaves the VMWare virtual machine, almost as if VMWare workstation knows that the NIC of the VMWare machine is the same as the physical NIC and therefore it has no need to send it any further, this just doesn't make any sense to me. The XP Clients connected via the 3Com 8-port switch can connect to the VMs no probs.
Been doing some reading and I think the above problem is due to the host (192.168.1.254) being bridged to the VM virtual adaptors (192.168.1.200, 192.168.1.201 etc...), the default gateway adaptor to get to the 192.168.0.0 subnetwork is 192.168.1.254 I think the end result is that the bridging results in the IP traffic never being re-transmitted as the bridging software realises it's the same.
Sorry for the long post but does anybody have any ideas.
So I split the LAN into 2 segments, got a second LAN card for the VMWare box and thought I'd simply route between the 2 nets, this is where the problems have started. My home PC and ADSL router sits on 1 LAN, 192.168.0.0 and the VM machines sit on the LAN 192.168.1.0, the 2 LANs are connected together effectively by the 2 LAN cards in the VM box. IP addresses of these cards are 192.168.0.254 and 192.168.1.254, I've also set up routing on this box under the host OS.
Now a proper workstation (not a VM client) connected to 192.168.1.0 can get access to 192.168.0.0 and obviously vice versa after adding static routes but for the life of me I can't get the VMs to talk across the LANs. It seems as if my request goes into the VM machine and then is never forwarded to the relevant gateway. I'm running the VMWare network in bridged mode and have the VMs set with a default gateway of 192.168.1.254.
This is what I have in terms of IP addresses:
ADSL wireless router 192.168.0.1
XP workstation 192.168.0.2 (static IP)
Laptop 192.168.0.10 (DHCP)
192.168.0.0 networks devices are either plugged into the ADSL router or wireless
VMWare PC with 2 NICS, LAN1 192.168.0.254, LAN2 192.168.1.254, the host OS (W2K3 server) also runs routing and remote access so routes between the 2 LANS
VMWare machine running W2K3 192.168.1.200 (DC runs DHCP, DNS, WINS)
VMWAre machine running W2K3 192.168.1.201 etc... (Member, used for file/print sharing)
XPClient 192.168.1.200 (DHCP from the VM above)
XPClient 192.168.1.201 (DHCP from the VM above)
192.168.1.0 network devices are plugged into a 3Com 8-port switch
The 2 LANS are physically connected together via the 2 physical NICs in the VMWare host box.
Now I can configure the XPClients above with either static routes or via DHCP routes and I can ping the ADSL router and the XP PC on the 192.168.0.0 network so this proves that the routing config is working. If I make the similar config changes on the VM virtual machines the machine can't ping the ADSL router or the XP PC on 192.168.0.0, it seems as if the traffic never leaves the VMWare virtual machine, almost as if VMWare workstation knows that the NIC of the VMWare machine is the same as the physical NIC and therefore it has no need to send it any further, this just doesn't make any sense to me. The XP Clients connected via the 3Com 8-port switch can connect to the VMs no probs.
Been doing some reading and I think the above problem is due to the host (192.168.1.254) being bridged to the VM virtual adaptors (192.168.1.200, 192.168.1.201 etc...), the default gateway adaptor to get to the 192.168.0.0 subnetwork is 192.168.1.254 I think the end result is that the bridging results in the IP traffic never being re-transmitted as the bridging software realises it's the same.
Sorry for the long post but does anybody have any ideas.
