Re: simple networking question
- From: pete0085 <pete0085@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 May 2008 19:49:01 -0700
In the past I was able to somehow get it to work, but I added one of my
physical pcs to the domain. That would work as well, they would be connected
together.
I'm not using VM, using virtual pc 2007. Not sure how similar they are.
My linksys router is on the 192.168.x.x network. On the DC, I created the
network of 198.213.30.1, used the .1 as my dns. Created a dhcp scope on the
DC.
On the client pc, set to obtain address automatically and set the dns at the
30.1 address.
I cannot ping from either pc or add it to the domain. Don't understand why,
I was able to do this before running virtual pc.
"Bill Grant" wrote:
It really depends on what you want to do. If you set the NIC in a vm to.
link to the network through the physical NIC in the host, it looks just like
another machine on the network (from a networking point of view). So you
effectively have four machines on the network, two hosts and two guests.
If the servers are set to get an IP automatically they should get their
network config from DHCP on your Linksys and be able to see each other, the
hosts and the Internet.
If you want to experiment with Active Directory, this is not the way to
do it (with virtual or hard metal machines). Active Directory does not work
well with the DHCP or DNS of a simple NAT setup as above.
If you don't need Internet access you can run your domain on the same
network using a different IP subnet. (This is called a logical subnet which
shares the underlying "wire"). If your LAN is using say 10.1.1.x addresses,
use 192.168..x.x addresses for your logical subnet. Set your DC to say
192.168.31.1/24 . Run dcpromo and allow it to configure DNS for you. When AD
is installed, set the second server to 192.168.31.2/24 using 192.168.31.1
for DNS. You don't need a default gateway if you don't need access to any
other network. You now have two logical networks running on the same
segment.
The machines on your physical LAN will not be aware of your virtual
machines and vice versa. They would only see each other if you installed a
router to route between the subnets.
"pete0085" <pete0085@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D933C22D-0D12-44C6-B1A5-F581D92F859E@xxxxxxxxxxxxxxxx
Hopefully this isn't a "dumb" question. I'm setting up a lab at home to
work
on my 291 exam. I am running server 2003 on virtual pc installed on two
different pcs. I need the two to be able to communicate.
I attempted to use my liksys router and had them both hooked up to the
router, using the same gateway. They were not able to communicate (ping).
I
don't believe its necessary to get out to the internet.
Would I need to use a hub instead and plug them both into a small hub?
Sorry if this is too easy of a question. Neither of the virtual pcs are
set
up as a DC.
- Follow-Ups:
- Re: simple networking question
- From: Bill Grant
- Re: simple networking question
- References:
- simple networking question
- From: pete0085
- Re: simple networking question
- From: Bill Grant
- simple networking question
- Prev by Date: Domain Controller becomes unresponsive after 7 days
- Next by Date: Re: Force install of XP app (on Server).
- Previous by thread: Re: simple networking question
- Next by thread: Re: simple networking question
- Index(es):
Relevant Pages
|
