Problem
SCO provides a LAN Manager Client module as part of the SCO OpenServer 5.0.x product release. How do I use the printing option of this module?
Solution
The SCO OpenServer 5.0.x LAN Manager Client (LMC) module gives the ability to mount a LAN Manager, or LAN Manager-like, or NT filesystem, on to the native SCO UNIX filesystem and treat it as if it were local. The print option of this module allows the user to print to a remote LAN Manager or Advanced File and Print Server (AFPS) printer share. The full LAN Manager or AFPS products are not required to be installed on the local server to obtain this functionality.
For SCO OpenServer 5.0.0
------------------------
NOTE: The SCO Networking Supplement Release 1.0 for SCO OpenServer
Release Version 5.0.x (NET100) contains a later version of the LMC
module. This version should be used rather than the older LMC module
present on the SCO OpenServer 5.0.0 CD-ROM media. Loading and
applying the NET100 supplement will update this module. However, a
previous version of LMC is required to be present on the system
before the NET100 supplement will update it. As it is not loaded by
default, it must be manually loaded from the original OpenServer 5.0
CD-ROM media. It is not possible to do a partial load and apply of
the LMC component of the NET100 module once the full NET100 has been
installed without the initial LMC module.It can be difficult to gauge which version of LMC is installed on the system at a later stage. It can be verified, if required, using the SCOadmin Software Manager utility. The NET100 LMC version shows as:
.. View Loaded Patches=> Networking Supplement Release 1.0 for SCO OpenServer (ver rs oss500.2.0.a)
(.. expanded ) => LAN Manager Client Version 2.0.0: Networking Supplement Release 1.0
This patch must also be "applied" to the system to be functional.
LMC printing is described in the SCO OpenServer "Guide to Gateways for LAN Servers". This method should be disregarded as it has been superseded by that described in the NET100 documentation in the section entitled "Adding a remote printer to a LAN Manager client". The printer option modifier for LMCFS filesystems described in the mount(ADM) manual page is no longer valid. The later documentation is unclear, in certain aspects. This article addresses those aspects.
NOTE: The LMC module contained within the NET100 supplement is present as an integral part of the SCO OpenServer 5.0.x operating system.
For OpenServer 5.0.x:
--------------------
However, it is not loaded by default. To load it:Insert the SCO OpenServer 5.0.x CD-ROM media.
From the SCOadmin Software Manager, select:- Install New- Software- Highlight:"SCO OpenServer Enterprise System (5.0.x)"- Select "Partial" install and press <Enter> to display its sub-components.
- Highlight:"SCO OpenServer Enterprise System Connectivity (ver
5.0.x)"and again display its sub-components.- Select and install:"LAN Manager Client (ver 2.0.x)"LMC printing requires a remote server to share out its printer(s) to network clients.
However, this functionality can be installed at "install" time, by
default it is turned off. During the Initial System Load (ISL) select
the LAN Manager Client in the "Connectivity" and "Documentation"
sections of Software selection.Configuring LMC Printing:
------------------------
LMC printing is set up in the following example.Client:
------Log in as the "root" user to the SCO OpenServer 5.0.x client.
#cd /usr/spool/lpCreate a file named "remote". It should contain a line of the format:
printer:<TAB>/usr/spool/lp/bin/rlmclp -D remote -S srv [ -P pass ]
where:"printer" is the name by which the SCO client knows the remote printer share,
"-D remote" specifies the name of the printer share on the remote LAN Manager, AFPS or Windows NT share.
NOTE: The share names are case sensitive."-S srv" specifies the name of the remote server,
"-P pass" specifies the plain-text password for access to the printer share. This option is only required for share level servers that require a password to be supplied by the client to gain access to its printer share.
For example:zag: /usr/spool/lp/bin/rlmclp -D lmcp1 -S scotopwhere:zag - is the local client printer name
lmcp1 - is the remote server print sharename
scotop - is the remote server nameChange the ownership and mode of the file:
#chown lp:lp /usr/spool/lp/remote
#chmod 444 /usr/spool/lp/remote
# ls -al remote
-r--r--r-- 1 lp lp 49 Oct 10 14:25 remoteDefine this printer to the local clients print service:
#/usr/lib/lpadmin -p zag -v /dev/null -m network
#accept zag
destination "zag" now accepting requests
#enable zag
printer "zag" now enabledPrinter Server:
--------------
Now configure a printer share on the remote AFPS server and
test it:Find a printer you want to use, for this example an HP Network connection printer called "supp_lw2" was used.
# lpstat -a
...
...
supp_lw2 accepting requests since 01:43:31
PM Wed 05 Jun 1
...# net share LMCP1=supp_lw2 /printThe queue does not exist. Do you want to
create it? (Y/N) [Y]: yPrint queue LMCP1 was created. LMCP1 was shared successfully.
Check that it exists:# net shareSharename Resource Remark
--------------------------------------------
...
...
LMCP1 supp_lw2 Spooled# net printPrinter queues at SCOTOPName Job # Size Status
--------------------------------------------
LMCP1 Queue 0 jobs *Queue Active*# lpstat -a
...
lmcp1 accepting requests since 03:47:47 PM
Thu 10 Oct 1Test that you can print to it. In this example, the test utility "lmshell" is used as a LAN Manager client.
#lmshell
C:\>
C:\>net logon administrator
Password ?
The server \\SCOTOP successfully logged you on as
ADMINISTRATOR.
C:\> net use lpt1: \\scotop\lmcp1
LPT1: linked to \\SCOTOP\LMCP1
C:\>copy /test1.txt lpt1:Back on the Client:
------------------
Ensure that the LMC module is running on the SCO OpenServer
client system. This is started on system reboot once LMC
Runtime has been configured to run over the systems network
card using the netconfig(ADM) interface. The command "lmc
start" may also be used.# ps -ef |grep lmc
root 379 1 0 19:43:12 ? 00:00:00 /etc/lmcfsd
root 650 649 1 19:44:41 ttyp2 00:00:00 grep lmcThe LMC module is not required to be running on the remote print server.
In order to have access to the printer share on the remote server, the client user must log on to that server as follows:
#lmc logon scotop administratorwhere "administrator" is a default user account that should exist on the remote AFPS or NT print server. A user account other than "administrator" can be used once it is created on the server.
NOTE: There is no visible response to the "lmc logon" command but on the remote server, the AFPS "#net sessions" command" should display the session. For example:
\\SCOTEST-00010 ADMINISTRATOR OS/2 LM 2.0 0 00:05:00Print the Test:
--------------
Now print a test file to the remote print share from the
client system:# xtod /etc/default/lang > /tmp/lang
# lp -onobanner -d zag /tmp/lang
request id is zag-326 (1 file)The print request should now print on the remote printer.
# lmc logoffNOTE: It has been seen that printing to a AFPS 4.0.2/3.5.2n shared printer
the only output that comes out will be the banner page unless the
-onobanner option is used.This issue has been reported to SCO Engineering.
NOTE: If you see this error message from mail:Reason for failure:/usr/spool/lp/bin/rlmclp : Server unavailable : Not availablefrom an "lp" request, then this problem has been reported to SCO Engineering.
NOTE: If the user fails to log on to the remote server, the print
requests may remain in the local print queue, for example:# lpstat -o
zag-352 root 1228 Nov 21 18:16They may also receive mail with the following error:
... ... Subject: Status of lp request. ... ... Subject: Status of lp request zag-350
Your request zag-350 destined for zag encountered an error while printing on printer zag.
Reason for failure:/usr/spool/lp/bin/rlmclp : Operation not permittedAnother error, "Remote I/O error" may also be seen. This indicates that the LMC module has received an SMB error from the remote print server. Check that the print share specified is a valid share.
Alternatively, run the "/usr/bin/vcview" command to verify that you have logged on successfully.
See also
lmc(LMC)TA100065, "How do I load and use a LAN Manager Client module with SCO AFPS?"