Changing IP Address on DCs to allow room for new child domains

[Bill Lucas]

We are adding 2 new child domains to our Win 2000 AD domain but are low on
available IP addresses (Currently in the Range 192.168.99.X). We are too
low on them to accommodate IP Address Requirements if we partition the
available ranges using subnet masks. So we want to move our current DCs
from (for Example) 192.168.99.1 and 192.168.99.2 to 172.16.1.1 and
172.16.1.2 and then add domain controllers for each of the new child domains
in the range 172.16.2.1 and 172.16.3.1 Thus allowing each domain 255 IPs to
start off.

Since these are the old class b notation we should have a subnet mask of
255.255.0.0 and should not have problems with traffic between IP ranges
correct?

Does this approach make sense and are there any gotchas for changing the IP
Address on the Current Domain Controllers I should be aware of since the
change will be to a new address range? I know we will need a new DHCP
Scope but what if anything (besides IPCONFIG/ registerDNS) will need to be
done to AD Integrated DNS Servers? What about WINS (Not sure what we use
that for anymore but it is there)? any other areas I am going to need to
touch?

Any other tips tricks or gotchas would also be welcomed. This is my first
time trying to do something like this and I "better not bring down the whole
&*%$)@#^ Network."

TIA
Bill

 

[Brian Oakes [MSFT]]

The only potential problem that I can thing of is based on the subnet mask.
When you use a class b mask you are saying that all these ranges are local
to me, i.e. if I need to get to another IP address I will arp for the IP
address. Since my subnet considers it local, then it won't goto my default
gateway.

If you have these sites as separate physical locations that have to cross
routers etc, then you can have a serious problem. If these are all on 1 big
LAN segment, then you should be ok. I.e., we will arp locally and we will
find the system we are trying to access and goto it locally.

There are plenty of networking tricks you can do, and implement to work
around situations like this, but just remember the note above.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.

 

[Bill Lucas]

Thanks for the thought. we are still rather small and only have 1 segment
to our network. The only router we have in the place is our Gateway to thhe
internet, so the multiple segment issue shouldn't be a big deal (at least
for a few years yet). We are moving to this address range because we don't
have internal routers to handle differnt class c ranges. That was my
original solution, but for simplicity they liked this one better.

Thanks for the reply., and I'll keep it in mind.

 

[Brian Oakes [MSFT]]

cool.

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.