Secure Design - SDLPD does not answer incomming jobs

SDLPD does not answer

Q. I can ping the NetWare server, however I can not send a print job to it. My Unix LPR/LPD daemon says "waiting for remote host"

A. Type "config" from the NetWare server console. Verify the IP address and netmask are correct.

From the UNIX host, verify that you can ping the NetWare server, and that ping on the NetWare server can reach the UNIX host.

Next, configure the log to show all (NOISE) messages in the log file with SDLPDCON.NLM. Load SDLPD.NLM after making the change.

Any connections to SDLPD will be logged, so you can see if the LPR/LPD daemon on the Unix host is actually contacting SDLPD or if there is some other problem.

Attempt to send your print job. You may need to stop and start the Unix queue to get the job to restart. Does the SDLPD log screen show any activity? If so, what? If not, then the LPR/LPD daemon is not contacting the NetWare server.

If the LPR/LPD daemon is not contacting the server, try this test: from the Unix command line, telnet to your NetWare host on port 515. (type "telnet netwarehost.domain.com 515" ) You should get a connect message, and then nothing. Telnet should wait for you to type something. If it does not, there is a problem. Press Enter, and the connection should terminate. The SDLPD log screen should log a connection attempt, and show the connection was closed because of an invalid command.

If the SDLPD log screen shows nothing (in noise mode) or telnet terminated or never connected, then there is a TCP/IP issue with your network, Unix host, or NetWare server. Most often, this is because there are two computers with the same IP address. When this happens, ping works because your packets go to the wrong computer, and the wrong computer answers them. LPD breaks because the wrong computer may not be running LPR/LPD.

support@sdesign.com