Your not completly wrong. DHCP is needed to allocate IPs ti the local LAN. The point is that he doesn't need a DHCP server to simply share an internet connection. All you need to do is on each machine on the LAN assisgn ips , default gateway and DNS. The deafult gateway is the router. End of story.
If you need to assign hostnames to each machine then your hostname section in miami will need to be changed once only. Since the IP's don't change for the machine, the host name will always be assigned to the same IP and hence the same machine.
If you use MAC caching your defeating the purpose of DHCP on a static LAN any how because it is efectivly the same as assigning static IP's. MAC caching, or IP leasing, ensures that the same NIC/PC gets the same IP when it connects to the LAN for a defined amount of time.
The only time that laziness could ever justify using DHCP is when you just want plug a machine in to the network, and use the shared network. If you want to set up servers on your lan then you need to think a bit harder.
Casper is right. Turn off DHCP if you want to do any serious networking.
Casper wrote:
for best results turn off the DHCP client on the router/acces point and assign all your computers static addresses in thier network setup
I don't think that'll work (somebody correct me if I'm wrong). I think that the router needs to use DHCP to assign IPs so that it knows which computer to forward the internet traffic to. It isn't even possible to turn off DHCP on my router.
