Solved: Seperate DHCP Server?

Beacon Bits · ‎09-03-2013

Hi Everyone!

Why we need DHCP server seperatley whereas if its already in the appliance? Is there any major impact does it has?

John Blakley · ‎09-03-2013

I'm not sure I completely understand the question, so I'm going to take a shot at it. If you have a DHCP pool configured on a router, you can do pretty much everything you can do as if it was configured on a Windows server. The advantages that you have on a Windows server are that it's simply easier to manage when you get to other advanced operations like reserving an address for a client. You can do that as well on a router, but when you have a bunch of clients that you want to do that for it's easier on a server.

There is really no impact to setting up a helper address on the router to forward those requests to a server, and there's no impact on the server acting as a dhcp server. I've never run a dhcp server on a router for a hundered clients. The most that I've run one for is about 30 users, and anything more than that we've moved over to servers.

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***

View solution in original post

elom.kutsienyo · ‎09-03-2013

Him it's always better to to put the DHCP on a windows Server so that you can take advantages of AD and all that directly on the server especially knowing that most of the time in companies, the IT guy is most likely to be a microsoft guy that a cisco or even a network guy. So it is better to put the DHCP server in a server so that the guys can manage it without needing to call a cisco guy anytime they guess something is wrong with DHCP.

View solution in original post

elom.kutsienyo · ‎09-03-2013

Hi,

your question is not very clear. could you be more specific?

Beacon Bits · ‎09-03-2013

Thanks for your interest.

I'm confused that why we configure a seperate DHCP server in our nework sometime whereas any router can provide this facility.

John Blakley · ‎09-03-2013

I'm not sure I completely understand the question, so I'm going to take a shot at it. If you have a DHCP pool configured on a router, you can do pretty much everything you can do as if it was configured on a Windows server. The advantages that you have on a Windows server are that it's simply easier to manage when you get to other advanced operations like reserving an address for a client. You can do that as well on a router, but when you have a bunch of clients that you want to do that for it's easier on a server.

There is really no impact to setting up a helper address on the router to forward those requests to a server, and there's no impact on the server acting as a dhcp server. I've never run a dhcp server on a router for a hundered clients. The most that I've run one for is about 30 users, and anything more than that we've moved over to servers.

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***

Beacon Bits · ‎09-03-2013

Thanks John!

It clears all the doubt that I had in my mind. I'm going through the similar design where dhcp service is needed for about 80 users and I was thinking why should I need a seperate server for dhcp only though I can achieve this through my router.

Thank you!

elom.kutsienyo · ‎09-03-2013

Him it's always better to to put the DHCP on a windows Server so that you can take advantages of AD and all that directly on the server especially knowing that most of the time in companies, the IT guy is most likely to be a microsoft guy that a cisco or even a network guy. So it is better to put the DHCP server in a server so that the guys can manage it without needing to call a cisco guy anytime they guess something is wrong with DHCP.

Beacon Bits · ‎09-03-2013

Thanks for your reply!

Much appreciated!!!

elom.kutsienyo · ‎09-03-2013

My pleasure.