simple networking question

  • Thread starter Thread starter pete0085
  • Start date Start date
P

pete0085

Guest
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.
 
Re: simple networking question

Where are your computers getting their IP address from? The router?

To make this a good Active Directory simulation, to study from, you should
disable DHCP on your router. And setup DHCP on a Domain Controller.
But if your DC is a VPC, than your hardware PC's would have a problem, if
they're going to get DHCP addresses from the DC.

Can you ping by IP address right now? If so, you've got DNS problems.

Before writing a lot on what you could or should do; is making one of your
PC's a DC an option? Not a VPC, but a hardware PC? That would be the best
way to go.



"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> 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.
 
Re: simple networking question

I can make one of the virtual server's a DC and add the second virtual pc to
the domain. It is asking me to set a specific ip address for each server,
but not sure if its necessary.

I can't make the physical pc a DC as you mentioned. The router has DHCP
enabled. I tried setting a manaul ip address givien the gateway of
192.168.1.1 and using the dns of my ISP.

I will first try to make the first virtual server as a DC and add dhcp.
Unless someone else has a better idea.


"JohnB" wrote:

> Where are your computers getting their IP address from? The router?
>
> To make this a good Active Directory simulation, to study from, you should
> disable DHCP on your router. And setup DHCP on a Domain Controller.
> But if your DC is a VPC, than your hardware PC's would have a problem, if
> they're going to get DHCP addresses from the DC.
>
> Can you ping by IP address right now? If so, you've got DNS problems.
>
> Before writing a lot on what you could or should do; is making one of your
> PC's a DC an option? Not a VPC, but a hardware PC? That would be the best
> way to go.
>
>
>
> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> > 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.
>
>
>
 
Re: simple networking question

In a typical business network, one it seems that you're trying to simulate
for your test, servers that provide access to shared resources, printer,
folders, etc.... need to have a static IP address so that client computers
can find them reliably. On your DC, you will need to configure DNS for your
internal network and, by having a consistent IP address for the servers,
their host name resolution will also be consistent and reliable.

You'll also want a server to provide DHCP addresses to your client
computers, and with that address you will also specify the address of the
DNS server that your clients will use.

Do you see the problem you're going to run into if you have the router
configured for DHCP? How will servers and PC's on your private network
resolve DNS? You can't use your ISP's DNS servers for that. They can't see
your internal network.
And of course the additional problem you're going to have by having the DC
boot after the client is; how will your client PC's even be aware of... i.e.
login to, a Domain Controller?

Do you have access to a spare hard drive? If you don't want to mess with
one of your PC's, that would be an option, put a different drive in it, and
install Server 2003 on that. I went out and bought one of those hot-swap
bays, along with a spare drive. Then I just swap which ever drive I want in
that PC; the original XP drive, or the 2003 server drive.

It's going to be tough to do this "the right way" without making one of your
PC's a DC. Maybe someone else has a better idea.




"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:F1C1352A-D264-4523-AF93-293F14E246DC@microsoft.com...
>I can make one of the virtual server's a DC and add the second virtual pc
>to
> the domain. It is asking me to set a specific ip address for each server,
> but not sure if its necessary.
>
> I can't make the physical pc a DC as you mentioned. The router has DHCP
> enabled. I tried setting a manaul ip address givien the gateway of
> 192.168.1.1 and using the dns of my ISP.
>
> I will first try to make the first virtual server as a DC and add dhcp.
> Unless someone else has a better idea.
>
>
> "JohnB" wrote:
>
>> Where are your computers getting their IP address from? The router?
>>
>> To make this a good Active Directory simulation, to study from, you
>> should
>> disable DHCP on your router. And setup DHCP on a Domain Controller.
>> But if your DC is a VPC, than your hardware PC's would have a problem, if
>> they're going to get DHCP addresses from the DC.
>>
>> Can you ping by IP address right now? If so, you've got DNS problems.
>>
>> Before writing a lot on what you could or should do; is making one of
>> your
>> PC's a DC an option? Not a VPC, but a hardware PC? That would be the
>> best
>> way to go.
>>
>>
>>
>> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
>> > 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.
>>
>>
>>
 
Re: simple networking question

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@discussions.microsoft.com> wrote in message
news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> 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.
 
