Carl, This is a great idea and worked wonderfully for the DC where I added the 2nd NIC. Now the DC has internet access. Any ideas for the rest of the machines or do you think I just need to add a second nic to each of the virtuals? Would prefer not to have to go the route of the 2nd nic on all machines.
On Wed, Dec 9, 2009 at 12:29 PM, Carl Houseman <c.house...@gmail.com> wrote: > Hmm, give the virtual adapter a second IP address on the 10.x.x.x network > and establish default gateway to the 10.x.x.x router? > > > > Carl > > > > *From:* Bryan Garmon [mailto:bryan.gar...@gmail.com] > *Sent:* Wednesday, December 09, 2009 12:00 PM > *To:* NT System Admin Issues > *Subject:* Simple Networking Question? > > > > Today is one of those days where my brain is just not working well. I could > use some help. > > > > I have a virtual 2003 AD test environment running under VMWare Workstation > 7 including DNS,DHCP. Each virtual is configured to use vmware's bridged > networking and I am using 169.x network for all of the virtual lab machines. > It's bridged and not nat'd because I have several phyiscal machines that > need to communicate with the virtuals. This works great except for 1 problem > - none of the virtual machines have internet access. > > > > I have not configured any of the virtuals to have a default gateway. > > > > The host machine and the rest of my network is 10.x. > > > > How can i get the 169.x network to have internet access? > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
