DNS & DHCP

  • Thread starter Thread starter just1coder
  • Start date Start date
J

just1coder

Can I setup a Windows 2000 Server to act as the DNS & DHCP server for a
Windows NT Domain?
 
Run the DHCP from the NT machine if this is an NT4 based domain. DHCP with
2000 and 2003 needs to be authorized by the Domain Controller which NT4 DCs
cannot do. There are workarounds but it is just too much trouble. You can
run DNS where ever you like, NT4 domains are Netbios-Based and don't depend
on DNS so it isn't critical.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
 
Thanks! Is the upgrade to AD pretty straightforward? I am running into
more and more bottlenecks caused by NT :)

Phillip said:
Run the DHCP from the NT machine if this is an NT4 based domain. DHCP with
2000 and 2003 needs to be authorized by the Domain Controller which NT4 DCs
cannot do. There are workarounds but it is just too much trouble. You can
run DNS where ever you like, NT4 domains are Netbios-Based and don't depend
on DNS so it isn't critical.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


Can I setup a Windows 2000 Server to act as the DNS & DHCP server for a
Windows NT Domain?
Click to expand...
Click to expand...
 
installing AD is not difficult, but there is some work involved if you are
migrating your NT domain to 2000/2003


Thanks! Is the upgrade to AD pretty straightforward? I am running into
more and more bottlenecks caused by NT :)

Phillip said:
Run the DHCP from the NT machine if this is an NT4 based domain. DHCP
with
2000 and 2003 needs to be authorized by the Domain Controller which NT4
DCs
cannot do. There are workarounds but it is just too much trouble. You
can
run DNS where ever you like, NT4 domains are Netbios-Based and don't
depend
on DNS so it isn't critical.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


Can I setup a Windows 2000 Server to act as the DNS & DHCP server for a
Windows NT Domain?
Click to expand...
Click to expand...
Click to expand...
 
Domain Controllers don't create "bottle necks". Physical cabling and
overall topology design create "bottle necks", changing to an Active
Directory based Domain that by nature has higher requirements and generates
greater "domain traffic" than the old NT domains is not going to cure a
supposed "bottle neck".

In a nutshell, to upgrade the Domain you simply upgrade over the top of the
NT4 PDC with either Server2000 or Server2003. But you need to study the
whole process yourself by reading the various migration documents that are
out there. This is not something we can give you all the details on in a
simple newsgroup message, there are just too many variables and too many
possible situations.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
 
Sorry - bad choice of words on my part ... the bottle neck I was
talking about was the need to install Exchange 2000 ... or use AD ...
which can not be done on an NT domain AFAIK.

The network itself is just fine :)

Phillip said:
Domain Controllers don't create "bottle necks". Physical cabling and
overall topology design create "bottle necks", changing to an Active
Directory based Domain that by nature has higher requirements and generates
greater "domain traffic" than the old NT domains is not going to cure a
supposed "bottle neck".

In a nutshell, to upgrade the Domain you simply upgrade over the top of the
NT4 PDC with either Server2000 or Server2003. But you need to study the
whole process yourself by reading the various migration documents that are
out there. This is not something we can give you all the details on in a
simple newsgroup message, there are just too many variables and too many
possible situations.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



It's a relatively small LAN - 25 PCs and about 20 users.
Click to expand...
Click to expand...
 
Sorry - bad choice of words on my part ... the bottle neck I was
talking about was the need to install Exchange 2000 ... or use AD ...
which can not be done on an NT domain AFAIK.

The network itself is just fine :)
Click to expand...

Ok, well you will need to have AD,..no way around that,..Exchange requires
it. MS has a lot of Migration Docs for doing this from NT4. It isn't very
hard but you do have to do it correctly.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
 
Back
Top