Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 312 — #338

Checking the TCP/IP Network The TCP/IP network and the name reso-

lution must be functional.

Checking a Remote lpd Use the following command to test if a TCP con-

nection can be established to lpd (port 515) on hhosti:

netcat -z <host> 515 && echo ok || echo failed

If the connection to lpd cannot be established, lpd may not be active

or there may be basic network problems.

As the user root, use the following command to query a (possibly

very long) status report for hqueuei on remote hhosti, provided the re-

spective lpd is active and the host accepts queries:

echo -e "\004<queue>" \

| netcat -w 2 -p 722 <host> 515

If the lpd does not respond, it may not be active or there may be ba-

sic network problems. If lpd responds, the response should show

why printing is not possible on the queue on host. If you receive a

response like that in Example 13.2, the problem is caused by the re-

mote lpd.

Example 13.2: Error Message from the lpd

lpd: your host does not have line printer access

lpd: queue does not exist

printer: spooling disabled

printer: printing disabled

Checking a Remote cupsd By default, the CUPS network server should

broadcast its queue every thirty seconds on UDP port 631. Accord-

ingly, the following command can be used to test whether there is a

CUPS network server in the network.

netcat -u -l -p 631 & PID=$! ; sleep 40 ; kill $PID

If a broadcasting CUPS network server exists, the following output

should be returned after forty seconds:

Example 13.3: Broadcast from the CUPS Network Server

ipp://<host>.<domain>:631/printers/<queue>

312 13.7. Printer Hardware