Re: simple networking question

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@discussions.microsoft.com> wrote in message
> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> > 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.
>
>
 
Re: simple networking question

There are several major problems with that.

1. You cannot run DHCP on a server if you already have DHCP running on
your NAT device. You will need to use static IP addresses for the second
network. You can only run a second DHCP server if it is isolated from the
physical network (such as running all vms in Local Only on the same host.
This requires a host with enough memory to host several guests).

2. It is not a good idea to join host machines to a domain when the DC
is running on a vm. (Incidently, vm is just an abbreviation for virtual
machine. It does not imply that you are using any particular sort of
virtualization). The DC may not be running when the host starts up and the
PC will have trouble logging on.

3. You should not really use 198.213.30.x as that is a registered public
network. 192.168.30.0/24 is fine, and should be different from your LAN. In
case you are not familiar with that format, 192.168.30.0/24 represents a
subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
255.255.255.0 (It should not really matter that you are using a public set
of IPs if you never connect this network to the internet).

The first thing you need to check in networking is that the machines you
are trying to network are actually in the same IP subnet. Do an ipconfig on
both vms and check that they are. If you cannot ping from one to another,
check that the firewalls are not blocking ICMP echo (which is what ping
uses).

"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
> 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@discussions.microsoft.com> wrote in message
>> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
>> > 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.
>>
>>
 
Re: simple networking question

I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10 for the
second server with a mask of 255.255.255.0. The dns on both is 10.0.0.1 with
no gateway. I removed the dhcp from server 1.

Does it matter that I have one virtual machince on a pc and the second
virtual pc installed on a laptop? Should I try to run them both on the same
machine or doesn't it matter?

They still can't ping eachother. The network settings for virtual pc are
set to local host. It's not neceassary for the the other to join the domain,
only to be able to communicate.

The ipconfig /all is showing the correct settings for both.

"Bill Grant" wrote:

> There are several major problems with that.
>
> 1. You cannot run DHCP on a server if you already have DHCP running on
> your NAT device. You will need to use static IP addresses for the second
> network. You can only run a second DHCP server if it is isolated from the
> physical network (such as running all vms in Local Only on the same host.
> This requires a host with enough memory to host several guests).
>
> 2. It is not a good idea to join host machines to a domain when the DC
> is running on a vm. (Incidently, vm is just an abbreviation for virtual
> machine. It does not imply that you are using any particular sort of
> virtualization). The DC may not be running when the host starts up and the
> PC will have trouble logging on.
>
> 3. You should not really use 198.213.30.x as that is a registered public
> network. 192.168.30.0/24 is fine, and should be different from your LAN. In
> case you are not familiar with that format, 192.168.30.0/24 represents a
> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
> 255.255.255.0 (It should not really matter that you are using a public set
> of IPs if you never connect this network to the internet).
>
> The first thing you need to check in networking is that the machines you
> are trying to network are actually in the same IP subnet. Do an ipconfig on
> both vms and check that they are. If you cannot ping from one to another,
> check that the firewalls are not blocking ICMP echo (which is what ping
> uses).
>
> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
> > 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@discussions.microsoft.com> wrote in message
> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> >> > 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.
> >>
> >>
>
>
 
Re: simple networking question

Are you pinging by host name or IP address?
I'm guessing you can ping by IP but not host name.

Is DNS setup on the DC?
If it isn't, what do you think is going to resolve the host name when you
ping a host in your internal network?

Again, your problem is, Active Directory is DNS based. You MUST have DNS
configured on your private network.

Another option for you - if your PC's have enough RAM - is to have your test
environment all virtual. That is; turn off DHCP on your router. Set all
computers to static IP.... i.e. 192.168.1.x
Set your 2 servers to static IP. Same subnet. And set your VPC's to be
DHCP, that they get from the DC. That will work, but it depends on how much
RAM you have on your PC's. You would be running 1 or 2, most likely 2....
VPC's from each PC. 512mb RAM might be too slow.



