when to use DHCP?

yoda · 28 Sep 2006 at 14:24

the IT admin of a small company network is using DHCP for clients and servers throught the site....
as far as I'm concerned this is wrong as their is only 200 PC's at the most and their all STATIC...
It's only a single site with very few laptops...

I'm after a recognised guide, preferably cisco or microsoft that states when to use DHCP and when not....
Aparently he was told at college to allways use DHCP... - Thats his current argument againsed me.... he left college about 8 years ago...

Can someone please help me....

Thanks

yoda · 28 Sep 2006 at 16:34

All the clients are allways connected to the network.... that have static assignments in the DHCP server...

I allways thaught that DNS and master browser functions work better with static IP addressing and it produces less network traffic.

yoda · 29 Sep 2006 at 13:13

but, why would you ever need to change gateways or DNS servers if you set it up right in the first place????

With the exception of large companies with multiple sites....
NET: 192.168.1.X

1: Unix / Linux main server
2: Exchange
3: Proxy
4: Gateway/firewall
5-10: DNS1-5 / ADS1-5
11-30: other servers
31-50: print servers
51-251: Client PC's
Use an excel spread sheet with IP number and what it's assigned to = no conflicts...
It works, I've implemented it and in three years I never needed to change it...

yoda · 29 Sep 2006 at 13:27

meh, for how often it changed, one change per week... at the most....