home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!att-out!walter!qualcom.qualcomm.com!qualcom!smiller
- From: smiller@qualcom.qualcomm.com (Scott Miller)
- Newsgroups: comp.protocols.tcp-ip
- Subject: BootP experience
- Message-ID: <smiller.725144237@qualcom>
- Date: 23 Dec 92 20:57:17 GMT
- Sender: news@qualcomm.com
- Organization: Qualcomm, Inc., San Diego, CA
- Lines: 27
- Nntp-Posting-Host: qualcom.qualcomm.com
-
- We have 1000+ PC and Macintoshs connected to our IP network and are
- starting to have problems managing these machines. Due to the fluid
- nature of our company, people and equipment are being moved continuously
- resulting in incorrectly configured machine being plugged into our net.
-
- One possible solution is to use BootP to assign IP addresses, subnet
- masks, default gateways, and domain name servers. With this information
- centralized, users can have their machines reconfigured with a phone call.
- Great stuff.
-
- I've downloaded and successfuly been using BootP 2.2 here with two
- servers (one on the other side of a cisco configured with BootP directed
- broadcasting), three Macintosh's running MacTCP and a PC running FTPPACK.
-
- It seems to work great, but I'd like some feedback from someone using
- this in the real world managing 1000+ machines. Some of my questions
- include: How many servers per x nodes/nets? Has anyone modified bootp
- to dynamically assign IP addresses to portable (palm-/lap-tops) machines?
- Have any security issues arisen from using BootP? How much of an impact
- does using BootP have on a network in terms of broadcasts/second? Is
- there anything I should be aware of before I start migrating the entire
- company to use BootP?
-
- Any input would be greatly appreciated.
-
- Scott Miller <smiller@qualcomm.com>
- Supervisor, Network Operations--Qualcomm, Inc.
-