Installing and Administering Internet Services

186 Chapter 5

Conﬁguring TFTP and BOOTP Servers

Troubleshooting BOOTP and TFTP Servers

To view the information that bootpd places in the bootreply, enable a

broadcast bootreply by adding the ba tap to the client’s /etc/bootptab

entry. Use the bootpquery command to emulate the client’s

bootrequest:

bootpquery client_link_address -s servername

bootpquery prints the reply it receives from the server, which allows

you to examine the information supplied to the client. Remove the ba tag

from the conﬁguration entry once you’ve veriﬁed the correctness of the

bootreply.

Symptom: The server’s system log ﬁle /var/adm/syslog/syslog.log does not

contain any log messages from /usr/lbin/bootpd showing that the

server started. A ps -ef listing does not show a running

/usr/lbin/bootpd.

Cause: The server may not be started or it may not be receiving the client’s

bootrequest.

Action: ❏ Make sure that /etc/inetd.conf is conﬁgured correctly as

documented earlier in this chapter.

❏ Ensure that you have reconﬁgured inetd with the command inetd

-c.

❏ Check inetd’s logging in /var/adm/syslog/syslog.log to ensure

inetd is conﬁgured to start bootpd.

❏ Verify that the server will start by using the bootpquery command.

❏ Check whether the client is on the same network as the BOOTP

server. If the client is not on the same network, ensure that

intervening BOOTP servers are conﬁgured to relay bootrequest

broadcasts.

Symptom: The system log /var/adm/syslog/syslog.log contains one of the

following messages:

hardware address not found: hardware_address

IP address not found: ip_address

Cause: bootpd does not have an entry in /etc/bootptab for this client’s

hardware address or IP address.