Which is better ...DHCP from server or router 1

[mystifying]

I am just curious as to what is recommended. We have been having our vpn router serve as the DHCP server (with no problems), but I just wanted to find out if there were any advantages/ reasons to use our Windows 2003 Server for DHCP instead. What do you think?

 

[tylan]

I like to use a server. As long as your DHCP server is pushing out all the right stuff it shouldn't matter - - Such as, your domain name, wins, dns, and so forth.

The only reason I like a server is because sometimes SOHO stuff (IE Linksys) will only push out IP, Mask, and Gateway - - Which doesn't help name resolution.

The other nicety of a server is the ease of management. You can see active leases, time left, and change all that very easily.

Thats My Opinion. I don't think it really matters.

 

[ricpinto]

For SOHO router DHCP should be OK but not with Enteprise because they will have multiple DHCP/subnets and all the complications.

Advantage using the router DHCP: PC can still surf the net even the server is down.

 

[Claudek]

If you use Windows 2000/2003, the option to integrate your DHCP with your internal DNS is a nice feature. Means you get rid of WINS totally as every client which registers for a DHCP address has a DNS record created/updated for it.

You could always turn on the Router DHCP in case the server goes down, so not a bad way to go.



Claudius (What certifications??)

http://www.iteq.com.au

 

[Shekinah]

Claudek, your posts in this forum have been spot on. I suspect you are really more than just a technical user!

 

[mystifying]

Thanks for the replies ...I appreciate the help!

Stacy

 

[zaznet]

It is a matter of size. If you have between 5 and 200 workstations then you are talking abuot one site or a very small enterprise network if you have multiple sites (nearer to the 200 mark).

DHCP on the 2003 server means that each system is automatically registered in the 2003's DNS. It is a matter of integration and allowing immediate access to resources after an IP change that's a huge benefit.

Beyond the DNS integration is how DNS then works when you have more than just one server. When you have a dozen sites, each with their own DC (Domain Controller, or Windows 2003 server) runnnig DNS and DHCP you can easily access systems and resources even with dynamic changes to the IP address.

This used to be done with WINS, but is no longer needed and DNS is better suited to an Active Directory environment since it (DNS) already uses a child parent "tree" structure as introduced with AD (as opposed to the flat domain and member method from NT 4 and earlier).

HTH,

Nathan

Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/

 

[jfk8680]

Means you get rid of WINS totally as every client which registers for a DHCP address has a DNS record created/updated for it"

I'm not sure that you can discard WINS as easy as this. Just because all your machines are registered with your DNS server (by it's own or by DHCP) doesn't mean NETBIOS name resolution traffic will be gone. If you still use legacy applications or even Operating Systems which do not use DNS for name resolution, NETBIOS broadcasts will occur if you don't have a WINS server in place. If you want to get rid of NETBIOS name resolution and thus WINS, you'll have tot disable NETBIOS totally (which you can specify in Windows DHCP btw) but as I said chances are pretty high you'll still need NETBIOS for certain applications or operating systems...

getting back on topic: I prefer my Windows servers for DHCP for (mostly) two reasons: it supports more features (adding vendor options which I need for my thin clients) and you can make a daily backup of your DHCP database and configuration.



Jeffrey Kusters

MCSA, MCSE, CCNA

 

[zaznet]

True jfk8680,

Some of us are very glad to see the death of WINS, even if it bloats DNS and promotes reckless use of DHCP. I do NOT mean that DHCP is itself "reckless". I have seen DHCP deployments with very poor planning or done with no purpose in mind. Driving down the street with no intent to stay on your side of the road is also reckless


Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/