Thanks Paul.
I do understand about having to use different IP addresses in a different
subnet, I'm just not sure how to get Active Directory to do the proper
routing *between* those 2 subnets. I don't know if I need to just create a
separate subnet in Sites & Services under the same site or if I need a whole
new site or if I have to add new NIC's to every one of our servers or what.
I would imagine that there is something I need to do in DNS to get the
routing part of it to work, I just don't know what that something is.
I guess the question I'm asking, which is perhaps only partially related to
this initial post and should be asked in a different thread, is, "If you were
in charge of an Active Directory forest/tree/network/thing and you were
quickly running out of IP addresses in the default subnet, how would you
setup a separate subnet or site or whatever so that you could continue adding
computers to your current network and all the machines could still talk to
each other?" Maybe that's a bit more descriptive than my original question.
That's the actual problem I'm facing.
Thanks again
Paul Bergson said:
From what I understood the same set of IP address are being used in both
sub-nets. The router only knows about unique sub-nets. If a second subnet
is created with the same set of addresses there is no way other than on the
local lan can addresses be forwarded. Each subnet needs its own set of
addresses. Change the third octet from a 1 to a 2 ... 192.168.2.x
"The single DC in DOMAINB does not host a DHCP server, and for example, the
DOMAINB DC's fixed IP address is 192.168.1.53; it's
subnet is 192.168.1.x. This is the same subnet as all the computers in
DOMAINA."
--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
This posting is provided "AS IS" with no warranties, and confers no rights.
Can you expand on this "...unique addressing that is routable between the
two"? My problem is that I am running out of IP addresses on DOMAINA and
want to begin using a 2nd subnet using the same domain name, DC's, gateway,
etc. I'm really not sure where to begin.
TIA :-]
-Brian
:
Correct
Different subnet different range of addresses. You don't need dhcp
(If
you
used fixed) but you do need unique addressing that is routable
between
the
two.
--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
This posting is provided "AS IS" with no warranties, and confers no rights.
Okay, I think I get what you're saying, but now I think I have something
in
DOMAINB set up wrong.
I am thinking this is wrong because from what you suggested,
there's
no
way
to assign a new zone, which would be the same zone for both
DOMAINA
and
DOMAINB, right?
I don't know what I'm doing, yes, but I might if I can get past
this!
I
hope this makes sense. Thanks for your help.
:
Once you have Domain B up and running you could make a secondary DNS
zone of
A in B and B in A. Once this is done you should be able to setup a
trust
between the two. Also setup Domain B's DNS server to "Forward" unknown
requests to Domain A.
Here is a white paper on DNS
http://support.microsoft.com/default.aspx?scid=kb;en-us;298448
--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
This posting is provided "AS IS" with no warranties, and confers no
rights.
I have a Windows 2000 network (with 1 NT client) with 2 DCs, firewall
and
router to a T-1 connection. There is a single domain
DOMAINA.com.
In
a
lab
environment, I want to create a new domain DOMAINB.com that
uses
the
gateway
to get out to the internet, but whose members can access
resources
in
DOMAINA
and visa versa.
I already attempted doing this by installing Win2000 Server on
a
new
box
as
a DC with DNS and Active Directory. At one point I managed to tell
this
new
DOMAINB to trust DOMAINA and was able to see computers in the DOMAINA
network, but we made changes to DNS in DOMAINA that may have nullified
that.
I'm ready to start again, so any suggestions to make a fresh
start
and
