Problems getting virtual guest both internet and local domain access on a Windows 7 host
Hi, I realise that I'm trying something a little bit out there and most likely unsupported but I didn't want to have to purchase another server for a test environment at the moment. I wanted to install and test features of Sharepoint 2007 in our office. I've got a free quad core w 4Gb RAM running Windows 7 so I thought I'd set up my own test environment with Virtual PC. Host - Windows 7 Guest - Windows 2008 Server (Domain Controller) Guest - Windows 2008 Server (Sharepoint 2007) I'm using a Loopback Adapter on the Host for network connectivity between the Host and the 2x Guests on the 192.168.x.x network and its running a dream. I can access the Sharepoint Server home pages and RDP to the Sharepoint Server and DC1 from Windows 7 host, and all guests and the host can connect to the test domain. What I would like to do is give the Sharepoint Server Guest, access to the internet to test some Sharepoint features. The Host has a single physical network card which gives access to the Internet. However as soon as I configure a second network adaptor to provide the guest with access to the internet via Windows 7 Virtual PC NAT option, I'm not longer able to RDP to the Sharepoint Server and the Internet access doesn't work either. I should point out that when building the servers and prior to the guest joining the domain, NAT worked fine for internet access (with the MS Loopback Adaptop disabled at the time). I feel its a networking issue that I'm just not getting.Thoughts?
January 6th, 2010 10:54am

I do not use VPC but I am thinking you should be bridging the VM nic with the host nic if you want it part of the network, the NAT option in all VM software I use only allows the host access to the VM unless you do some routing.
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 5:26pm

That really isn't a feasable way to run a domain. If they are on the loopback network, the only way to route to the Internet would be through ICS on the host. (ie your physical NIC as the public interface of ICS and the loopback adapter as the private interface). ICS (and the built-in NAT option)are not really compatible with AD. You would need a third-party NAT solution like Wingate. Bill
January 7th, 2010 2:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics