IP Scopes

  • Thread starter Thread starter vincent
  • Start date Start date
V

vincent

Hi

I'm try to built a new win2003 network in my office, I
currently have an existing NT network with 4 server and
approx 15 to 20 client, where my dc run dhcp

The ips that are used range from 10.0.0.0 through to
10.0.0.254, where 10.0.0.254 is the default gateway.
Everything work fine and has been for years

At the moment I have created a new domain on a win2003 box
and got active dir set up, but now i have a problem when
trying to set up dhcp on win 2003, i simply do not know
where to start when it comes to telling dhcp what ip's and
subnet masks to use, im completely confused,

Is it possible to create a new scope from my existing ip
addresses that i have on my other network????

can anyone point me in the correct direction please

Cheers

Vincent
 
The new scope wizard walks you through this process. Here's how to install
and configure a DHCP server in Windows 2003:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323360

If you want to duplicate your existing scope, the address range is 10.0.0.1
to 10.0.0.254, the subnet mask is 255.255.255.0. You should exclude the IP
address of the Windows Server 2003 machine and any other machines which have
fixed IPs. In your scope options, you should also include the IP address of
the Windows 2003 machine as the DNS server for your DHCP clients.

You will have to shut down, disconnect, or disable the existing DHCP server
when you bring the new DHCP server online.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Thanks for the reply Doug, I kind of thought thats what
you would have to do, the problem that i face is that
management (non IT) want to keep running the existing nt
domain and buid this new 2003 side by side untill its up
and running and then eliminate the nt4 domain

The only way that i could see that happening is to get a
new router, and switch and do it that way, thus creating a
new independant network

Is it possible to add in a 2003 box into the existing nt4
domain? as far as i understand, you have 2 options when
doing this either, upgrade the existing nt4 domain or
build a new network

for example say my current domain name is microsoft under
NT, when i create a new 2003 dc the domain would then
become something like microsoft.local, you would then have
to get the clients to connect to this domain and as a
result they would loose all the features of the old domain
like email, file servers etc

Could you do this!!!!
 
You are correct. You can join a Win2003 server to an NT domain, but you
can't make it a domain controller in that domain. If you want to do an in
place upgrade, you must upgrade the NT PDC to Windows 2003.

The parallel domain/switch over is probably a good solution for your
situation. There are migration tools available; however, with only 15-20
users, I think the parallel-from-scratch solution is both practical, and has
less risk, and gives better results. You could create the Active Directory
domain on the same subnet as the existing NT4.0 domain, but this will cause
unnecessary conflicts. You are better off using a separate network segment
and different IP subnet for your AD domain. However, you do not necessarily
need a new router device - Windows 2003 makes an excellent router - just add
a second NIC and enable IP routing. This will give the Active Directory
server an interface on both subnets. Also, you can configure domain trusts
between your Active Directory domain and your NT4.0 domain so that users can
access resources in both while you get ready for a complete switch over.
See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;325874

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
There is no relationship between IP# Ranges and Windows Domains. You could
have 10 Windows Domains running all on the same IP# Range or you could have
a dozen different IP# Ranges and run only a single Windows Domain on it.
There is no relationship between the two.

DHCP is a non-issue,...it has nothing to do with Windows Domains. You have
have multiple DHCP Servers supplying the same Subnet (if done
carefully),...you can also have one DHCP Server a dozen Subnets. So there
is no relationship between the number of DHCP Servers you run and the number
of Subnets you have. And none of it has anything to do with Windows Domains.

Can you make it more clear what the real goal is?
 
Back
Top