Re: setting up windows 2003 on virtual pc 2007

Comcast has nothing to do with it.

You don't create "networks",...they already exist. VirtualPC has 4.
You just have to associate them with an "adapter" on the physical Host. For
two machine to communicate they must use the same network and the network
must be associated with the same adapter.

Your options are:

1. Local Only
2. An actual adapter on the physical machine

I do not think you can use "Shared Networking NAT" for that.

If you use "Local Only" or a "Loopback Adapter" then your Vitual LAB cannot
connect to anything outside of the Virtual Network without a Virtual Machine
with 2-nics to act as a Firewall to carry them outside their own virtual
Network.
Do not multi-home the Domain Controller

If you use the actual physical machines adapter then the DHCP on the DC will
be in conflict with whatever you are using for DHCP on your LAN (like the
Comcast NAT Box).

It is not that complicated if you understand correct and proper networking
principles and you take the time to understand and think everything through.

All of my Virtual PC Labs that contain a "network" of multiple VMs use ISA
Server on Server2003 as the Firewall,...but you could use a 2-nic VM with
Server2003 runnig RRAS as a NAT box or use a 2-nic VM wirth XP running ICS.
XP would eat up less resources from the parent Host.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------





"lee720" <u58994@uwe> wrote in message news:a58cf89386009@uwe...
>I have virtual pc 2007. I have installed server 2003 and windows xp 2003. I
> would like to create a virtual network attaching my server to my windows
> xp
> operating system. I've installed active directory created a domain name
> and
> went through the process. . I prefer dynamic over static. I have setup
> active directory with a domain name and dns. I also set up DHCP. Can I do
> it
> with comcast.net on my server with any IP address. or even on my company
> network. cd drives are set as primary controllers.
> I have tried connecting and I get an error can't find domain.I am so
> frustrated . I can connect to the internet on server 2003 and xp 2003.
> Maybe
> someone can explain to me how to properly setup my server thorugh
> micorsoft
> virtual PC 2007 so I can connect to xp. I know it has to do with my IP
> address for dhcp settings settings.that t will connect to my workstaion.
> My
> hardisk 1 for server and xp are setup on 2 different directories on my C
> drive. Don't know if tha matters or not What am I doing wrong. Any help
> would
> be appreciated.
>
> Lee
>

If you are running AD you should not be using DHCP from a router, and the
DC should have a static IP.

I would recommend that you run your domain in Local Only. You can
then set up your domain in its own IP subnet. You can even run your own DHCP
service because you are on your own network.

If you want to connect this network to an existing network (home or
work) the best solution is to run a NAT router in a vm (one NIC in the
private network and one linked to a physical network). Your network can
access the physical network (and the Internet) but your network is not
visible from the "public" network.


"lee720" <u58994@uwe> wrote in message news:a58e42bad726f@uwe...
> Phillip Windell wrote:
>>Comcast has nothing to do with it.
>>
>>You don't create "networks",...they already exist. VirtualPC has 4.
>>You just have to associate them with an "adapter" on the physical Host.
>>For
>>two machine to communicate they must use the same network and the network
>>must be associated with the same adapter.
>>
>>Your options are:
>>
>>1. Local Only
>>2. An actual adapter on the physical machine
>>
>>I do not think you can use "Shared Networking NAT" for that.
>>
>>If you use "Local Only" or a "Loopback Adapter" then your Vitual LAB
>>cannot
>>connect to anything outside of the Virtual Network without a Virtual
>>Machine
>>with 2-nics to act as a Firewall to carry them outside their own virtual
>>Network.
>>Do not multi-home the Domain Controller
>>
>>If you use the actual physical machines adapter then the DHCP on the DC
>>will
>>be in conflict with whatever you are using for DHCP on your LAN (like the
>>Comcast NAT Box).
>>
>>It is not that complicated if you understand correct and proper networking
>>principles and you take the time to understand and think everything
>>through.
>>
>>All of my Virtual PC Labs that contain a "network" of multiple VMs use ISA
>>Server on Server2003 as the Firewall,...but you could use a 2-nic VM with
>>Server2003 runnig RRAS as a NAT box or use a 2-nic VM wirth XP running
>>ICS.
>>XP would eat up less resources from the parent Host.
>>
>>>I have virtual pc 2007. I have installed server 2003 and windows xp 2003.
>>>I
>>> would like to create a virtual network attaching my server to my
>>> windows
>>[quoted text clipped - 20 lines]
>>>
>>> Lee
> Phillip
>
> I want to thank you for you email. After reading it over, it made sense. I
> was finally able to make a connection from my server to my workstation.
> The
> problem was the conflict with the DHCP and the DC as well as not using my
> nic
> card from my host computer. Thanks again. I appreciate your help.
>
> Lee
>

