Advanced File and Print Server Quick Start Guide

Frequently asked questions

The following sections includes some of the most commonly asked Advanced Server questions from SCO Technical Support library:

To access the complete library of Technical Support articles for Advanced Server see "SCO Support online".

Can a share be automatically mapped to a driver letter?

The "net use" command can be used on the client to map a drive letter to a share on the server. In order to manage this from the server, net commands may be added to a logon script that will be executed each time the user logs on.

Logon scripts are DOS batch files which must be created with a DOS or Windows text editor. They can contain DOS commands along with the "net" commands. Also, in order to be executable by the DOS command interpreter, the logon script must have the ".bat" extension, that is, logon.bat. For an OS/2 client, it must have the ".cmd" extension.

Finally, in order for the script to be executed, the client must be logging onto the domain. For a Windows 95 client, in My Computer->Control Panel->Network->Client Properties, there is a checkbox for "Log on to Windows NT domain". If this is not checked, or if the domain is incorrect, the script will not be executed. If there is more than one logon server on the network, the logon script must exist on all the servers that can validate the user logon request.

By default, the logon scripts are stored in the directory:

   /var/opt/lanman/shares/asu/repl/export/scripts

This path is determined by the value of the Export Path key in the Registry.

Once the script is in place, the account must be configured to use the script file. To configure the account from the UNIX command line, type:

   net user account_name /scriptpath:account_logon_script

NOTE: The script path is relative to the default logon script directory /var/opt/lanman/shares/asu/repl/export

The User Manager may also be used from a Windows workstation to set the logon script name.

The next time the user logs on to the network, the logon script will be run.

As an example, to have the share EDDIE on the server "payroll" automatically map to the U: drive on the client, use the script:

   NET USE U: \\PAYROLL\EDDIE

Why are files created with group ownership DOS----?

Files stored on the Advanced Server system can be viewed from both the UNIX and MS-DOS environments. The special UNIX groups are used to set MS-DOS file attributes when a workstation user creates a new file on the Advanced Server system:

   DOS----
   DOS-a--
   DOS--s-
   DOS---h
   DOS-as-
   DOS--sh
   DOS-a-h
   DOS-ash

Generally, an Advanced Server user will only log on to Advanced Server from a PC client. However, a user can also log into the UNIX operating system. In this case, a system administrator may want to ensure that any files created by this UNIX user have certain MS-DOS file attributes.

MS-DOS allows the following attributes to be set on a file:

   R - Read only file attribute
   A - Archive
   S - Sets file as a System file
   H - Set file as a Hidden File

These attributes may be viewed or set from within the MS-DOS/Windows operating system using the ATTRIB command.

Does Advanced Server have a debug mode?

Advanced Server has a limited debug feature built into the asuserver package. To activitate debugging mode:

Log in as the user root.
Stop the server with net stop server.
Edit the "[lmxserver]" section of the lanman.ini control file as follows:
```
   debug=yes
   debugsignal=yes
```
Change to the directory /var/opt lnaman/debug and remove any files named Debug-nnnnn.
Restart the server using net start server.

Debug files will written into the directory /var/opt/lanman/debug as Debug-nnnnn where nnnnn is the PID of the process being traced.

Use the kill -16 server_PID command to activate the debug trace. Once you have captured the relevant data, turn off debug with another kill -16 server_PID command.

To obtain more extensive diagnostic information, the asudebug package can be installed on top of the asuserver package.

CAUTION: This should only be done on the instruction of support as it will severely impact the performance of Advanced Server.

To enable the debug feature to examine a specific problem:

Stop the server using net stop server.

Install the asudebug package from the Advanced Server CD-ROM using the commands:

    mount -F cdfs -r /dev/cdrom/* /mnt
    pkgadd -d /mnt asudebug

Start the server using net start server.
Make sure the server is running using ps -ef | grep lmx. The following processes must be running:
```
   lmx.ctrl
   lmx.srv
   lmx.dmn
   lmx.browser
```
Recreate the conditions which cause the problem.
Stop the server using net stop server and save the contents of the directory /var/opt/lanman/debug. Retain the debug files for use by SCO Technical Support in diagnosing the problem.
Remove the asudebug package using the command:
```
    pkgrm asudebug.
```
Start the server using net start server. The server is now restored to its normal operational state.