"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:B4803CE7-F321-42FA-ABC2-73812543B31E@microsoft.com...
>I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10 for the
> second server with a mask of 255.255.255.0. The dns on both is 10.0.0.1
> with
> no gateway. I removed the dhcp from server 1.
>
> Does it matter that I have one virtual machince on a pc and the second
> virtual pc installed on a laptop? Should I try to run them both on the
> same
> machine or doesn't it matter?
>
> They still can't ping eachother. The network settings for virtual pc are
> set to local host. It's not neceassary for the the other to join the
> domain,
> only to be able to communicate.
>
> The ipconfig /all is showing the correct settings for both.
>
> "Bill Grant" wrote:
>
>> There are several major problems with that.
>>
>> 1. You cannot run DHCP on a server if you already have DHCP running
>> on
>> your NAT device. You will need to use static IP addresses for the second
>> network. You can only run a second DHCP server if it is isolated from the
>> physical network (such as running all vms in Local Only on the same host.
>> This requires a host with enough memory to host several guests).
>>
>> 2. It is not a good idea to join host machines to a domain when the
>> DC
>> is running on a vm. (Incidently, vm is just an abbreviation for virtual
>> machine. It does not imply that you are using any particular sort of
>> virtualization). The DC may not be running when the host starts up and
>> the
>> PC will have trouble logging on.
>>
>> 3. You should not really use 198.213.30.x as that is a registered
>> public
>> network. 192.168.30.0/24 is fine, and should be different from your LAN.
>> In
>> case you are not familiar with that format, 192.168.30.0/24 represents a
>> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
>> 255.255.255.0 (It should not really matter that you are using a public
>> set
>> of IPs if you never connect this network to the internet).
>>
>> The first thing you need to check in networking is that the machines
>> you
>> are trying to network are actually in the same IP subnet. Do an ipconfig
>> on
>> both vms and check that they are. If you cannot ping from one to another,
>> check that the firewalls are not blocking ICMP echo (which is what ping
>> uses).
>>
>> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
>> > 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@discussions.microsoft.com> wrote in message
>> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
>> >> > 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.
>> >>
>> >>
>>
>>
 
Re: simple networking question

Well the problem is I can't even ping by IP address, that's my first concern.
I have two virtual servers. One with the ip aod 10.0.0.1, the other with
10.0.0.10, with no gateway.

I"m not sure why I can't even get them to ping, that's my first problem. I
might try a hub from work, but I've done this before, and remember I had some
weird settings for my dns to get them to communicate. Like the dns wasn't
the ip address of the server.

"JohnB" wrote:

> Are you pinging by host name or IP address?
> I'm guessing you can ping by IP but not host name.
>
> Is DNS setup on the DC?
> If it isn't, what do you think is going to resolve the host name when you
> ping a host in your internal network?
>
> Again, your problem is, Active Directory is DNS based. You MUST have DNS
> configured on your private network.
>
> Another option for you - if your PC's have enough RAM - is to have your test
> environment all virtual. That is; turn off DHCP on your router. Set all
> computers to static IP.... i.e. 192.168.1.x
> Set your 2 servers to static IP. Same subnet. And set your VPC's to be
> DHCP, that they get from the DC. That will work, but it depends on how much
> RAM you have on your PC's. You would be running 1 or 2, most likely 2....
> VPC's from each PC. 512mb RAM might be too slow.
>
>
>
> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> news:B4803CE7-F321-42FA-ABC2-73812543B31E@microsoft.com...
> >I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10 for the
> > second server with a mask of 255.255.255.0. The dns on both is 10.0.0.1
> > with
> > no gateway. I removed the dhcp from server 1.
> >
> > Does it matter that I have one virtual machince on a pc and the second
> > virtual pc installed on a laptop? Should I try to run them both on the
> > same
> > machine or doesn't it matter?
> >
> > They still can't ping eachother. The network settings for virtual pc are
> > set to local host. It's not neceassary for the the other to join the
> > domain,
> > only to be able to communicate.
> >
> > The ipconfig /all is showing the correct settings for both.
> >
> > "Bill Grant" wrote:
> >
> >> There are several major problems with that.
> >>
> >> 1. You cannot run DHCP on a server if you already have DHCP running
> >> on
> >> your NAT device. You will need to use static IP addresses for the second
> >> network. You can only run a second DHCP server if it is isolated from the
> >> physical network (such as running all vms in Local Only on the same host.
> >> This requires a host with enough memory to host several guests).
> >>
> >> 2. It is not a good idea to join host machines to a domain when the
> >> DC
> >> is running on a vm. (Incidently, vm is just an abbreviation for virtual
> >> machine. It does not imply that you are using any particular sort of
> >> virtualization). The DC may not be running when the host starts up and
> >> the
> >> PC will have trouble logging on.
> >>
> >> 3. You should not really use 198.213.30.x as that is a registered
> >> public
> >> network. 192.168.30.0/24 is fine, and should be different from your LAN.
> >> In
> >> case you are not familiar with that format, 192.168.30.0/24 represents a
> >> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
> >> 255.255.255.0 (It should not really matter that you are using a public
> >> set
> >> of IPs if you never connect this network to the internet).
> >>
> >> The first thing you need to check in networking is that the machines
> >> you
> >> are trying to network are actually in the same IP subnet. Do an ipconfig
> >> on
> >> both vms and check that they are. If you cannot ping from one to another,
> >> check that the firewalls are not blocking ICMP echo (which is what ping
> >> uses).
> >>
> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> >> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
> >> > 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@discussions.microsoft.com> wrote in message
> >> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> >> >> > 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.
> >> >>
> >> >>
> >>
> >>
>
>
>
 
