Vista - vpc with srv2003 en xppro

hi
I installed a server2003 and a xppro in vpc.
I plan to install DHCP on the server, so I want to be sure that my router is
not giving ip addresses (I can not turn him off since I am in a classroom).
I was experimenting with vmware and I did not succeeded: I want to be able
to go on the internet with both server and client...
I am new to vpc, please if possible, explain what I have to do.
I am on a cable-modem.

"marcel" <marcel@xxxxxx> wrote in message
news:E1549B3F-32EC-4AA6-A2A5-6696DF5F54F7@xxxxxxThe correct way to do that is to run the virtual machines in their own
network. In VPC that means setting both both machines to use Local Only. You
should not run DHCP on a server if there is another DHCP server on the
network.

You will not be able to connect to the Internet from these machines. If
you really need Internet connection you could run a third vm as a NAT router
between the virtual network (Local Only) and the physical network.

This is not really a virtual machine problem. You need to do the same
things to run DHCP on two physical networks.

does it have any sence to experiment in a "local only" (private) network
where a virtual server is dhcp, instead of working with the hardware router
who gives the ip addresses?

In general, is a server2003 used as a DHCP server? I tought the router took
that job.

I do not succeed in giving my virtual pc's access to the internet, if i use
the server as a dhcp server (all vpc's are "local only"). But, i am rather
newbie in this mather.




"Bill Grant" wrote:

hi there
I have read another answer of you in a forum about some one with the same
problem:

"I usually put my virtual machines in Local Only in their own IP subnet
when running on VPC and set up one vm as a NAT router between the local only
and physical network. .."

I understand "putting in there ownn subnet", but I do not know how to work
with the server as NAT router... is there a specific webpage wich explains in
depth how to do this?

marcel




"Bill Grant" wrote:

On Thu, 26 Feb 2009 04:12:23 -0800, marcel
<marcel@xxxxxx> wrote:
Local only won't give your VMs access to your outside network. Local
only is a 'virtual' network for VMs, there's no connection to the host
PC or any outside network. It is local to the VMs only.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

"marcel" <marcel@xxxxxx> wrote in message
news:26CC9BC3-CEA2-4D91-B759-8B2C4DBB58A7@xxxxxxIt really depends on what you want the server to do. If you are trying to
set up a domain controller you cannot use the DHCP from your router. This is
true whether you are using physical machines or vms. The server needs to
have a static IP and use its own IP address for DNS.

If you simply want the server to behave like an additional server on
your local LAN, leave the server at he default setting. (That is set to get
its IP config automatically and its NIC set to link to the physical NIC of
your host).

That really is not a VPC question. It is a networking question.

To join two IP subnets you need an IP router. You can use a server (or
workstation for that matter) as an IP router. The router has two NICs, one
in each subnet.

The routing software in Windows Server is RRAS. Setting up a RRAS router
as a NAT router is as simple as running the setup wizard and selecting the
NAT option.

To run a private LAN in Local Only behind a NAT router, you configure the
network like this. The external NIC of the router connects to the physical
network through the physical NIC in the host. The internal NIC connects to
the virtual network Local Only.

Internet
|
Gateway device
192.168.0.1 --------------------------------------
|
|
LAN machines |
192.168.0.x dg 192.168.0.1 physical network
|
|
192.168.0.201 dg 192.168.0.1______________|
RRAS/NAT
192.168.21.1 dg blank-----------------------
|
|
machines in private LAN virtual network
192.168.21.x dg 192.168.21.1_____________|

"marcel" <marcel@xxxxxx> wrote in message
news:E83687D0-9DDF-4769-ADDD-175E3949EC4F@xxxxxx

Sorry about that. The formatting got messed up.

Internet
|
Gateway device
192.168.0.1
|
LAN machines
192.168.0.x dg 192.168.0.1
|
192.168.0.201 dg 192.168.0.1
RRAS/NAT
192.168.21.1 dg blank
|
machines in private LAN
192.168.21.x dg 192.168.21.1


"Bill Grant" <not.available@xxxxxx> wrote in message
news:u75FoAfmJHA.1216@xxxxxx