MultiView 2000® & MultiView 2000 Server Edition Support

LPR/LPD Trouble Shooting Guide For UNIX SVR 4.x

LPD / lpsystem command missing

Verify that the package which contains “LPD” and “lpsystem” is installed by using the command:   pkginfo netcmds

The command should return the following:   system netcmds Commands Networking Extension

If not, it will be necessary to install the package from the release media for the operating system with the following command:   pkgadd -d /dev/rmt0 netcmds

Note:  The device for the -d option may vary between systems.

Error number 6 message from Remote Printer Driver under Windows

If the message “JSB-LPR Error number 6 Cannot open LPR Connection&rdqo; appears when trying to print using the Remote Printer Driver under Windows, do the following:

1. Check that the port monitor for “tcp” on the host is running by typing sacadm -l

Check for an entry with a tag of “tcp” with a status of ENABLED or STARTING. If the port monitors status is FAILED or NOTRUNNING then try to restart it by typing: sacadm -s -p tcp

2. Check the port monitor log file for error messages by typing tail /var/saf/tcp/log

If output similar to the following can be seen, then the lpd service “Servers Private Address” is incorrect:

07/17/95 11:53:58; 22082; Requested address \x00020203C1816D260000000000000000
07/17/95 11:53:58; 22082; Actual address \x00020203000000000000000000000000
07/17/95 11:53:58; 22082; Service lpd unavailable

Find the correct value with the command lpsystem -A and make a note of the address printed. Then use the sysadm program to check the settings for the lpd service. (See the JSB guide to setting up LPR/LPD on UNIX SVR 4.2 for detailed instructions of how to configure lpd using sysadm.)

Error number 7 message from Remote Printer Driver under Windows

If the message “JSB-LPR Error number 7 Unable to make LPR connection” appears when trying to print using the Remote Printer Driver under Windows, do the following:

1. Check the network printer spooler log file on the UNIX host for error messages by using the following command: tail /var/lp/logs/lpNet

If the printer is not accepting requests the following message will be seen in the file:

03/01/95 14:16 c 23657 richppc richppc requests recvjob rptest
03/01/95 14:16 c 23657 richppc request for disabled printer: rptest
03/01/95 14:16 c 23657 richppc lpd exiting, status=1

To enable the printer type, use this command: accept <printer name>

2. Check the correct printer queue name is specified correctly in the MultiView DeskTop Remote Print Manager program.

To check if wrong printer queue name is specified in the Remote Print Manager program use the following command to check the network printer spooler log file on the UNIX host: tail /var/lp/logs/lpNet

If the printer queue name is incorrect the following message will be seen in the file:

03/01/95 14:18 c 23670 richppc richppc requests recvjob rptest2
03/01/95 14:18 c 23670 richppc unknown printer rptest2:No such file or directory
03/01/95 14:18 c 23670 richppc lpd exiting, status=1

To get a list of available UNIX print queues type: lpstat -p

3. Check to see if the port service lpd is enabled by typing the following command: tail /var/saf/tcp/log

If the lpd service is disabled the following message will be seen in the file:

03/01/95 16:45:30; 6484; New call on addr <lpd> fd 8, seq # 48364288
03/01/95 16:45:30; 6484; Caller : 000201B8C1816D680000000000000000
03/01/95 16:45:30; 6484; Request for service on fd 8 denied: disabled

Use the sysadm program to enable the lpd service.

4. Check to see if tcp port monitor is enabled by typing the following command: tail /var/saf/tcp/log

If the tcp port monitor is disabled the following message will be seen in the file:

03/01/95 16:52:58; 6484; New call on addr <lpd> fd 8, seq # 41489920
03/01/95 16:52:58; 6484; Caller 000203ABC1816D680000000000000000
03/01/95 16:52:58; 6484; Incoming call while disabled: fd 8, seq 41489920

Use the sysadm program to enable the tcp port monitor.

5. Check that the PC name is valid on the host by “pinging” the PC, e.g., ping richppc

The following response will be seen if the PC name is valid:  richppc.jsb.co.uk is alive

If the PC name is not registered correctly on the host then the following response will be seen:   ping: unknown host richppc

Check the /etc/hosts file to make sure there is an entry for the PC.

6. Check that the PC is registered with the network print system by typing:
   lpsystem -l <pc-name>

Output similar to the following will be seen;

	System:	richppc
	Type:	bsd
	Connection timeout:	never
	Retry failed connections:	after 10 minutes
	Comment:	none

If the PC is not registered with the network print system the following message appears: UX:lpsystem: WARNING: "richppc" not found.

Use the lpsystem command to add the correct PC name.

NB: If a Domain Name Server (DNS) is being used make sure that the PC name registered includes the PC's domain (e.g., jsb.co.uk) otherwise requests will be rejected, unless the PC name is listed in the hosts /etc/hosts file.

Check the output of the lpsystem command to make sure that the PC is registered as “bsd”. The line in the listing should appear as: Type:  bsd

To change to type "bsd", enter the following:  lpsystem -t bsd <pc-name>

Print jobs sent without error but nothing appears on the UNIX printer

Print jobs appear to have been successfully sent without errors from a Windows application using the Remote Printer Driver but no print out appears on the printer connected to UNIX host./p>

