Installing and Administering Internet Services

Chapter 5 241
Configuring TFTP and BOOTP Servers
Troubleshooting BOOTP and TFTP Servers
reboot the BOOTP client.
❏ Ensure that the hardware address you specified for the ha tag
matches the hardware address that /usr/lbin/bootpd said it could
not find. Correct the tag and reboot the BOOTP client.
❏ Ensure the hardware type tag ht has the correct value for the client.
For example, if you have specified ether but the client is reporting
ieee in its bootrequest, bootpd will reject the request. Correct the tag
and reboot the BOOTP client.
Symptom: The system log /var/adm/syslog/syslog.log contains a message that
looks like this:
requested file not found: filename
Cause: The client specified filename as the boot file in its bootrequest, but
bootpd could not find the file in the tftp directory.
Action: ❏ Make sure that you have configured tftpd with the entry in
/etc/passwd for the user tftp.
❏ Ensure that the requested file is present in the tftp directory, which
is usually /home/tftpdir or in the directory specified with the tftpd
command. If it is not, place the file in the directory and reboot the
BOOTP client. If the requested file exists in the directory, be sure it is
readable by the user tftp. (See “Common tftpd Problems” on page
243.)
Symptom: The system log /var/adm/syslog/syslog.log contains the following
message:
cannot route reply to client's_IP_address
Cause: The IP address you have specified for the client is one which the server’s
system cannot reach directly.
Action: ❏ Ensure you have specified the correct IP address for the client in
/etc/bootptab. Correct the entry and reboot the BOOTP client.
❏ If the server is to reply directly to the client, it must reside on the
same network or subnet as the client. If the client resides on another
network, ensure that intervening servers are configured to relay the
bootrequests.
❏ Ensure the IP address you have chosen for the client is a valid IP