Technical article 100065

How do I load and use a LAN Manager Client module with SCO AFPS?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

SCO provides a LAN Manager Client (LMC) module as part of the SCO
OpenServer 5.0.x product.  How do I load and use this module?

Solution

To load the LAN Manager Client (LMC):

Insert the SCO OpenServer 5.0.x product CD-ROM into your CD-ROM drive.

As the user "root", run the SCOadmin(ADM) utility.

Choose the <Software Manager> option.
Select the <Software> option.
Select the <Install New> option.
Choose the current host when prompted.

Choose the Media Device, for example "SCSI CD-Rom Drive 0".

Choose "SCO OpenServer Enterprise System (ver 5.0.x)".

For OpenServer 5.0.0:
Select "Partial".
For OpenServer 5.0.2+:
Select "Connectivity".
Select "LAN Manager Client (ver 2.0.x)".

When prompted, enter your system License number, code and data or enter "Defer" to defer the licensing of the product, if required.

The LMC module now has to be configured into the network stack. In the example system, SCO TCP/IP and SCO TPI NetBIOS for TCP/IP were already configured over a 3COM Etherlink III ISA Combo (3C509) network card.

As the "root" user, start the Network Configuration Manager:

#netconfig

Highlight the network card for the system.

Select <Protocol>.
Select <Add Protocol>.
Choose "LMC Runtime System".
Select <Add>.

Should this choice not be available then add:

"SCO TPI NetBIOS for TCP/IP"

and when prompted, relink the kernel and re-boot the server. Return to "netconfig" and you will be able to add the LMC Runtime System beneath the "SCO TPI NetBIOS for TCP/IP" layer:

HW Intel(R) PRO/100+ PCI Adapter - PCI Bus# 0,Device# 9,Function# 0 SCO TCP/IP - SCO NFS Runtime System SCO TPI NetBIOS for TCP/IP - LMC Runtime System

Accept the default number of connections, Sco_nb, as 64.

This message should then appear:

The following products were successfully configured into the system LMC Runtime System SCO TPI NetBIOS for TCP/IP

Recreate the system kernel when prompted and reboot.

On reboot of the system, the LMC module should be automatically
started.  For example:

... Starting TCP Services: ... Starting netbios: nbd Starting LMC ... LMC Startup complete Starting NFS services: ... ... ...

The LMC daemon is now running, for example:

#ps -ef|grep lmc
...
=> root 366   1 0 18:43:54   ?   00:00:00 /etc/lmcfsd
...
or use:
#lmc status
=>LMC is running

The LMC can now be used to mount remote LAN Manager (or LAN Manager-like) filesystems onto the local filesystem.

Example:

Use "#net view" to check that a system is visible to your primary domain controller.

From the Advanced File and Print Server Primary Domain Controller (PDC) system, "systemx", connect to the Backup Domain Controller (BDC) system "systemy".

#lmc logon systemy administrator

Now mount the remote system resource onto your local filesystem onto, for example, the "remote1" mountpoint.

#mount -f LMCFS systemy/USERS /remote1

To remotely mount a High Sierra CD-ROM, use these commands:

On "systemy":
#mount -f HS,lower /dev/cd0 /cdrom
#net share cd1=c:/cdrom
On "systemx", the local system, use:
#lmc logon systemy administrator
#mount -f LMCFS systemy/cd1 /mnt
#cd /mnt
#ls
To log off the system, use:
#lmc logoff systemy

Follow the same steps to mount a resource from a Microsoft NT 3.51 server that is on the same physical network and uses TCP/IP as the primary access provider.

You can also mount a local server based LMCFS.

Log in as a client onto your own Advanced File and Print server, "systemx":

$lmc logon systemx administrator
=> Password:

The session should now be made with the local server.

$net sessions
Computer     User name        Client Type      Opens Idle time
--------------------------------------------------------------
...
\\SYSTEMX-00002  ADMINISTRATOR   OS/2 LM 2.0    0   00:06:01
...

Mount a share, for example "MSOFFICE", onto a directory mount point, in this example "/mnt"

#mount -f LMCFS systemx/MSOFFICE /mnt
#cd /mnt
#ls
... etc. etc.
NOTE:     If you forget to initially "lmc logon" you may get the error,
          "ksh: /mnt: bad directory"

See also

SCO OpenServer Guide to Gateways for LAN Servers, Chapter 4.

The manual entry for lmc(LMC).

From the Xinuos technical article database, record 100065. Reproduced with permission. The original is at www.sco.com/ta/100065, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.