The printer spooler will normally mail the user if a problem is encountered while tying to print a job on the host. However the network printer spooler daemon lpNet, tries to send the mail response via SMTP over the network to the originating PC. Unless the PC has some SMTP mail software installed on it the mail will remain in a queue on the host.

1. To see if mail is waiting for the PC which sent the print, change to the SMTP mail queue directory with the command cd /var/spool/smtpq and, then, find the id of the mail request with the command tail LOG.

If a mail message is waiting for the PC and cannot be sent, the following message will be seen in the file:

03/01 17:34:40 smtpqer queued message for host <richppc> user <richardp >
03/01 17:34:40 smtpsched dosmtp richppc/C.073807927900
03/01 17:34:40 smtpsched /usr/lib/mail/surrcmd//smtp -N -d .jsb.co.uk -H drs6000.jsb.co.uk root richppc richardp
03/01 17:34:41 smtpsched fail 69

To examine the message which is in the queue, “cat” the data file for the mail message. The mail message ID will be in the LOG file. In the above example, the mail message ID is “073807927900”.

To examine the data file for the message type: cat <pc name>/D.<mail request id>

2. Mail message reports the following:

From root Wed Mar 1 17:43 GMT 1995 remote from drs6000
Subject: printer job
Content-Length: 247
Content-Type: text
Your printer job (rptest.001) could not be printed.
Reason for failure:
UX:lpd: ERROR: You are not allowed to use the destination "".
UX:lpd: TO FIX: Use the lpstat -p command to list all known printers; you can use those marked "available".

Permission needs to be granted for users from other systems to use the printer. Enter the following command to fix this problem: lpadmin -p <printer name> -u allow:all!all

"No filter to convert" message under DRS/NX

If the following mail message is seen when using ICL DRS/NX:

From root Wed Mar 1 17:49 GMT 1995 remote from drs6000
Subject: printer job
Content-Length: 286
Content-Type: text

Your printer job (rptest.001) could not be printed.

Reason for failure:

UX:lpd: ERROR: There is no filter to convert the file content.
UX:lpd: TO FIX: Use the lpstat -p -l command to find a printer that can handle
the file type directly, or consult with your system administrator.

This problem is caused by a bug in DRS/NX where the lpsched process misinterprets the lpd protocol switches "l" and "f". The print spooler scheduler is looking for a filter it does not possess. A filter can be created to circumvent the problem which essentially does nothing to data to be printed. The work around for this problem is as follows.

1. Login as root.

2. Create the file “/tmp/lpdfil&rdqyo; which contains the following lines:

Input types: simple
Output types: simple
Printer types: any
Printers: any
Filter type: slow
Command: /usr/bin/cat
Options: MODES catv_filter = -s

3. Create the filter by typing: lpfilter -f lpdl -F /tmp/lpdfil
4. Verify the filter by typing: lpfilter -l -f lpdl
5. Send the print again.

IMPORTANT NOTE: You must have a printer type set for the queue or the lpfilter work round will not succeed.

Prints are not sent from UNIX to PC LPD

When print jobs are sent from the UNIX host and no output appears on the printer connected to the PC running MultiView DeskTop check the following:

1. Check the network printer log file on the UNIX host by typing: tail /var/lp/logs/lpNet

If the following messages are seen, then the lpd server is not running on the PC.

07/19/95 10:12 p 20991 <none> Started child for richppc.jsb.co.uk, pid = 3267 07/19/95 10:12 c 3267 richppc.jsb.co.uk lpd starting (active)
07/19/95 10:13 c 3267 richppc.jsb.co.uk no connection

Start the server and try again.

2. If the print queue name is wrong on the UNIX host the following messages will be seen in the lpNet file:

07/19/95 10:33 c 5285 richppc.jsb.co.uk lpd starting (active)
07/19/95 10:33 p 20991 <none> Started child for richppc.jsb.co.uk, pid = 5285
07/19/95 10:33 c 5285 richppc.jsb.co.uk lpd connected to richppc.jsb.co.uk
07/19/95 10:33 c 5285 richppc.jsb.co.uk NAKed by remote lpd (1)
07/19/95 10:33 c 5285 richppc.jsb.co.uk lpd disconnecting from richppc.jsb.co.uk

Make sure that the print queue specified when setting up the remote printer matches the print queue set-up under the MultiView DeskTop LPD Server.

3. If the PC name cannot be resolved on the host the following messages will be seen in the lpNet file:

07/19/95 10:55 p 20991 <none> Started child for richppc.jsb.co.uk, pid = 11698
07/19/95 10:56 c 11698 richppc.jsb.co.uk no connection

The wrong printer PC name is specified on the UNIX host. Check the PC name specified is correct using the lpsystem -l command and check the “/etc/hosts&rdqo; file to make sure that the name and ip address of the PC running MultiView DeskTop is correct. Try "pinging" the PC name from the UNIX host to make sure that the name is being resolved.

4. If no error messages are seen in the lpNet file, change the retry timeout for the network printer using the lpsystem command.

Example:

To change the retry timeout to 1 minute enter lpsystem -R 1 <pc-name> where <pc-name> is the name of the PC where MultiView DeskTop is installed.

Check the lpNet file again to look for error messages.