Networks

Ask something
Discussion Locked

Windows 2000 DNS/DHCP

0 helpful
7 replies

by william.wang

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have Windows NT Domain network with NT DNS/DHCP server for name resolution. Now we need Windows 2000 DNS/DHCP dynamic to support our application server.

Question 1: If I add Windows 2000 server to NT Domain will have a lot problems?

Question 2: What is the difference between having the DNS/DHCP Server as a stand alone ?vs.- being joined to a member server?

7 replies

by mike jones

Question 1. You should be able to connect a Windows 2000 server to a NT4.0 domain without problem, just don't enable Active Directory. This will then act as a standalone server.

Question 2. None, several companies use Unix for DNS and Microsoft for DHCP. Doesn't matter what the server is.

by demongp

Right, lets start from the beginning:

Q1:You can add the Win2k Server to your NT Domain as a MEMBER SERVER, with no problems. You cannot, however, add it to the domain as a BDC. you can install it as the PDC, which will mean your domain will become a AD domain running in mixed mode.

Q2: As far as i know, in your current enviroment, you should not have any problems running DNS\DHCP on Win2k as a standalone server. you will lose some functionality though, but this functionality is onlyavailable if your domain is running AD, though. However, I would really recommend adding it as a member server to the domain - unless there is a specific reason you want to keep it Standalone?

by tellmewhy

Q1: Add windows 2000 in NT4.0 domain as a member server and do not run "dcpromo" file in "run" or just do not install active directory and it would run normally. add it to NT4.0 domain. thats all.

Q2: DNS/DHCP has no prob running alone or joined to a member server.

This discussion is closed to new replies.