Re: simple networking question

Check, on all PC's and VPC's, that the Windows firewall is disabled. It may
be enabled on the VPC's. That would be the cause of not being able to ping
by IP address.


"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:E8CAB5DD-2DC9-4D0F-A34F-D3FE3FE307DD@microsoft.com...
> Well the problem is I can't even ping by IP address, that's my first
> concern.
> I have two virtual servers. One with the ip aod 10.0.0.1, the other with
> 10.0.0.10, with no gateway.
>
> I"m not sure why I can't even get them to ping, that's my first problem.
> I
> might try a hub from work, but I've done this before, and remember I had
> some
> weird settings for my dns to get them to communicate. Like the dns wasn't
> the ip address of the server.
>
> "JohnB" wrote:
>
>> Are you pinging by host name or IP address?
>> I'm guessing you can ping by IP but not host name.
>>
>> Is DNS setup on the DC?
>> If it isn't, what do you think is going to resolve the host name when you
>> ping a host in your internal network?
>>
>> Again, your problem is, Active Directory is DNS based. You MUST have DNS
>> configured on your private network.
>>
>> Another option for you - if your PC's have enough RAM - is to have your
>> test
>> environment all virtual. That is; turn off DHCP on your router. Set all
>> computers to static IP.... i.e. 192.168.1.x
>> Set your 2 servers to static IP. Same subnet. And set your VPC's to be
>> DHCP, that they get from the DC. That will work, but it depends on how
>> much
>> RAM you have on your PC's. You would be running 1 or 2, most likely
>> 2....
>> VPC's from each PC. 512mb RAM might be too slow.
>>
>>
>>
>> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> news:B4803CE7-F321-42FA-ABC2-73812543B31E@microsoft.com...
>> >I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10 for
>> >the
>> > second server with a mask of 255.255.255.0. The dns on both is 10.0.0.1
>> > with
>> > no gateway. I removed the dhcp from server 1.
>> >
>> > Does it matter that I have one virtual machince on a pc and the second
>> > virtual pc installed on a laptop? Should I try to run them both on the
>> > same
>> > machine or doesn't it matter?
>> >
>> > They still can't ping eachother. The network settings for virtual pc
>> > are
>> > set to local host. It's not neceassary for the the other to join the
>> > domain,
>> > only to be able to communicate.
>> >
>> > The ipconfig /all is showing the correct settings for both.
>> >
>> > "Bill Grant" wrote:
>> >
>> >> There are several major problems with that.
>> >>
>> >> 1. You cannot run DHCP on a server if you already have DHCP
>> >> running
>> >> on
>> >> your NAT device. You will need to use static IP addresses for the
>> >> second
>> >> network. You can only run a second DHCP server if it is isolated from
>> >> the
>> >> physical network (such as running all vms in Local Only on the same
>> >> host.
>> >> This requires a host with enough memory to host several guests).
>> >>
>> >> 2. It is not a good idea to join host machines to a domain when
>> >> the
>> >> DC
>> >> is running on a vm. (Incidently, vm is just an abbreviation for
>> >> virtual
>> >> machine. It does not imply that you are using any particular sort of
>> >> virtualization). The DC may not be running when the host starts up and
>> >> the
>> >> PC will have trouble logging on.
>> >>
>> >> 3. You should not really use 198.213.30.x as that is a registered
>> >> public
>> >> network. 192.168.30.0/24 is fine, and should be different from your
>> >> LAN.
>> >> In
>> >> case you are not familiar with that format, 192.168.30.0/24 represents
>> >> a
>> >> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
>> >> 255.255.255.0 (It should not really matter that you are using a
>> >> public
>> >> set
>> >> of IPs if you never connect this network to the internet).
>> >>
>> >> The first thing you need to check in networking is that the
>> >> machines
>> >> you
>> >> are trying to network are actually in the same IP subnet. Do an
>> >> ipconfig
>> >> on
>> >> both vms and check that they are. If you cannot ping from one to
>> >> another,
>> >> check that the firewalls are not blocking ICMP echo (which is what
>> >> ping
>> >> uses).
>> >>
>> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> >> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
>> >> > 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@discussions.microsoft.com> wrote in message
>> >> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
>> >> >> > 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.
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
>>
 
