Alright. I've read lots and lots and lots about this on the 'net and on Communities, here, but I can't seem to solve this problem.
I've got a Windows 2003 64bit VMWare server. It's configured with 2 physical adapters. One is on my DMZ. One is on my corporate NAT (not to be confused with VMWare's NAT).
I've got about 20 VMs setup on the NAT, and they all work fine.
My NAT network has a DHCP server on it.
My 2nd NIC on my DMZ, well, I need to expose a VM to the outside world for testing. Using a bridged network (I gave the VM session his own public IP on the DMZ), and allowing VMWare to "automatically choose" the adapter on vmnet0 was working fine. Then it stopped.
Every time I try "automatically choose," I'm unable to ping from .47 (my VMWare server) to .48 (the VM session). If, however, I change to a DHCP address, I get one of my NAT addresses. This tells me that VM has mapped this session to the wrong adapter.
So, I try the trick of setting up VMWare with vmnet2 bridged to physical adapter #2 (my DMZ nic). This "seems" to work, but I still have to choose "Bridged" as the network type in the UI, and when it comes up, it's picking vmnet0, apparently. I don't see anywhere I can force the session to use vmnet2 instead of vmnet0. I've tried adding:
What I now have is:
VMNet0 bridges to Broadcom Gigabit Ethernet (my internal NAT address -- about 20 machines work fine)
VMNet2 bridges to Broadcom Gigabit Ethernet #2 (my DMZ address. The outside world can ping him, and he can ping out on this)
Again, the only choices I have for the Network Adapter Type or "Bridged," "Host Only," or "NAT" (that last being VMWare's NAT of course, not my network NAT as referred to above). I choose bridge (since I gave him a public DMZ address). I start the machine.
.47 (the VM server) cannot ping .48 (the VM session). .47 can ping to the outside world, and they can see him.
How can I fix this??????