Problems revision 1.2
1 1.1 gwr 2 1.1 gwr Common problems and ways to work around them: 3 1.1 gwr 4 1.1 gwr Bootpd complains that it "can not get IP addr for HOSTNAME" 5 1.1 gwr 6 1.1 gwr If the entry is a "dummy" (not a real host) used only for 7 1.1 gwr reference by other entries, put '.' in front of the name. 8 1.1 gwr 9 1.1 gwr If the entry is for a real client and the IP address for 10 1.1 gwr the client can not be found using gethostbyname(), specify 11 1.1 gwr the IP address for the client using numeric form. 12 1.1 gwr 13 1.1 gwr Bootpd takes a long time to finish parsing the bootptab file: 14 1.1 gwr 15 1.1 gwr Excessive startup time is usually caused by waiting for 16 1.1 gwr timeouts on failed DNS lookup operations. If this is the 17 1.1 gwr problem, find the client names for which DNS lookup fails 18 1.1 gwr and change the bootptab to specify the IP addresses for 19 1.1 gwr those clients using numeric form. 20 1.1 gwr 21 1.1 gwr When bootptab entries do not specify an ip address, bootpd 22 1.1 gwr attempts to lookup the tagname as a host name to find the 23 1.1 gwr IP address. To suppress this default action, either make 24 1.1 gwr the entry a "dummy" or specify its IP numeric address. 25 1.1 gwr 26 1.1 gwr If your DNS lookups work but are just slow, consider either 27 1.1 gwr running bootpd on the same machine as the DNS server or 28 1.1 gwr running a caching DNS server on the host running bootpd. 29 1.1 gwr 30 1.1 gwr My huge bootptab file causes startup time to be so long that clients 31 1.1 gwr give up waiting for a reply. 32 1.1 gwr 33 1.1 gwr Truly huge bootptab files make "inetd" mode impractical. 34 1.1 gwr Start bootpd in "standalone" mode when the server boots. 35 1.1 gwr 36 1.1 gwr Another possibility is to run one bootpd on each network 37 1.1 gwr segment so each one can have a smaller bootptab. Only one 38 1.1 gwr instance of bootpd may run on one server, so you would need 39 1.1 gwr to use a different server for each network segment. 40 1.1 gwr 41 1.1 gwr My bootp clients are given responses with a boot file name that is 42 1.1 gwr not a fully specified path. 43 1.1 gwr 44 1.1 gwr Make sure the TFTP directory or home directory tags are set: 45 1.1 gwr :td=/tftpboot: (or) 46 1.1 gwr :hd=/usr/boot: (for example) 47 1.1 gwr 48 1.2 gwr My HP Laserjet 4 gets an error during boot: "80 service (xxxx)" 49 1.2 gwr Here is an explanation of the problem from a fellow at HP: 50 1.2 gwr 51 1.2 gwr Date: Mon, 16 Oct 95 10:16:29 MDT 52 1.2 gwr From: James Clough <clough (a] hpbs3651.boi.hp.com> 53 1.2 gwr Subject: Re: problems bootp-2.4.3 and JetDirect 54 1.2 gwr To: bootp (a] andrew.cmu.edu 55 1.2 gwr 56 1.2 gwr > I installed bootp-2.4.3 with the DHCP-patches. 57 1.2 gwr > All went oke, except the JetDirect cards, build in in 58 1.2 gwr > several HP Laserjet 4's. They stopped while initialising 59 1.2 gwr > with error message '80 service (01E0)' or 60 1.2 gwr > '... (0009)'. The DUTH HP service support did not know 61 1.2 gwr > what the error-message was. 62 1.2 gwr 63 1.2 gwr This problem has surfaced here more than once--each time with a 64 1.2 gwr different hypothesized cause and proposed fix. 65 1.2 gwr 66 1.2 gwr The real cause of this problem is the byte alignment in the vendor 67 1.2 gwr extensions portion of the bootp packet. Here are a few workarounds 68 1.2 gwr that I've either used myself or heard tell of others using with 69 1.2 gwr success: 70 1.2 gwr 71 1.2 gwr 1. Change the name of the printer. If the name in your 72 1.2 gwr bootptab entry has an even number of characters, 73 1.2 gwr change it to a name with an odd number of 74 1.2 gwr characters. If it's odd, make it even. 75 1.2 gwr 76 1.2 gwr 2. Remove the logserver (lg) capability from the 77 1.2 gwr bootptab entries for the affected printers. 78 1.2 gwr 79 1.2 gwr 3. Use the vendor sort patches posted here in June by 80 1.2 gwr Ron Stanonik. They make bootpd sort the vendor 81 1.2 gwr extensions into RFC numeric order. It just 82 1.2 gwr so happens that this causes them to be aligned 83 1.2 gwr correctly. 84 1.2 gwr 85 1.2 gwr Really, anything that changes the byte alignment in the vendor 86 1.2 gwr tags section of the packet can work, including removing null 87 1.2 gwr terminators from string capabilities. 88 1.2 gwr 89 1.2 gwr James Clough 90 1.2 gwr -- 91 1.2 gwr clough (a] boi.hp.com 92 1.2 gwr 93 1.2 gwr (Perhaps we need a "pad for alignment" option in bootpd. -gwr) 94
Indexes created Sun Sep 21 20:09:37 GMT 2025