"lee720" <u58994@uwe> wrote in message news:a58e42bad726f@uwe...
> Phillip Windell wrote:
>>Comcast has nothing to do with it.

> I want to thank you for you email. After reading it over, it made sense. I
> was finally able to make a connection from my server to my workstation.
> The
> problem was the conflict with the DHCP and the DC as well as not using my
> nic
> card from my host computer. Thanks again. I appreciate your help.

Sounds like you may have done the opposite of what I said. See Bill Grant's
reply. We are both saying the same thing.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"lee720 via WinServerKB.com" <u58994@uwe> wrote in message
news:a5988f576045a@uwe...

> Am I setting the NAT router in virtual memory to both my server and
> workstation.

A "NAT router in virtual memory"??? There is no such thing.

> Do I need to create a Virtual private network?

A VPN?? .....No.

Read the documentation for VirtualPC. It is a very simple product.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"lee720 via WinServerKB.com" <u58994@uwe> wrote in message
news:a5988f576045a@uwe...
> Bill Grant wrote:
>>If you are running AD you should not be using DHCP from a router, and the
>>DC should have a static IP.
>>
> Bill,
> Could you explain more what you mean my one NIC in the
>>private network and one linked to a physical network). Am I setting the
>>NAT router in virtual memory to both my server and workstation. Do I need
>>to create a Virtual private network? How do I link it to the physical
>>network. This is kind of new for me. Any more suggestions can help.
>
> Thanks,
>
> Lee
/201003/1
>
>

NAT is a very simple process. It allows a subnet to share a connection.
It was originally designed to allow a private subnet to share a public
(Internet) connection. Most DSL "routers" are NAT devices which do just
that. It does a simple address translation so that all traffic on the
"public" network uses the IP of the NAT device, not the original client's
private address. The NAT device makes the connection to the remote server
using its own public IP then relays the data to the machine on the private
LAN.

NAT works fine to allow client machines to access Internet sites. The NAT
device looks after the address translation and also forwards DNS requests.
However is comes unstuck if you install Active Directory. AD needs to use
the local DNS, not some public DNS server. Once you install a DC you need to
modify how DNS works. You also need to change how DHCP operates. The clients
need to use the local DNS, not use the NAT device.

There are basically two ways to handle this. If you want to run AD in the
same subnet as the NAT device, you need to have access to the NAT device and
be able to change its settings. If you can alter the DHCP settings so that
it hands out your server's IP for DNS (instead of its own IP) you are in
business. All you need to do is modify your local DNS to forward to a public
DNS service (so that it can resolve foreign URLs as well as local AD
resources) and everything works.

If your NAT device comes from an ISP and they do not give you access to
it, your best bet is to set up AD on its own subnet and install an
additional NAT router of your own. This is similar to running a private LAN
behind a DMZ. There is another subnet between the private LAN and the public
Internet. eg

Internet
|
public IP
NAT
192.168.0.1
|
192.168.0.2 dg 192.168.0.1
your router
192.168.31.1 dg blank
|
DC
192.168.31.11 dg 192.168.31.1
|
workstations
192.168.31.x dg 192.168.31.1 dns 192.168.31.11

Your private LAN has no direct connection to the ISP router. You can run
your own DHCP server if you want because you are in your own network.

You probably noticed that I have not mentioned virtual machines or virtual
networks. That is because you need to do these things regardless of whether
you have virtual machines or not. If you are talking about virtual machines,
the second scenario above is the one I use. With VPC, your private LAN
(192.168.31.0/24) is in local only. Your local NAT router is a vm with one
NIC in local only and one NIC linked to the physical network and the ISP NAT
device. You can use Windows Server with RRAS/NAT or Linux or whatever as
your NAT router.