Unable to Assign IP Address
If you ping the device and are not getting a response, the glean is not working. Check the following possible problems:
Verify the ARP table contains the correct hardware and IP address by running the ‘arp -a’ command.
If you are getting a response, but the OkiLAN 6200e LED is still blinking green, power down the print server and try the ping again. There might be a different device answering to the ping.
Verify the OkiLAN 6200e is on the same subnet as the computer running the ping.
The glean will not work if the OkiLAN 6200e has already defaulted to an IP address two minutes after power up. The LED will turn solid green and the device will print a configuration page. Power cycle the device and try the glean again.
RARP or BOOTP
If you are using a BOOTP or RARP server and the OkiLAN 6200e is not getting an IP address, check the following:
Verify the BOOTP/RARP configuration files are correctly set up (“/etc/ethers” and “/etc/hosts” for RARP and “/etc/bootptab” for BOOTP). Verify the files have the correct hardware address of the OkiLAN 6200e. If using RARP, check that the hostnames are the same between the “/etc/ethers” and “/etc/hosts” files.
If you are running UNIX, try the following methods with the BOOTP server (check the documentation for your particular UNIX flavor).
Verify the BOOTP server has reread the “/etc/bootptab” file when the new entry was added. If the BOOTP server was running when you added the new entries, the server might not have reread the new bootptab file. Try sending the SIGHUP signal to the running BOOTP server. For example, kill -HUP <process id of bootpd> tells it to reread “/etc/bootptab”. Most BOOTP servers support this option. Check your local BOOTP documentation. If this does not work, restart the BOOTP server (kill and restart the process).
Some BOOTP servers will write their internal bootptab tables to a file when they receive a SIGUSR1 signal. You can check this file to verify the hardware and IP address are correct. You can use the kill command to send signals. For example, kill -USR1 <process id of bootpd>. Check your documentation for more information.
Check the system’s syslog file. Some BOOTP servers will write error messages into the syslog file.
Example: Sep 6 14:38:43 bootpd: hardware address not found: 004068175042
This message appears when the BOOTP server received a request from a device not in its internal bootptab tables.