Win2003 Srvr w/DC under Fusion

[ejaco]

I have a set of VM's (4 - db, app srver, mid-service apps) that interoperate & the main has Win2003 Server with a Domain Controller. The DC needs to retain it's static addressing & when I start it with Fusion on my MacBook Pro (2.4/4GB) it takes the netAddr from the MBP and the environment falls apart.

First- I'm not a technical admin & most of this is way beyond me but my tech team (who all run VMWare Workstation 6.0 under Windows) say that in 6.0 there are vmware virtual network drivers that are loaded in Win that can then be accessed under VMWare Settings so the DC is not reset. None of them know the Mac & the couple that were helping me said they couldn't find a similar feature in Fusion.

Any one have any ideas / instructions on how to set this up with Fusion? Greatly appreciated!

Eric

[WoodyZ]

The DC needs to retain it's static addressing & when I start it with Fusion on my MacBook Pro (2.4/4GB) it takes the netAddr from the MBP and the environment falls apart.

Without have a clearer picture of the topology of this network it's hard to offer anything other than by default a Fusion Virtual Machine's Network is set to NAT and if you're Hard Coding the IP address in the Virtual Machine's then you should set the Virtual Machine's Network to Bridged.

Have a look at:

[Technogeezer]

I've done something similar to this. While it may not match what you want to do exactly, it may give you some ideas on how to proceed.

I have a group of VMs that I use for demonstration/training purposes. One of them is a DC. There's no need for them to communicate with the outside world, just with one another.

There's very little I do on the Fusion side to get things working, most of the work is in the Windows VMs themselves.

First, from within the Windows 2003 VMs, assign each server a static address and configure their TCP/IP settings manually (no DHCP). What address to use would be dependent upon the virtual NIC type. NAT would be, by default on the 172.16.247 network (subnet mask 255.255.255.0), or Host Only on the 192.168.99 network (also subnet mask 255.255.255.0). Avoid the .1 address on each subnet as that's the Mac host. You should be able to pick addresses in the .2 - .127 range and not interfere with the DHCP provided by Fusion.

Since my VM environment has no need to access the world, my virtual NICs are is set up for Host Only.

The second thing I do is to use the DC as a DNS server (AD-integrated DNS). Either register the IP addresses manually in the DC's DNS, or configure the other servers to automatically register their connections. Make sure the DC VM is configured in your other server VMs as the DNS server.