On 5/16/07, john harvey <[EMAIL PROTECTED]> wrote: > If you have many machines, static ip is not a good solution. I'd set the > expiration for a couple of months (maybe even 6) and rescavenge the dhcp > data.
You need to quantify "many." I've had people tell me they had HUGE databases because it took three (three!) floppies to back them up. Is 40 many? 300? 12,000? Some shops I work with have smart DCHP servers (I think they're using dnsmasq[1]) that hand out the same IP to the same Mac address each time, and the admins know who that is. That range is separate from the truly static IP addresses for fixed resources like servers and print queues. Handy for tracking down bandwidth abuse or other problems, and any admin can centrally control it, so they don't have to hike to a user's workstation just to set their IP address. They have a smaller range of dynamic IPs for guests, on a different subnet. Laptop/mobile users can access the core business network via VPN, but the other dynamic addresses just get internet access. So, it can work as a security mechanism, too. Pretty cool stuff. When it all works right, it's impressive to watch. [1] http://www.thekelleys.org.uk/dnsmasq/doc.html -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
