46 | The TFTP server IP address specified for the print server (through |
INVALID SERVER | BOOTP) is an invalid IP address for specifying a single node. Check |
ADDRESS | your Bootptab file for proper entries. |
47 | One of the SNMP trap (Trap PDU) destination IP addresses specified |
INVALID TRAP | for the print server (through TFTP) is an invalid IP address for |
DEST ADDRESS | specifying a single node. Check your TFTP configuration file. |
48 | The TFTP configuration file contained an incomplete last line that did |
CF ERR- FILE | not end in a new line character. |
INCOMPLETE |
|
49 | A line being processed in the TFTP configuration file was longer than |
CF ERR- LINE | the print server could accept. |
TOO LONG |
|
4A | A TFTP configuration file line contained an unknown keyword. |
CF ERR- |
|
UNKNOWN |
|
KEYWORD |
|
4B | A line in the TFTP configuration file was missing a required parameter. |
CF ERR- |
|
MISSING |
|
PARAMETER |
|
4C | A line in the TFTP configuration file contained an invalid value for one |
CF ERR- | of the parameters on that line. |
INVALID |
|
PARAMETER |
|
4D | The TFTP configuration file specified too many access list entries using |
CF ERR- ACCESS | the “allow:” keyword. |
LIST EXCEEDED |
|
4E | The TFTP configuration file specified too many trap destination list |
CF ERR - TRAP | entries using the |
LIST EXCEEDED |
|
4F | The TFTP transfer of the configuration file from the host to the print |
TFTP REMOTE | server failed with the remote host sending a TFTP ERROR packet to the |
ERROR | print server. |
50 | The TFTP transfer of the configuration file from the host to the print |
TFTP LOCAL | server failed with the local print server encountering some form of |
ERROR | inactivity timeout or excessive retransmissions situation. |
51 | The overall retrying of the TFTP transfer of the configuration file from |
TFTP RETRIES | the host to the print server has exceeded a retry limit. |
EXCEEDED |
|
52 | An error was detected in the BOOTP or DHCP reply that the print |
BAD BOOTP/DHCP | server received. The reply either had insufficient data in the UDP |
REPLY | datagram to contain the minimum BOOTP/DHCP header of 236 bytes, |
| had an operation field that was not BOOTPREPLY(0X02), had a header |
| field that did not match the print servers hardware address, or had a |
| UDP source port that was not the BOOTP/DHCP server port (67/udp). |
