2003 Server Domain Controller......Do I need DHCP??

[trudawg]

I did a search but wasn't able to come up with a definitve answer......so if I may I'd like to know if I need the DHCP role installed on our 2003 server machine.
This a small network, and the 03 server will be used only as a domain controller, that will replace our existing Windows NT domain controller and file server, leaving the NT machine simply as a file server and to be used for backups.
Okay we have a broadband DSL modem connected to our cisco switch along with about 18 machines, along with the NT D.C and F.S, and more recently the 2003 server machine as I'm implementing and testing the D.C. role. After I finally got the test domain setup and connected to it I notiched I was getting a 192.xxx.xxx.xxx IP address as opposed to a 10.xxx.xxx.xxx range which is what I set up in DHCP scope. Therefore leading me to believe that the broadband modem is issuing the IP address. So is it the case that I don't really need the DHCP role on the 2003 server machine, if I really only need it to function as a Domain Controller??

 

[LWComputingMVP]

You don't NEED the 2003 system to be the DHCP server, but it's generally considered a good idea. TECHNICALLY, you don't need to use DHCP at all -- if you use static addresses everywhere.

You should understand that DNS (not DHCP) plays a CRUCIAL role in an Active Directory domain. As such, your DNS servers that DHCP tells your clients about should ONLY be Windows Servers (no secondary that's the ISP and even the server's TCP/IP Properties MUST point to itself as the DNS server).

Windows DHCP is generally easy to configure and manage for this purpose. If your existing DHCP server can be configured to hand out your DC as THE DNS server, then your fine to continue using it (still, I'd switch to Windows).

If you're not familiar with how vital DNS is to an Active Directory domain, I suggest reviewing some links I have at:

http://www.lwcomputing.com/tips/static/dns.asp

-Lee

Those who ask why, learn

http://www.lwcomputing.com

 

[trudawg]

Thanks MVP for the info!


On another note, as I am still testing. I'm trying to get access to the F-Drive on the Original DC, by mapping the drives, it sees the other computers and more importantly the original DC and file server, but I cannot access anything on the machine
In order to do so will I have to remove the Domain Controller role, or deactivate the DC in order to map that drive?

 

[trudawg]

BTW....I tried going to "RUN" and type in "\\{IP address of the older NTserver", and it would prompt me for UN & PW, but evrytime I try and type one in it comes back and changes itself to the UN and domain for the machine I currently have logged into the new 2003 DC

 

[trudawg]

through further research I gathered that I need to setup a trust relationship between the 2003 DC, and the NT PDC. But now I'm stuck with that, because when I try and add the new domain to trusted domain in the user manager it is unable to find the domain.

Any suggestions would be greatly appreciated. I know there is a simple fix, just can't see the forest because of the trees....lol

 

[trudawg]

Just wanted to say I got the new 2003 domain controller able to talk to and see the NT DC and fileserver. Apparently there was an issue with the netbios names not being associated with the ip address. Had to write an Lmhost file to both machines
before being able to create a trust between the two

found info here

http://support.microsoft.com/kb/325874