home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!nwnexus!ole!rwing!eskimo!ntprlr
- From: ntprlr@eskimo.com (NightProwler)
- Newsgroups: comp.sys.novell
- Subject: Re: BOOTP through server
- Message-ID: <1993Jan25.054214.20338@eskimo.com>
- Date: 25 Jan 93 05:42:14 GMT
- References: <1993Jan20.234034.20904@ccu1.aukuni.ac.nz>
- Organization: Ghost in the Shell
- Lines: 24
- X-Newsreader: TIN [version 1.1 PL6]
-
- A R Anderson (alastair@ccu1.aukuni.ac.nz) wrote:
- : We have PCs that use telnet to communicate with central systems, with a
- : Novell server (3.11) functioning as an IP router. In most respects, TCP/IP
- : works correctly. However, one of the central systems is a BOOTP server and
- : it does not receive BOOTP requests that are generated by the PCs. Does
- : anyone have a way of making this part of TCP/IP work?
-
- So what you're saying is that you have a 3.11 server acting as an IP router
- between two IP sub-nets....and the diskless clients are on one side of the
- router and the bootp server is on the other side....is that it?
-
- Now, I've never actually read how bootp works, nor seen it in action, but my
- understanding is that the card wakes up and sends out a broadcast message to
- any bootp server on the same subnet to see if someone can send it a boot
- image...at least that's my understanding of it.
-
- I think I'm wrong on this...because that would mean that you'd need a bootp
- server on each subnet to boot the clients on it.
-
- I'm curious as to how bootp works...anyone know the RFC that defines it?
- --
- # NightProwler ----------- I live in the night | "When the going gets weird, #
- # NtPrlr@eskimo.com | The Weird turn Pro." #
- # [Standard Disclaimer Applies] | --Dr. Hunter S. Thompson #
-