I have installed both a Windows Server 2003 32bit and Windows 2003 64bit editions as a Guest OS on my Mac Mini Lion Server using Parallels 7. Both work fine except I cannot get the 64bit version to use a static ip address of 192.168.1.9. The 32bit version takes the static ip address fine and is pingable from another computer on the local network. The 64bit version shows that it is as 192.168.1.9 when I run ipconfig from the command prompt, but is not pingable from another computer. I have checked and rechecked that they are in Bridged mode, Default Adapter. I have even tried Bridged mode, Ethernet with the same result. Both server versions have been updated to latest release as has Lion Server. The Windows server will be a Terminal Server and a Web server, so I need to have a static ip address for port forwarding from my Airport Extreme router. Thanks for looking...
Just to confirm, you've tried setting both the 32-bit and 62-bit VMs to the *same* static IP address? (Ostensibly at different times, of course. ) Another thought too is to try pinging the 192.168.1.9 address from the 64-bit VM, when the VM is set to that address. If that fails, there's some fun and ugly bug going on somewhere. Also, just to sort out some network topology issues, I assume your host and other machines are also running on the 192.168.1.x subnet? Can you ping the 64-bit VM from the Mac host? A distant bell in my memory suggests that the 192.168.1.x subnet might be the virtual network, and thus wouldn't ordinarily be accessible from any physical machine other than the host. Are you setting the static IP address from within the guest, or is the router assigning the IP address via DHCP? It's possible in many routers to configure a set IP address via DHCP for a specific MAC address, so you'd have the 64-bit VM just get its address via regular DHCP but you'd still have a fixed IP address for server purposes. (Some routers also offer dynamic DNS capabilities allowing you to use hostnames instead of fixed IP addresses for servers, but I don't know if Airport Extreme is one of them -- it's definitely possible using Tomato router firmware, for instance.) Cheers,
Yes, both VM's are set to 192.168.1.9, but at different times, i.e. only one VM started at a time. 192.168.1.9 is pingable from within the 64 bit VM, but not at the local mac host or any other computer on the local network. I don't see how it can be anything to do with the local router or local network, because the 32bit VM works fine on the exact same mac and Parallels 7 version as the 64bit VM that doesn't. I have compared the two TCPIP windows setups on both VM's and they are setup exactly the same. I have also checked the Parallels setting for both VM's and they are setup exactly the same also.