Re: simple networking question

I checked this before. I enabled icmp echo request to verify nothing is
being blocked.

What else should I try? I'm completely lost. I've set up a network for my
company so why can't I network two pcs together??

This doesn't make any sense.

"JohnB" wrote:

> Check, on all PC's and VPC's, that the Windows firewall is disabled. It may
> be enabled on the VPC's. That would be the cause of not being able to ping
> by IP address.
>
>
> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> news:E8CAB5DD-2DC9-4D0F-A34F-D3FE3FE307DD@microsoft.com...
> > Well the problem is I can't even ping by IP address, that's my first
> > concern.
> > I have two virtual servers. One with the ip aod 10.0.0.1, the other with
> > 10.0.0.10, with no gateway.
> >
> > I"m not sure why I can't even get them to ping, that's my first problem.
> > I
> > might try a hub from work, but I've done this before, and remember I had
> > some
> > weird settings for my dns to get them to communicate. Like the dns wasn't
> > the ip address of the server.
> >
> > "JohnB" wrote:
> >
> >> Are you pinging by host name or IP address?
> >> I'm guessing you can ping by IP but not host name.
> >>
> >> Is DNS setup on the DC?
> >> If it isn't, what do you think is going to resolve the host name when you
> >> ping a host in your internal network?
> >>
> >> Again, your problem is, Active Directory is DNS based. You MUST have DNS
> >> configured on your private network.
> >>
> >> Another option for you - if your PC's have enough RAM - is to have your
> >> test
> >> environment all virtual. That is; turn off DHCP on your router. Set all
> >> computers to static IP.... i.e. 192.168.1.x
> >> Set your 2 servers to static IP. Same subnet. And set your VPC's to be
> >> DHCP, that they get from the DC. That will work, but it depends on how
> >> much
> >> RAM you have on your PC's. You would be running 1 or 2, most likely
> >> 2....
> >> VPC's from each PC. 512mb RAM might be too slow.
> >>
> >>
> >>
> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> >> news:B4803CE7-F321-42FA-ABC2-73812543B31E@microsoft.com...
> >> >I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10 for
> >> >the
> >> > second server with a mask of 255.255.255.0. The dns on both is 10.0.0.1
> >> > with
> >> > no gateway. I removed the dhcp from server 1.
> >> >
> >> > Does it matter that I have one virtual machince on a pc and the second
> >> > virtual pc installed on a laptop? Should I try to run them both on the
> >> > same
> >> > machine or doesn't it matter?
> >> >
> >> > They still can't ping eachother. The network settings for virtual pc
> >> > are
> >> > set to local host. It's not neceassary for the the other to join the
> >> > domain,
> >> > only to be able to communicate.
> >> >
> >> > The ipconfig /all is showing the correct settings for both.
> >> >
> >> > "Bill Grant" wrote:
> >> >
> >> >> There are several major problems with that.
> >> >>
> >> >> 1. You cannot run DHCP on a server if you already have DHCP
> >> >> running
> >> >> on
> >> >> your NAT device. You will need to use static IP addresses for the
> >> >> second
> >> >> network. You can only run a second DHCP server if it is isolated from
> >> >> the
> >> >> physical network (such as running all vms in Local Only on the same
> >> >> host.
> >> >> This requires a host with enough memory to host several guests).
> >> >>
> >> >> 2. It is not a good idea to join host machines to a domain when
> >> >> the
> >> >> DC
> >> >> is running on a vm. (Incidently, vm is just an abbreviation for
> >> >> virtual
> >> >> machine. It does not imply that you are using any particular sort of
> >> >> virtualization). The DC may not be running when the host starts up and
> >> >> the
> >> >> PC will have trouble logging on.
> >> >>
> >> >> 3. You should not really use 198.213.30.x as that is a registered
> >> >> public
> >> >> network. 192.168.30.0/24 is fine, and should be different from your
> >> >> LAN.
> >> >> In
> >> >> case you are not familiar with that format, 192.168.30.0/24 represents
> >> >> a
> >> >> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0 netmask
> >> >> 255.255.255.0 (It should not really matter that you are using a
> >> >> public
> >> >> set
> >> >> of IPs if you never connect this network to the internet).
> >> >>
> >> >> The first thing you need to check in networking is that the
> >> >> machines
> >> >> you
> >> >> are trying to network are actually in the same IP subnet. Do an
> >> >> ipconfig
> >> >> on
> >> >> both vms and check that they are. If you cannot ping from one to
> >> >> another,
> >> >> check that the firewalls are not blocking ICMP echo (which is what
> >> >> ping
> >> >> uses).
> >> >>
> >> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
> >> >> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
> >> >> > 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@discussions.microsoft.com> wrote in message
> >> >> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
> >> >> >> > 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.
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
 
