Problem
The LAN Manager Upgrade Release 2.2.2, Maintenance Supplement 106 (MS106), contains the file:
/usr/net/servers/lanman/supplement/readmeWhat is contained in this file?NOTE: Due to attached documentation, this article is especially long.
It may be unsuitable for faxing. Solution
The file:/usr/net/servers/lanman/supplement/readmecontains information on problems resolved in this release, performance and troubleshooting, printing and tuning.
The entire file is appended to this article.
See also
IT lmu/89, "What is LAN Manager Upgrade Release 2.2.2 (MS106)?".
IT lmu/106, "The 'net files' command still fails for large numbers of open files in 2.2.2.".
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Microsoft(r) LAN Manager for SCO(r) SystemsRelease 2.2.2 May 1995
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1 INTRODUCTION2 NEW FEATURES
2.1 Client printing is easier and more reliable
2.2 Improved file replication
2.3 Improved account replication
2.4 Improved filesystem access from client workstations
2.5 No more incorrect "sharing violation" error messages
2.6 Improved terminal emulation
2.7 lmshell now sees specific files in a directory
2.8 Runaway server processes are prevented
2.9 Improved NetAdmin functionality
2.10 Improved audit functionality
2.11 Large numbers of open files now display correctly
2.12 UNIX group permissions available on files created by LAN Manager3 PERFORMANCE AND TROUBLESHOOTING NOTES
3.1 Checking user security files before installing LAN Manager
3.2 Running out of STREAMS
3.3 Avoiding timeouts with TCP/IP by disabling keepalives
3.4 Improving performance with NetBEUI-based terminal emulation program
3.5 Logged on, but not validated by a server
3.6 Files and directories on CD-ROM filesystems not visible
3.7 Using the LAN Manager server as a client through lmshell
3.8 Administering your server with the NetAdmin utility
3.9 Known limitations of the LAN Manager server4 PRINTING NOTES
4.1 Extraneous characters (~0~10) with LaserJet printer
4.2 LAN Manager server hangs when printing from client
4.3 Setting up shared client printing5 TUNING YOUR SYSTEM TO INCREASE CLIENT CONNECTIONS
5.1 LAN Manager server licensing
5.2 LAN Manager server configuration
5.3 UNIX kernel tuning
5.4 Using VTP in addition to the LAN Manager client
5.5 Special concerns with large numbers of clients6 OVER-THE-NETWORK INSTALLATION OF THE LAN MANAGER WORKSTATION1. INTRODUCTIONMicrosoft(r) LAN Manager for SCO(r) Systems Release 2.2.2 (hereafter
referred to as Release 2.2.2) provides the latest updates to the
LAN Manager server. Release 2.2.2 is supported on these platforms:+ SCO OpenServer(tm) Release 5+ SCO Open Server(r) or Open Desktop(r) Release 3.0+ SCO UNIX System V/386 Release 3.2 Operating System Version 4.2+ SCO MPX(tm) Release 3.0This document provides the latest information available at the time of this release. If the information in this document differs from that contained in any of the printed guides in the LAN Manager documentation, please consider this document to be the most current.
Certain notes in this document are marked as applying only to the
Enterprise Edition because the information relates only to LAN Manager
workstations, which are not part of the Workgroups Edition. Workstations
are also sometimes referred to as "clients."When reading the LAN Manager Release Notes, please substitute your
current system release for any mention of "Open Desktop 2.1". Also,
please substitute "Microsoft(r) LAN Manager for SCO(r) Systems" for any
mention of "Microsoft(r) LAN Manager for UNIX(r) Systems" throughout the
documentation.2. NEW FEATURESThe Release 2.2.2 server includes these improvements over Release 2.2.0 (details follow):
- client printing is easier and more reliable - improved file replication - improved account replication - improved filesystem access from client workstations - no more incorrect "sharing violation" error messages - improved terminal emulation - lmshell now sees specific files in a directory - runaway server processes are prevented - improved Net Admin functionality - improved audit functionality - large numbers of open files now display correctly - UNIX group permissions available on files created by LAN Manager
2.1 Client printing is easier and more reliableClient printing is easier and more reliable with the following new features (details follow):
- lmadmin scripts fixed - improved printer sub-system reliability - using PRINTSTA instead of CLISPOOL or CLIPCACH (Enterprise Edition only)
See also section 5 "PRINTING NOTES."2.1.1 lmadmin scripts fixedThe lmadmin scripts (held in the /usr/net/servers/lanman/fmli directory) have been fixed so you should no longer experience the following problems:
- changes to the client printer type are not saved - cannot delete a client printer - changes to preprocessing or postprocessing sequence are not saved - cannot enable or disable printer
2.1.2 Improved printer sub-system reliabilityThe printer sub-system problem that generated lmx.srv terminations and
subsequent core dumps has been corrected. This problem was indicated
when the net error command yielded the output:NET3100 / LMU6060 server process unexpectedly terminated2.1.3 Using PRINTSTA instead of CLISPOOL or CLIPCACH (Enterprise Edition
only)If you use the DOS CLISPOOL or CLIPCACH utilities for client printing, you might experience hangs or other difficulties if the workstation is running Windows or other networking products because CLISPOOL is not supported in these environments.
A better approach is to use the MS-DOS(r) Print Station service, which is
recommended by Microsoft and works reliably with Windows. When
PRINTSTA.EXE is loaded on the enhanced DOS workstation, the client
becomes a print server, allowing DOS, OS/2(r), Windows NT(tm), and
Windows for Workgroups workstations to print directly to the DOS client
acting as a print server.For details about loading PRINTSTA.EXE on the client, see section 4.3
"Setting up shared client printing" later in this document. (This
section also provides information about setting up a Windows for
Workgroups or Windows NT client as a print server.) For information on
configuring the PRINTSTA.EXE utility on a DOS workstation, see Page 132
of the LAN Manager User's Guide for MS-DOS.By default, the LAN Manager server's client printing facility is
compatible with the CLISPOOL and CLIPCACH client printing agents. A new
shell script is provided that allows the LAN Manager server to
interoperate with the PRINTSTA.EXE agent.You must use this new shell script to replace the binary file
/usr/net/servers/lanman/clipr/clipr, which is the agent on the server
that converses with the CLISPOOL or CLIPCACH printing agent on the
workstation. The new clipr script provides connectivity with compatible
LAN Manager print resources on the network: OS/2, Windows NT, Windows for
Workgroups, or even another LAN Manager server. This should greatly
simplify your network printing setup._________________________________________________________________________
NOTE The following modification globally affects client printing
services on the server and is not compatible with the CLISPOOL and
CLIPCACH client printing agents.
_________________________________________________________________________To modify the server:1. Log in as root.2. Back up the original copy of the following file:/usr/net/servers/lanman/clipr/clipr3. Use the following commands to replace that clipr binary file (which
interfaces to the CLISPOOL program running on a client) with a new
script that interfaces the LAN Manager print spooler to the PRINTSTA
utility:cd /usr/net/servers/lanman
cp supplement/clipr clipr/cliprThis new file is a shell script that takes the same arguments as the clipr program, but sends the print data to the PRINTSTA utility running on the specified client.
4. Use the following commands to change the permissions on this file to
make the script executable and to set the appropriate ownership on
the file.cd /usr/net/servers/lanman/clipr
chmod 755 clipr
chown lanman clipr
chgrp DOS---- cliprSee also section 4.3 "Setting up shared client printing" later in this document for details about configuring the server for shared printing.
2.2 Improved file replicationSupport has been added for the repl_fileperms keyword in the lanman.ini
file. This keyword was ignored in previous releases. Replicated files
should carry ownership and permissions to the replicated systems.2.3 Improved account replicationAccount replication is more flexible and reliable with the following new features (details follow):
- UAS replication improved between heterogeneous servers - replicated file ownership and permissions support - account replication is reliable with home directories in UNC format - full account synchronization provided
2.3.1 UAS replication improved between heterogeneous serversUser Accounts Subsystem (UAS) information now replicates correctly between Microsoft Windows NT Advanced Server and SCO LAN Manager servers.
2.3.2 Account replication is reliable with home directories in UNC formatWhen an account is created with the home directory specified in UNC
format, you no longer have problems when account replication is attempted
between servers within a domain, and you no longer repeatedly receive
LMU6086 errors. (These errors were logged in the server log file on the
backup domain controller.)The account is now created normally, except that it is created without a home directory; the UNIX system administrator needs to set up a home directory when enabling the account (as is normally required).
The home directory specification for the /homedir option to the net user
command should always follow UNC format. In the LAN Manager
documentation, the description for the /homedir option implies that you
can specify a home directory in UNIX format. For example:net user <user> <passwd> /add /homedir:c:/home1/lanman/userdirIf you specify the home directory in UNIX format, the account will be created, but the home directory will not be usable from the client.
Instead, you should specify a home directory in UNC format. For example:net user <user> <passwd> /add /homedir://<servername>/<sharename>/<userdir>where:- <servername> is the name of the LAN Manager server that will be hosting the home directory for this user. - <sharename> is the name of a share on the server under which the user's home directory will be created. - <userdir> is the name of the user's home directory.
Example:net user scotts passwd /add /homedir://bear.serve/users/scottsThis command will build the home directory for the LAN Manager user
scotts as /u/lanman/scotts. Remember, during installation, the sharename
of "users" is added to the system for you. This sharename, by default,
points to the /u/lanman directory. Any sharename for a disk resource can
be used in this manner.When the user scotts does a net logon from a client, he can connect to
his home directory as it was defined by the net user /add command. Using
the command below, scotts can connect to the share containing his home
directory using the logical drive D:net use D: /home2.3.3 Full account synchronization providedFull account synchronization is now forced during account replication if
an error is detected in a partial synchronization. Account replication
will not halt when synchronization errors are detected, and the errors
will be written to the server's error log (accessible with the net error
command). In earlier releases, if a user had been added but no group was
present for that user, LAN Manager would detect the missing group early
in the replication cycle and abort the process.2.4 Improved filesystem access from client workstationsWindows NT workstations no longer experience:- repeated filenames when listing the contents of a very large directory on the LAN Manager server. - file corruption or truncation when a file is copied from a LAN Manager server.
Windows For Workgroups workstations running Version 3.11 no longer
experience slow file loading and transfer with the LAN Manager server
when using the NetBEUI stack in protected mode. This was corrected with
changes to the datalink driver.2.5 No more incorrect "sharing violation" error messagesA second client trying to run an application already in use by another
client from a shared drive no longer incorrectly receives an error
message implying that application license sharing is being violated. If
proper application licensing exists, the second client can run the same
application as normal. This problem was originally seen when trying to
run Foxpro, but might have occurred with other applications as well.2.6 Improved terminal emulationA problem with hangs of large amounts of data through vtp (or other terminal emulation programs) over NetBEUI has been fixed.
In addition, vtpsrv now provides reliable terminal emulation connections. These problems have been resolved:
- disconnection from the server and inability to reconnect to the server via terminal emulation program - console messages of t_accept and/or t_rcv - error messages issued by Century Software's Tiny Term and Term terminal emulators of write error 0, write error 24, and cmd 12h error 08h session number out of range
In addition to improvements to the vtpsrv binary, this release contains an updated NetBEUI driver that has been modified to allow granular flow control of the read/write data streams.
2.7 lmshell now sees specific files in a directoryWhen using lmshell, if you enter a dir command with a specific filename, you should now see the file correctly displayed, instead of getting an error message of "0 files found". However, you will still have this problem if you are in the UNIX root directory when you start lmshell and then enter a dir command with a specific filename at the DOS prompt.
2.8 Runaway server processes are preventedThe potential for lmx.ctrl and lmx.srv server processes to "run away" or
"spin" has been reduced. The symptoms of runaway server processes
include slow server response, 100% CPU activity, little disk access, and
no service to clients._________________________________________________________________________
NOTE These improvements notwithstanding, lmx.ctrl and lmx.srv
processes can spin if the server is not tuned properly to handle
the workload. For additional information about tuning, see the
relevant transport sections (5.3) in "TUNING YOUR SYSTEM TO
INCREASE CLIENT CONNECTIONS" later in this document.
_________________________________________________________________________2.9 Improved NetAdmin functionalityThis release updates NetAdmin from 2.1 to 2.2 in the LAN Manager server's
DOSUTIL share. Customers with the Workgroups edition of LAN Manager were
not eligible for the DOS 2.2 Client update and therefore had no upgrade
path for the Windows based LAN Manager server administration tool,
NetAdmin.NetAdmin 2.2 was previously available with the DOS 2.2 client update.
NetAdmin 2.2 resolves the following reported problems:
- corruption of the /usr/net/servers/lanman/datafiles/accounts.lmx file
- default creation of access control lists for every file in the
directory tree when using the "Permit Tree" option during permission
setting. Access control lists at the file level are not required by
default and their use increases the size of the accounts.lmx file.
- client hangs when setting access permissions on a server resource.
Error 59 is commonly seen when this occurs.
- setting permissions with Windows NetAdmin on a directory with 64 or
more entries now works properlySee the NetAdmin section (3.8) under "PERFORMANCE AND TROUBLESHOOTING" to
enable the new release of NetAdmin on your workstation.2.10 Improved audit functionalityThe net audit command now accurately reports the audit trail from the
server's /usr/net/servers/lanman/logs/net.aud file. Previously, certain
entries in the net.aud file would cause net audit to fail and dump core.The failure and success options of the net access command now work
correctly. These options allow you to monitor successes and failures for
a number of defined events; previously, all events were displayed
regardless of the options set. See the LAN Manager Troubleshooting and
Command Reference for more information about configuring these options.2.11 Large numbers of open files now display correctlyThe net file command and the NetAdmin Opened files interface now
accurately display open files. The output of these commands previously
displayed blank or corrupt entries when there were large numbers of open
files.2.12 UNIX group permissions available on files created by LAN ManagerPreviously, files created by LAN Manager users were assigned "DOS----"
DOS group attributes, regardless of their UNIX GID (group ID). Because
LAN Manager groups do not correspond to UNIX groups, these files were not
accessible to others in the user's UNIX group.It is now possible to set permissions assignment such that files created
by a LAN Manager user will correspond to the user's UNIX GID. Although
the DOS file attributes are thereby lost, file accessibility and
interoperability is improved, particularly if you are running UNIX system
applications that must access files created by LAN Manager users.To enable UNIX group permissions on files created by LAN Manager, edit this keyword in the server's lanman.ini file:
[ lmxserver ]
unixgroups=yes
The default is "no".3. PERFORMANCE AND TROUBLESHOOTING NOTESSome of the following might help you administer your LAN Manager network or troubleshoot LAN Manager problems more easily:
- checking user security files before installing LAN Manager - tuning for more than 64 clients - running out of STREAMS - avoiding timeouts with TCP/IP by disabling keepalives - improving performance with NetBEUI-based terminal emulation program - logged on, but not validated by a server - files and directories on CD-ROM filesystems not visible - Novell NE2000 Ethernet card - maxnames is size of local name table - using the LAN Manager server as a client through lmshell - administering your server with the NetAdmin utility - known limitations of the LAN Manager server
The details of these suggestions are given in the following sections.
3.1 Checking user security files before installing LAN ManagerThe UNIX utility addxusers fails at installation (without any error messages) if the system user security files contain any discrepancies. Prior to installing LAN Manager, be sure to run fixperm(ADM) and authck(ADM) to make sure there are no errors in the user accounts. If you do not perform these checks first, LAN Manager will appear to install properly, but the server will not run.
3.2 Running out of STREAMSBecause LAN Manager is heavily dependent on STREAMS resources, you should
periodically check STREAMS availability. If TCP/IP is installed on your
system, use the netstat -m command to do so; otherwise, use the crash
strstat command. If you are experiencing failures from running out of
STREAMS, you can reconfigure STREAMS by following the procedures in the
administrator's guide for your operating system. Also, see section 5
"TUNING YOUR SYSTEM TO INCREASE CLIENT CONNECTIONS" later in this
document.3.3 Avoiding timeouts with TCP/IP by disabling keepalivesIf you do client printing or use a Basic DOS client over TCP/IP on any of
the DOS workstations, you might experience connections dropping after 10
minutes. To eliminate this timeout problem, disable the NetBIOS
keepalive mechanism._________________________________________________________________________
NOTE If you are running TCP/IP Release 1.2.1, you must install the
latest version of SLS NET382 to complete this procedure. To obtain
SLS NET382, call your service provider or SCO supplier; it is also
available from the SCO bulletin board.
_________________________________________________________________________You can disable TCP/IP NetBIOS keepalives via a kernel tunable with the following steps:
1. Log in as root. On the server, change directory to where the NetBIOS
driver is held and back up the original space.c file:cd /etc/conf/pack.d/nb
cp space.c space.orig2. Modify the space.c file so that the "nb_sendkeepalives" assignment
reads:int nb_sendkeepalives = 1;3. Change directory to relink the kernel:cd /etc/conf/cf.d
./link_unix -y4. Reboot the server with:/etc/reboot3.4 Improving performance with NetBEUI-based terminal emulation programWhen using a terminal emulation program over NetBEUI, the communication can be very slow because, in certain circumstances, the number of piggyback acknowledgements sent by the client to the server increases.
You might be able to improve performance by modifying the vtp client so
that it does not send the piggyback acks to the server. To make this
change, add the following line to the [NETBEUI_XIF] section of the file
C:\LANMAN.DOS\PROTOCOL.INI on the DOS workstation:PIGGYBACKACKS = 0Then, reboot the DOS workstation for this change to take effect.
3.5 Logged on, but not validated by a serverWhen trying to connect to a LAN Manager server with a net logon command, if you receive an error message about being logged on, but not validated, consider these possible causes:
- There are not any servers in your domain setup in USER level security. - There are not any servers set up in your domain to validate logons, that is, there are not any servers set up as primary or backup domain controllers. - There are not any primary or backup domain controllers in your domain running the Netlogon service. Specifically, the process lmx.dmn is not running on any primary or backup controller in your domain. - The user name you are using with the net logon command does not exist in the User Accounts database. - The NetBIOS computer name of the workstation or server contains an illegal character, such as a space.
*** If you are running LAN Manager over TCP/IP: ***
- The scope identifier is not the same for your workstation and any of
the primary or backup domain controllers in your domain. Specifically,
the DOS client scope identifier differs from the scope identifier
defined by the "nb_scope" variable in the /etc/default/nbconf file.3.6 Files and directories on CD-ROM filesystems not visibleFiles and directories with names containing uppercase characters are not
visible to the LAN Manager workstation because of the UNIX to DOS
filename translation rules. CD-ROM filesystems containing uppercase file
and directory names can be mounted with the special "lower" option, which
automatically translates file and directory names containing uppercase
characters to all lowercase.mount -fHS,lower,novers /dev/<device> /<mnt>3.7 Using the LAN Manager server as a client through lmshellYou can use lmshell to print or transfer files from a LAN Manager server to an OS/2 server, Windows for Workgroups, or any other type of server. See the lmshell manual page for details.
3.8 Administering your server with the NetAdmin utilityAfter the initial installation and configuration, we recommend that you administer your LAN Manager network from a client workstation using the Windows NetAdmin utility.
The Server Maintenance Supplement contains the latest version of the
Windows NetAdmin utility, Release 2.2. To enable NetAdmin on your
workstation, copy the NetAdmin binary file (netadmin.exe) and the help
file (netadmin.hlp) from the /usr/net/servers/lanman/shares/dos directory
on the server to your workstation.Follow these procedures to update the NetAdmin utility on the workstation to the latest version:
1. Connect to the dosutil directory from a LAN Manager 2.2c workstation.
2. Log in as the admin user and copy the files from the dosutil drive to
your workstation (we suggest you copy them to the \lanman.dos\netprog
directory).You can then run NetAdmin as described in Chapter 2, "Using the
Administrative Interfaces", of Administering LAN Manager. We recommend
that you do not run NetAdmin on the workstation from the virtual drive.3.9 Known limitationsThese known limitations have been observed for this release of the LAN Manager server (details follow):
- maxnames is size of local name table - net time set option - multiple primary domain controllers - netrun service limitations - NFS mandatory locking problems - shared NFS filesystems must be exported as root - system time discrepancies - replication problems with long pathnames - Novell(r) NE2000 Ethernet adapter
3.9.1 maxnames is size of local name tableChapter 6 of the LAN Manager Installation and Configuration Guide
incorrectly defines maxnames. maxnames is the size of the local name
table on the computer being configured. This name table size limits the
number of NetBIOS names that can be claimed by this system. On the
LAN Manager server, 5 names are claimed by the current set of LAN Manager
services.3.9.2 net time set optionThe /set option of the net time command is not supported from the UNIX shell prompt.
3.9.3 Multiple primary domain controllersIt is possible to inadvertently install a second primary domain
controller in a domain that already has one. Under normal circumstances,
the new server will poll the domain during installation to detect the
presence of a primary domain controller and prevent itself from
configuring as a primary domain controller if one is detected. However,
if network problems prevent the new server from polling, it will be
installed as a primary domain controller. When the network is restored,
the second primary domain controller cannot start its Netlogon service.When you install a primary domain controller, be sure that one does not already exist in that domain.
3.9.4 Netrun service limitationsThe Netrun service is designed for a single session under Windows. If
two or more sessions are established from one client to one LAN Manager
server, as might occur by running netrun from two DOS screen sessions on
a single workstation (for example, under the Microsoft Windows or OS/2
operating systems), one of the sessions might hang.3.9.5 NFS mandatory locking problemsWhen LAN Manager copies a file from a DOS or OS/2 client to the server, it sets the mandatory lock bit in the file's UNIX permission string. Listing the file shows a capital "S" in the group section of the file's permissions, as in the following example:
-rwxrwSrwx root other <filename>*An NFS client is unable to edit or execute the file, and the file appears
to NFS to have zero length. If this is a problem, use the -l (lowercase
"L") option of the chmod command to release the lock bit:chmod -l <filename>Also, refer to the LAN Manager Release Notes for information on the use of NFS-mounted filesystems.
3.9.6 Shared NFS filesystems must be exported as rootWhen mounted NFS filesystems are shared via LAN Manager, they must be
exported from the NFS server with root permissions. Otherwise, when a
LAN Manager workstation user tries to create a file in the shared NFS
filesystem, a write error is generated and the file size is listed as 0.To export a filesystem as root from an NFS server:
1. Edit the NFS server's /etc/exports file and add the line:/<your_filesystem> root=lanman_server(See also the exports(NF) manual page.)2. Export the filesystem by issuing the command:exportfs -a(See also the exportfs(NADM) manual page.)3.9.7 System time discrepanciesThe LAN Manager server has only an approximate idea of the system time,
which is updated at least once a minute. Thus, if the operating system
time is changed, there is a period during which the server's time is
inaccurate. If the server statistics are cleared during this period, the
LAN Manager statistics timestamp, as well as session idle times, will be
inaccurate.3.9.8 Replication problems with long pathnamesTrying to replicate a file with a pathname that is longer than 256
characters fails and no error log entry is generated. The replication
service supports only FAT-compatible files with no extended attributes.3.9.9 Novell NE2000 Ethernet adapterUse of the Novell NE2000 Plus Ethernet adapter on the LAN Manager server over NetBEUI is not supported in Release 3.1 of the SCO LLI Driver Disk. Only Release 3.2 or later of the LLI Driver Disk offers this support.
4. PRINTING NOTESIf you experience problems with client printing, you should first check the printing section (2.1) under "NEW FEATURES" to see if this server update solves your problems.
The following sections can help you solve other client printing problems:
- extraneous characters (~0~10) with LaserJet printer - LAN Manager server hangs when printing from client - setting up shared client printing
4.1 Extraneous characters (~0~10) with LaserJet printerAn error in the 495hp section of the /usr/lib/terminfo/terminfo.lp file
causes a client printer configured as an "hplaserjet" to print ~0~10 at
the top of each print job. To correct this problem, modify the
terminfo.lp file so that the "is2" definition in the 495hp section reads:is2=\E&k0S,After you make this change, save the file and then recompile the terminfo.lp with the tic command:
tic terminfo.lp4.2 LAN Manager server hangs when printing from clientOn systems prior to SCO OpenServer Release 5, when a print job is submitted to the LAN Manager server from a client using any of the network printer shares made available by that server, the server can hang. This happens when the UNIX system spooler returns a print request ID to the LAN Manager server that is greater than or equal to 8192, resulting in one or more of these symptoms:
- Occasionally, lpsched appears as if it has died and is not present in
the process table.- A print request on the client from the DOS command line hangs for
approximately one minute and eventually responds with the error:NET805: Network device no longer exists writing device <devicename>
- When printing from Microsoft Windows, the following error messages
occur:Error: Cannot Write to Device <devicename>Windows cannot write to this file. The disk may be full. Delete any unwanted file, and then try again.
- Attempts by other clients to use the server fail. For example, a net
logon request will fail with the following message:NET3779: Your logon attempt has failed due to an incorrect username or password
If you have not yet experienced any of these symptoms, you can avoid the problem by running the setlpcyc script as described in Step 4 below.
To recover a hung server without disconnecting clients or rebooting the machine:
1. Log in as root. If the system has already been recovered or
rebooted, perform only Step 4.
2. Get the pid (process identification number) of the lmx.srv process
that spawned the first born setlpcyc process using the ps -ef
command. In this listing find the setlpcyc process with the lowest
pid. The number to the right of the pid is the ppid (parent process
id) or the process id number of its parent. In this case the ppid
should be the lmx.srv process. You will also use this pid in Step 5.
3. Use the ps -ef command again to find the pid of each of the setlpcyc
processes. Kill each of the setlpcyc processes with:kill <pid>where <pid> is the process id of the setlpcyc process being killed. Check to see that all the setlpcyc processes have been killed by performing another ps -ef command and looking for them in the output. If some of the setlpcyc processes are still present, attempt to kill them with the kill -9 <pid> command. 4. Run the setlpcyc script to reset the /usr/spool/lp/temp/.SEQF file:
/usr/net/servers/lanman/bin/setlpcyc5. Stop and start the server:/etc/ms_srv stop
net start serverIf this does not restore normal server function, reboot the system.
4.3 Setting up shared client printingConfiguration of the server for a shared client printer is the same for
workstations running CLISPOOL, CLIPCACH, and PRINTSTA.EXE. It is the
configuration of the workstation that changes.See the printing section (2.1) under "NEW FEATURES" for the supplemental server configuration for interoperability with the PRINTSTA.EXE client printing agent.
4.3.1 Configuring the LAN Manager server for connection to a client printerThe server acts as a liaison between the workstation requesting a print
job and the workstation hosting the destination printer. The server
spools print data to its spool directory and manages the flow of print
requests to the client hosting the designated printer.Configuring the server:- enables the server to spool print requests to a client-hosted printer.- establishes a shared client-printer-queue sharename on the server to
which network workstations can connect and print.The server provides a unique sharename for each client printer for which it manages print requests.
To configure a LAN Manager server using the lmadmin utility:
1. Invoke lmadmin by entering:/usr/net/servers/lanman/bin/lmadmin2. Select Printer Administration.
3. Select Define Client Printers.
4. Press the ADD key to add a printer.
5. Enter the DOS workstation name in the "Client computername:" field.
6. In the "Printer type:" field use the CHOICES key to select from the
list of supported printers. If in doubt, select or enter "dumb".
7. Press the SAVE function key.
8. Press the CANCEL function key.
9. Exit the lmadmin menu.For more information on the lmadmin interface, see "Using the UNIX System Administrative interface" in Chapter 2 of Administering LAN Manager.
This operation shares a disk resource under the name of your DOS
workstation suffixed with the letter "Z". This resource is the print
spool area on the server used for communication with clients using the
CLISPOOL and CLIPCACH printing agents. These printing agents read the
print data off the server by connecting to this share on the server.Workstations hosting printers that do not use CLIPCACH or CLISPOOL do not
connect to this "Z" share on the server. Instead, the server directly
transfers the print data to PRINTSTA.EXE, or some other agent, on the
workstation.There will also be an entry in the UNIX system spooler by the name of the
DOS client print server. This is the spool queue to which UNIX system
print jobs destined for the DOS workstation will be sent. (This is also
the name that is used below for the <unix-spooler-name>.)The LAN Manager server must net share the client printer resource so that
workstations on the network can access it with a net use command or from
within Microsoft Windows. To create this print share, log in to the
server as root and set default access permissions for it:net share <shared-printer-queue>=<unix-spooler-name> /print net share <shared-printer-queue> /perm:wc net access \\print\\<shared-printer-queue> /add <user>:y
Choose any unique name as the <shared-printer-queue>. The <unix-
spooler-name> is the name assigned by the lmadmin utility, and will be
the name of the DOS client print server.4.3.2 Configuring a workstation as a print serverYou can configure the following workstations as print servers:
- DOS workstation using PRINTSTA.EXE- DOS workstation using CLISPOOL or CLIPCACH- Windows for Workgroups workstation- Windows NT workstation4.3.2.1 DOS workstation setup as a print server using PRINTSTA.EXEThe following command executed on a DOS workstation named farallon installs the PRINTSTA.EXE terminate and stay resident utility into memory and configures it to use the printer on parallel port 1 (LPT1:) and to use the c:\tmp directory as its work area:
C:>\LANMAN.DOS\NETPROG\PRINTSTA /L:1 /W:C:\TMPWhen PRINTSTA is loaded, it reports the following:
Microsoft LAN Manager Print Station Copyright (c) 1992 Microsoft Corporation
Print Queue: \\FARALLON\LPTThis indicates that PRINTSTA.EXE loaded correctly and has created the
network print share of LPT available on the network. This print share
can be connected to in the same manner as a share on the LAN Manager
server:net use LPT2: \\FARALLON\LPTA LAN Manager server modified to converse with the PRINTSTA.EXE utility on a workstation would connect to this printer share in the same manner.
For more information on configuring the PRINTSTA.EXE utility on a DOS workstation, see the printing section (2.1) under "NEW FEATURES" above and Page 132 of the LAN Manager User's Guide for MS-DOS.
4.3.2.2 DOS workstation setup as a print server using CLISPOOL or
CLIPCACHThe procedure for setting up a shared client printer in Chapter 6 of
Administering LAN Manager omits an important configuration step. Before
proceeding with Step 9 on Page 6-9 of that guide, add the following
command to the AUTOEXEC.BAT file as well. Do not proceed to Steps 9 or
10 in the guide until this is complete.net use <driveid> \\<servername>\<clientname>Zwhere:- <driveid> is the same <driveid> used in the clispool or clipcach
command in the previous steps- <servername> is the NetBIOS name of the LAN Manager server that the
client printer was configured on and that will be handling the print
requests to the client- <clientname>Z is the share on the server that was created by the
client printer configuration process (the name of the client hosting
the printer is truncated to 7 characters and a "Z" is appended--see
the explanation of "Z" share in configuring the server above)This step establishes a connection to a disk share on the server in which
print requests for this workstation are spooled. The CLISPOOL and
CLIPCACH printing agents read from this <driveid> and direct the data
they read to the printer on the workstation in which they are running.For more information, refer to Chapter 6 of Administering LAN Manager, specifically Steps 8 and 9 on Pages 6-7 through 6-10.
4.3.2.3 Windows for Workgroups workstation setup as a print serverTo set up a Windows for Workgroups workstation as a print server on a LAN Manager network, you do not need PRINTSTA.EXE.
The setup on the server is the same as for a DOS client printer. The
difference is in the setup on the client that is to function as a print
server.Follow these procedures on the Windows for Workgroups workstation:
1. Click the PRINTER MANAGER in the CONTROL PANEL.
2. Select the printer you want to share.
3. On the toolbar, click the SHARE PRINTER AS button.
4. Type LPT in the share name box, then choose the OK button.4.3.2.4 Windows NT workstation setup as a print serverConfiguring a Windows NT workstation as a print server on a LAN Manager
network follows a similar procedure. Refer to the Windows NT manual.5. TUNING YOUR SYSTEM TO INCREASE CLIENT CONNECTIONSAs shipped, LAN Manager is configured for 64 clients under NetBEUI and
for 32 clients under TCP/IP, but the configuration can be modified to
allow additional clients. The number of LAN Manager client connections
is limited by:+ LAN Manager server licensing.+ LAN Manager server configuration.+ UNIX kernel tuning.+ using VTP in addition to the LAN Manager client.+ special concerns with large numbers of clients.5.1 LAN Manager server licensingThis is a fixed limit that sets the maximum number of client connections that the server will allow. The number of clients that the server is licensed to service can be displayed by the command "net config server". The Server Level indicates the license level. You can also display the number of clients by issuing the command:
/usr/net/servers/lanman/bin/sesslimwhich returns a number that indicates the total number of client to server connections supported by the server license. A value of 0 indicates that server will accept a maximum of 1000 connections.
5.2 LAN Manager server configurationThe lanman.ini file, in /usr/net/servers/lanman, contains a parameter
called "maxclients". The value against this parameter is the number of
client to server connections that the LAN Manager server will allow up to
the license level. This number is also displayed with the "net config
server" command.5.3 UNIX kernel tuningTuning the network transports affects the number of client-to-server
connections possible at the network transport level. This may involve
reconfiguring:+ kernel tuning parameters for both NetBEUI and TCP NetBIOS transports+ the NetBEUI transport stack+ the TCP NetBIOS transport stack5.3.1 Kernel tuning parametersThe operation and performance of the server may be limited by various kernel tuning parameters that control the resources available to the STREAMS facility used by the SCO networking products:
NSTREAM, NQUEUE, NBLKn
These parameters control the allocation of streams, queues and
data blocks._________________________________________________________________________
NOTE Only the NSTREAM parameter applies to SCO
OpenServer Release 5._________________________________________________________________________The values associated with each of these parameters will be
automatically increased when the LAN Manager server is
installed. While the increased allocation is sufficient for
the majority of installations, servers which encounter heavy
usage or have large (>64) number of clients connected may find
that the allocated resources are inadequate. The allocation
and usage of these resources can be monitored using the
"netstat -m" command. If the system does not have sufficient
resources then the "netstat -m" output will show failures in
the column headed "fail".To determine the optimal values for NSTREAM and NQUEUE, first load all the required networking products (including the LAN Manager server) and record the numbers listed in the "alloc" column of the "netstat -m" output. This will show the resource usage for an idle system. Each LAN Manager client connection will then require an additional stream (NSTREAM) and 6 (NetBEUI) or 8 (TCP NetBIOS) queues (NQUEUE). In other words, for 64 clients, you will need to ensure that there are 64 streams and 384 (NetBEUI) or 512 (NetBIOS) queues free after the server is initially loaded. For 256 client, you will require 256 streams and 1536 (NetBEUI) or 2048 (NetBIOS) queues in addition to those in use when the server is initially loaded.
To determine the optimal values for the NBLKn parameters, simply monitor the output of "netstat -m" for failures against these resources and increase the allocation for any resource that shows failures. While it may be tempting to increase these parameters to very large values, please keep in mind that the streams blocks use system memory which will limit the amount of memory available for running user applications. For example, increasing the NBLK1024 parameter by 1024 will require an additional 1 megabyte of system memory. Reducing the amount of system memory available for user applications will increase the possibility of the system having to swap processes to disk which will have an impact on the performance of the system. If it does become necessary to allocate large values to the NBLKn parameters, you may need to consider increasing the amount of RAM in the PC to maintain an acceptable level of system performance.
NMUXLINK, NUMTIM, NUMTRW
These parameters control the number of links that can be
established between network drivers in the UNIX kernel. Since
each LAN Manager client connection requires a corresponding
link to be established between the network drivers, the values
associated with these parameters will directly limit the number
of clients that can connect. In other words, NMUXLINK, NUMTIM
and NUMTRW should all be increased to a value that is in excess
of the maximum number of clients that will connect to the
server.Please note that all of the above parameters are also used by other SCO networking products. You will need to provide additional resources if, for example, you also have TCP/IP rlogin and telnet sessions active or your system is acting as an NFS server.
See also the "Tuning network resources" chapter in the SCO OpenServer Release 5 Performance Guide or for earlier operating system releases, the "Kernel parameter reference" chapter in the system administrator's guide.
5.3.2 NetBEUI TransportThe server comes configured to support 64 clients over the NetBEUI transport.
The Network Configuration Manager (on SCO OpenServer Release 5 systems) or the netconfig utility (on earlier operating systems) is used to configure the NetBEUI and Datalink layers of the NetBEUI transport. This process also adjusts other kernel parameters; see Pages 79 through 86 in the LAN Manager Installation and Configuration Guide for further details.
The MAXLINKS parameter in the NetBEUI layer, as described in the manual, is set to 64 by default. This is the parameter that needs to be modified to provide a greater number of client connections.
The MAXLINKS parameter in the Datalink layer has a direct correspondence with the MAXLINKS parameter in the NetBEUI layer and must be set to the same value.
The MAXSESSIONS parameter in the NetBEUI layer must be greater than or equal to the MAXLINKS value. By default the server is configured to allow 4 sessions per client connection for up to 64 clients (4*64=256).
5.3.3 TCP NetBIOS TransportThe server comes configured to support 32 clients over the TCP NetBIOS
transport. The number of supported clients can be increased by manually
editing the NetBIOS parameters; see Page 32 of the LAN Manager Release
Notes for further details. However, the Release Notes contain four
errors:1. It is suggested that increasing the TCPWINDOW parameter in the file
/etc/conf/pack.d/tcp/space.c above the default of 4*1024 will improve
the performance of the LAN Manager server. While this does provide a
noticeable increase in the performance of loading data from the
server, it can lead to problems when copying large amounts of data
from the client to the server. It is recommended that the TCPWINDOW
parameter is not increased above the 4*1024 default.2. The parameter in /etc/conf/pack.d/nbcots/space.c is called NBT_NDEV,
not NBT_DEV, and is set to 64 by default (this parameter has the same
effect as the MAXLINKS parameter of the Datalink and NetBEUI
transport in that it limits the number of clients that can connect to
the server). The value associated with this parameter must not exceed
256.3. The NB_NDEV parameter in the /etc/conf/pack.d/nb/space.c file is set
to 32 by default, not 64 as mentioned in the LAN Manager Release
Notes. It is this parameter that determines the limit of 32 client
connections in the default configuration. NB_NDEV and NBT_NDEV should
be set to the same value and must not exceed 256.4. The LAN Manager Release Notes omit configuration of the NB_NTPE
parameter in the file /etc/conf/pack.d/nb/space.c. This parameter is
the number of TCP/IP endpoints that the NetBIOS layer can establish
with the TCP/IP layer. This parameter also limits the number of
clients that can connect to the server. The value of this parameter
must not exceed 256.In addition to increasing the TCP NetBIOS parameters, you may need to increase the number of TCP connections that the system can handle. By default, TCP will allow 256 connections but many of these may be in use by processes such as the TCP/IP utilities and NFS server daemons (the output of "netstat -a" will list all TCP connections that are in use on the server). Since each LAN Manager client connection will also require a TCP connection, you will need to ensure that the system has sufficient TCP resources to accommodate the required number of clients.
To increase the number of TCP connections:
+ On SCO OpenServer Release 5 systems, use the Network Configuration
Manager to select TCP/IP over the appropriate network adapter, then
select Modify protocol configuration from the Protocol menu.+ On earlier operating systems, load the netconfig(ADM) utility, choose
the option to "Reconfigure an element in a chain" and select the chain
with the sco_tcp element.These screens will allow you to change the TCP configuration, including the number of supported connections.
In conclusion, if you want to configure the LAN Manager server to support up to 64 clients over the TCP NetBIOS transport, it is necessary only to change the NB_NDEV parameter in /etc/conf/pack.d/nb/space.c to 64. However, if you want to increase the number of supported clients connections then follow the directions in the LAN Manager Release Notes together with the additional notes provided above.
For consistency, the /etc/default/nbconf file should also be updated to reflect the changes in the NetBIOS space.c files:
+ NB_MAXNAME should be less than or equal to NB_NNAMETAB+ NB_MAXNCB should be less that or equal to NB_NREQ+ NB_MAXSSN should be less than or equal to NB_NSESSIONS+ NB_DFLTNCB should be less than or equal to NB_MAXNCB+ NB_DFLTSSN should be less than or equal to NB_MAXSSNThese parameters are used simply to limit the amount of NetBIOS resource that a single user process can consume and do not appear to effect the operation or performance of the LAN Manager server.
5.4 Using VTP in addition to the LAN Manager clientUsing the VTP remote login facility on a DOS system that is also running
the LAN Manager client has the effect of doubling the demand for kernel
resources. That is, you will need to double the resources allocated to
each client that has both an LAN Manager and a VTP session active. This
only applies to the resources detailed in Item 3 above. VTP does not
occupy a LAN Manager session so the number of VTP session is not limited
by the LAN Manager licensing level or the parameters in the lanman.ini
file.5.5 Special concerns with large numbers of clientsFor acceptable performance, we recommend that you plan to support no more
than 1000 registered users per server and no more than 256 clients per
server. Support for users or clients over these limits will require the
addition of potentially sizable server resources and extensive server
tuning to realize reasonable server performance.When a relogon request is sent from the server on restart, a net who
broadcast is generated. In networks with large numbers of clients, this
can result in heavy broadcast traffic and poor network performance. You
can disable the net who broadcast by editing this keyword in the
lanman.ini file:[ services ]
netlogon=lmx.dmn /netwho:no6. OVER-THE-NETWORK INSTALLATION OF THE LAN MANAGER WORKSTATIONThe network installation share directory on the LAN Manager server
contains an outdated version of the workstation software. To perform
over-the-network installation of the LAN Manager workstation, first
update the contents of this directory with the workstation software from
the LAN Manager 2.2c workstation disks. Then, perform the over-the-
network installation of the LAN Manager 2.2 workstation.The network installation share directory is usually accessed as the NINSTALL share from a LAN Manager workstation, or as /usr/net/servers/lanman/shares/ninstall on the server.
Refer to Chapter 5 of the LAN Manager Installation and Configuration Guide for detailed instructions on setting up the server for network installation of the DOS workstation, including establishing the NINSTALL share.
To update the network share directory with the LAN Manager 2.2c DOS workstation:
1. Log in to the server as root.2. Enter the following commands to change to the
/usr/net/servers/lanman/shares directory and back up the original
network installation directory containing the LAN Manager 2.2a DOS
workstation:cd /usr/net/servers/lanman/shares
mv ninstall ninstall.22a3. Create a new NINSTALL directory with the same permissions.4. If you are running merge on the server, go to Step 6.
If not, log in to a DOS workstation as the admin user:net logon admin5. Enter:net use <driveid>: \\<servername>\ninstall6. Using the DOS xcopy command or the Windows File Manager, copy the
contents of each of the following DOS workstation disks to a drive
that can connect to the NINSTALL share (merge users can copy the
contents of these disks directly to the new NINSTALL directory on the
server):- "dO Setup" - "dO Drivers 1" - "dO Drivers 2" - "dO Over The Net Install"
7. On the NINSTALL share, rename lmsetup.exe to lmsetup.xxx, and
setup.exe to setup.xxx so they will not inadvertently be used when
attempting to install from the workstation. nsetup is the
appropriate utility for installing workstations over the network.The NINSTALL share is now ready for network installation of the
LAN Manager 2.2 DOS workstation. For information on how to do over-the-
net installation, refer again to Chapter 5 of the LAN Manager
Installation and Configuration Guide.