> Ok,
>
> Been tinkering with my VMs today, and I can't figure this one out, or even
> if it is possible so any suggestions would be appreciated.
>
> I have a 2003 server which is set up as a DC.
> I also want this server to be configured as a DHCP server eventually, so
> that it assigns IP's to my VM clients.
>
> What I'd like to do is to have the server as the sole point of connection to
> the internet for my virtual network, so that if a client wants to gain access
> to the net it has to go through my server.
>
> Now, I currently have a network adapter in the VM which is set to use NAT
> and gain access to the web through the Host. This works fine, however the
> address is dynamically assigned. I want to give the server a static address,
> it being my DC.
>
> What I thought about doing was installing a second adapter set to local only
> which would serve as the LAN connection and have the other one NAT'ed as the
> Internet connection. I was then going to run ICS on the NAT'ed adapter, but
> this again changes the IP Address to 192.168.0.1 which also happen to be the
> IP Address of my Cable Modem, which kind of confuses the host OS I think.
>
> Anyone got any ideas as to what I need to be setting my adapters to inorder
> for what I want to do to work?
>

> Ok,
>
> Been tinkering with my VMs today, and I can't figure this one out, or
> even if it is possible so any suggestions would be appreciated.
>
> I have a 2003 server which is set up as a DC.
> I also want this server to be configured as a DHCP server eventually,
> so that it assigns IP's to my VM clients.
>
> What I'd like to do is to have the server as the sole point of
> connection to the internet for my virtual network, so that if a
> client wants to gain access to the net it has to go through my server.
>
> Now, I currently have a network adapter in the VM which is set to use
> NAT and gain access to the web through the Host. This works fine,
> however the address is dynamically assigned. I want to give the
> server a static address, it being my DC.
>
> What I thought about doing was installing a second adapter set to
> local only which would serve as the LAN connection and have the other
> one NAT'ed as the Internet connection. I was then going to run ICS on
> the NAT'ed adapter, but this again changes the IP Address to
> 192.168.0.1 which also happen to be the IP Address of my Cable Modem,
> which kind of confuses the host OS I think.
>
> Anyone got any ideas as to what I need to be setting my adapters to
> inorder for what I want to do to work?

> You are on the right track. It is a better idea to use RRAS/NAT on the
> server. This gives you more flexibility.
>
> Configure your AD network in the local only subnet using a static IP for
> the server. You can run DHCP on this server and it will not affect the
> host's network. The virtual network is isolated from that. You would set
> DHCP so that the clients use the AD server as default gateway and DNS
> server.
>
> Put a second NIC in the server, and link it to the host's physical NIC.
> This NIC will get the dynamically assigned IP and be able to access the
> Internet.
>
> Configure RRAS on the server as a NAT router. This will allow the AD
> clients to share the server's Internet connection. You will need to modify
> the DNS on your server to forward to a public DNS service (so that it can
> resolve "foreign" names as well as your local ones). Do not use the DNS
> relay option in NAT. This is not compatible with AD.
>
> This isn't just theoretical. I have a virtual network like this running
> on my home network. It was set up under VPC and is currently running under
> Virtual Server. It basically looked like this under VPC.
>
> Internet
> |
> DLink router
> 192.168.0.1
> |
> workstations
> 192.168.0.x dg 192.168.0.1 (config from router)
> |
> VPC host (XP Sp2)
> 192.168.0.n dg 192.168.0.1 ditto
> |
> 192.168.0.n dg 192.168.0.1 ditto
> "virtual" server 2003 (RRAS/NAT)
> 192.168.9.1 dg blank static
> |
> "virtual" clients
> 192.168.9.x dg 192.168.9.1 (config from DHCP on server)
>
> Clients on the virtual network have full access to each other, to the
> server and to the Internet. machines on the host's network cannot see the
> machines on the virtual network (because they are on the public side of the
> NAT router).
>
> To minimise problems caused by a multihomed DC, disable Netbios over
> TCP/IP on the "public" NIC of your server. It is also advisable to set your
> DNS server to listen on its "private" interface only (so that DNS only
> registers machines in the virtual network).
>
> simongrahamuk wrote:
> > Ok,
> >
> > Been tinkering with my VMs today, and I can't figure this one out, or
> > even if it is possible so any suggestions would be appreciated.
> >
> > I have a 2003 server which is set up as a DC.
> > I also want this server to be configured as a DHCP server eventually,
> > so that it assigns IP's to my VM clients.
> >
> > What I'd like to do is to have the server as the sole point of
> > connection to the internet for my virtual network, so that if a
> > client wants to gain access to the net it has to go through my server.
> >
> > Now, I currently have a network adapter in the VM which is set to use
> > NAT and gain access to the web through the Host. This works fine,
> > however the address is dynamically assigned. I want to give the
> > server a static address, it being my DC.
> >
> > What I thought about doing was installing a second adapter set to
> > local only which would serve as the LAN connection and have the other
> > one NAT'ed as the Internet connection. I was then going to run ICS on
> > the NAT'ed adapter, but this again changes the IP Address to
> > 192.168.0.1 which also happen to be the IP Address of my Cable Modem,
> > which kind of confuses the host OS I think.
> >
> > Anyone got any ideas as to what I need to be setting my adapters to
> > inorder for what I want to do to work?
>
>
>