Re: simple networking question

Try a tracert to see where the IP communication is dieing

Can the hardware PC's ping each other?


"pete0085" <pete0085@discussions.microsoft.com> wrote in message
news:E675223F-B69F-4B7C-8ADF-98E391472E4D@microsoft.com...
>I checked this before. I enabled icmp echo request to verify nothing is
> being blocked.
>
> What else should I try? I'm completely lost. I've set up a network for
> my
> company so why can't I network two pcs together??
>
> This doesn't make any sense.
>
> "JohnB" wrote:
>
>> Check, on all PC's and VPC's, that the Windows firewall is disabled. It
>> may
>> be enabled on the VPC's. That would be the cause of not being able to
>> ping
>> by IP address.
>>
>>
>> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> news:E8CAB5DD-2DC9-4D0F-A34F-D3FE3FE307DD@microsoft.com...
>> > Well the problem is I can't even ping by IP address, that's my first
>> > concern.
>> > I have two virtual servers. One with the ip aod 10.0.0.1, the other
>> > with
>> > 10.0.0.10, with no gateway.
>> >
>> > I"m not sure why I can't even get them to ping, that's my first
>> > problem.
>> > I
>> > might try a hub from work, but I've done this before, and remember I
>> > had
>> > some
>> > weird settings for my dns to get them to communicate. Like the dns
>> > wasn't
>> > the ip address of the server.
>> >
>> > "JohnB" wrote:
>> >
>> >> Are you pinging by host name or IP address?
>> >> I'm guessing you can ping by IP but not host name.
>> >>
>> >> Is DNS setup on the DC?
>> >> If it isn't, what do you think is going to resolve the host name when
>> >> you
>> >> ping a host in your internal network?
>> >>
>> >> Again, your problem is, Active Directory is DNS based. You MUST have
>> >> DNS
>> >> configured on your private network.
>> >>
>> >> Another option for you - if your PC's have enough RAM - is to have
>> >> your
>> >> test
>> >> environment all virtual. That is; turn off DHCP on your router. Set
>> >> all
>> >> computers to static IP.... i.e. 192.168.1.x
>> >> Set your 2 servers to static IP. Same subnet. And set your VPC's to
>> >> be
>> >> DHCP, that they get from the DC. That will work, but it depends on
>> >> how
>> >> much
>> >> RAM you have on your PC's. You would be running 1 or 2, most likely
>> >> 2....
>> >> VPC's from each PC. 512mb RAM might be too slow.
>> >>
>> >>
>> >>
>> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> >> news:B4803CE7-F321-42FA-ABC2-73812543B31E@microsoft.com...
>> >> >I used your advice and stuck used 10.0.0.1 for the DC and 10.0.0.10
>> >> >for
>> >> >the
>> >> > second server with a mask of 255.255.255.0. The dns on both is
>> >> > 10.0.0.1
>> >> > with
>> >> > no gateway. I removed the dhcp from server 1.
>> >> >
>> >> > Does it matter that I have one virtual machince on a pc and the
>> >> > second
>> >> > virtual pc installed on a laptop? Should I try to run them both on
>> >> > the
>> >> > same
>> >> > machine or doesn't it matter?
>> >> >
>> >> > They still can't ping eachother. The network settings for virtual
>> >> > pc
>> >> > are
>> >> > set to local host. It's not neceassary for the the other to join
>> >> > the
>> >> > domain,
>> >> > only to be able to communicate.
>> >> >
>> >> > The ipconfig /all is showing the correct settings for both.
>> >> >
>> >> > "Bill Grant" wrote:
>> >> >
>> >> >> There are several major problems with that.
>> >> >>
>> >> >> 1. You cannot run DHCP on a server if you already have DHCP
>> >> >> running
>> >> >> on
>> >> >> your NAT device. You will need to use static IP addresses for the
>> >> >> second
>> >> >> network. You can only run a second DHCP server if it is isolated
>> >> >> from
>> >> >> the
>> >> >> physical network (such as running all vms in Local Only on the same
>> >> >> host.
>> >> >> This requires a host with enough memory to host several guests).
>> >> >>
>> >> >> 2. It is not a good idea to join host machines to a domain when
>> >> >> the
>> >> >> DC
>> >> >> is running on a vm. (Incidently, vm is just an abbreviation for
>> >> >> virtual
>> >> >> machine. It does not imply that you are using any particular sort
>> >> >> of
>> >> >> virtualization). The DC may not be running when the host starts up
>> >> >> and
>> >> >> the
>> >> >> PC will have trouble logging on.
>> >> >>
>> >> >> 3. You should not really use 198.213.30.x as that is a
>> >> >> registered
>> >> >> public
>> >> >> network. 192.168.30.0/24 is fine, and should be different from your
>> >> >> LAN.
>> >> >> In
>> >> >> case you are not familiar with that format, 192.168.30.0/24
>> >> >> represents
>> >> >> a
>> >> >> subnet wirh a 24-bit subnet and is equivalent to 192.168.30.0
>> >> >> netmask
>> >> >> 255.255.255.0 (It should not really matter that you are using a
>> >> >> public
>> >> >> set
>> >> >> of IPs if you never connect this network to the internet).
>> >> >>
>> >> >> The first thing you need to check in networking is that the
>> >> >> machines
>> >> >> you
>> >> >> are trying to network are actually in the same IP subnet. Do an
>> >> >> ipconfig
>> >> >> on
>> >> >> both vms and check that they are. If you cannot ping from one to
>> >> >> another,
>> >> >> check that the firewalls are not blocking ICMP echo (which is what
>> >> >> ping
>> >> >> uses).
>> >> >>
>> >> >> "pete0085" <pete0085@discussions.microsoft.com> wrote in message
>> >> >> news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@microsoft.com...
>> >> >> > 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@discussions.microsoft.com> wrote in message
>> >> >> >> news:D933C22D-0D12-44C6-B1A5-F581D92F859E@microsoft.com...
>> >> >> >> > 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.
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
 
Re: simple networking question

I end up installing both virtual machines on the same physical host. I was
able to ping the router and both pcs. After a reboot I was able to add the
second server to the domain.

There must of been some problems with the second physical host and virtual
pc interacting. I have no idea what, but since I have enough memory, this
solves the problem and probably makes it easier too. No need to have a
second pc on my desk. It makes my host pc slow, but it works, that's all I
care about.

Wish I would have tried this a few days ago.

Thanks for all your help on this.


"JohnB" wrote:

> Try a tracert to see where the IP communication is dieing
>
> Can the hardware PC's ping each other?
>
>
 
networking in win2003

networking in win2003

Y didn't u try to make both pc addresses in a same subnet. and u have to disable dhcp in DC. obtain it from local interface(from ur router). and drives of the router has to be installed in he DC also(VPC). then connect the other using the router or what ever. assign a static address in the same subnet with DNS address in the router. this will do it.........
 
Back
Top