Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 686
  • Last Modified:

Is it best practice to have routers/Switches handle DHCP or should Server 2008 handle it?

Hello,

I just need to get a general feeling of what is "Best Practice"  I have just introduced 3 Server 2008 R2 DC's to an environment.  Currently DHCP is handled by the router.  They have around 90 users and I feel DHCP would be better managed on the server.

What is the general concensus on DHCP out there?
0
Clarick1
Asked:
Clarick1
1 Solution
 
wrightsonmCommented:
You will almost definitely have more control over dhcp using server 2008 than a standard off the shelf router.  If you have domain controllers then you need dns running on the server so that the DC is regsitered correctly, so you would have to reconfigure the router dhcp to use the dns on the server.  So you may aswell to dhcp with the dns on the same machine.

My vote is to have dhcp on the server
0
 
AmitIT ArchitectCommented:
For small env (2-50 user) router DCHP is good. But for large env, Windows DHCP will be better, as you can create multiple scopes and design according to your requirement.

0
 
Clarick1Author Commented:
The environment was small but now they have grown.  We just put in a new VMWare environment and the user base is much larger.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
AmitIT ArchitectCommented:
With my exp, Windows DHCP will be the better option for large env. It is easy to manage and troubleshoot. For more details please check below link.

http://www.windowsnetworking.com/articles_tutorials/How-to-Install-Configure-Windows-Server-2008-DHCP-Server.html
0
 
Craig BeckCommented:
I would use the Server, so DHCP and DNS management is easier, and so DHCP clients can register their hostnames successfully in DNS.
0
 
Clarick1Author Commented:
I basically agree with all of you.  on using the server.  I wanted to see if there was a consensus.  Thanks so much for input!
0
 
itconsultant7717Commented:
Definitely use the server because DNS and active directory work together, when users log into machines you do not want any information to go to a router first you want that information (username, computer name etc) to go straight to the DNS server that hosts active directory. I've seen log on performance suffer if you don't utilize DNS and DHCP on a server in a domain environment. Just have the server forward DNS info to the router and the router will forward to the ISP. Also in the DHCP server you can setup options, for example router IP, DNS server, time server which you can control from your own DHCP server but you usually can't do this from a router or switch. Again, all this information is better left on the server so it's in the loop as the information is sent to workstations.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now