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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4803CE7-F321-42FA-ABC2-73812543B31E@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE0659F8-91F1-4ACD-8733-D5EFEF4A2C5B@xxxxxxxxxxxxxxxx
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.






.

Relevant Pages

  • Re: DNS, DHCP and classes
    ... I can't help with the DNS and DHCP changes, but I do want to clarify what you're doing so that someone else may be able to help on where your problem may lie. ... DHCP is set up to recognise all three networks and ignore requests from the 10/24 network. ... All bits set on a host address is a broadcast address for that network. ...
    (uk.comp.os.linux)
  • Re: ESX Vmware Physically connected to different segments
    ... If something like this is found, I'm optimistic that someone will provide a xen patch (if not then we watch for people taking advantage of that exploit, maybe installing KLM in guest systems, no windows guests, etc). ... host specifically. ... virtualization techniques that allow for greater use of the devices we ... While there are fun ways to attack network vlans to ...
    (Pen-Test)
  • Re: Routing from local to local network
    ... DNS assumes that you are _running_ a DNS server on that host. ... Windoze may or may not follow redirects. ... What about the computers on the 192.168.0.x network. ...
    (alt.linux)
  • Re: DNS, DHCP and classes
    ... I can't help with the DNS and DHCP changes, but I do want to clarify what you're doing so that someone else may be able to help on where your problem may lie. ... DHCP is set up to recognise all three networks and ignore requests from the 10/24 network. ... All bits set on a host address is a broadcast address for that network. ...
    (uk.comp.os.linux)
  • Re: Web Site Mystery
    ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see the ... www.europacrown.com don't work from our corporate network. ...
    (microsoft.public.windows.server.general)