Steps for diagnosing timeouts, hangs, and waits
Timeouts, hangs, and waits occur when the LPD server does not respond to client requests for a data packet, an acknowledgment that a data packet was received, or a reply to a command. Similarly, the LPD server can time out a connection if the LPR client does not respond.
Before you begin
- Incorrect host name or IP address specified on the LPR command
- Malfunctioning remote server or remote host
- Problems with the network (for example, network congestion), bridge, gateway, or router in the routing path
- Problems with the device or channel attached to the host
- Corrupted TCP/IP address space
- Incorrectly built or defined translation tables
- Malfunctioning LPR client
Procedure
Perform one or more of the following steps to diagnose timeouts, hangs, and waits.
- Check to see whether the target LPD print server is running, has enough paper, and is not jammed.
- Check the LPR and LPD traces for possible error messages, or for the last activity performed by LPR or LPD (for example, waiting for a connection, port availability, or an acknowledgment). Be aware that when sending a print request to a remote printer through the LPD server, the LPR client can show a successful data transfer even though there might be a problem connecting to the remote printer.
- Check the IP address or host name used with the LPR command.
- Check the LPR, LPD, and packet traces. If the packet trace shows a problem during binding or connecting, then check the socket trace.
- Verify that the translation tables are built correctly. Test them using the hlq.STANDARD.TCPXLBIN table supplied with TCP/IP.
Results
Be aware that waits can occur because some LPD servers do not send acknowledgments until data is printed. In this situation, the LPR client does not show successful data transfer until it receives the acknowledgment.