Advanced File and Print Server Quick Start Guide

Solutions to common problems

The most common Advanced Server problems are described in the following sections:

If your problem is not listed here, see SCO Advanced Server Administration Guide, Chapter 6, Troubleshooting.

Installation problems

Advanced Server is not installed

No networking protocol

Advanced Server configuration will fail at the end of installation if there is no network adapter or NetBIOS transport configured.

Advanced Server will not install and run successfully until TCP/IP NetBIOS is correctly installed and running. To correct this problem:

install, configure, and test the TCP/IP NetBIOS
reconfigure Advanced Server using the joindomain command

See the UnixWare documentation and NetBIOS online help for information about configuring TCP/IP and NetBIOS.

VisionFS incompatible

If VisionFS is installed on the server, the Advanced Server initialisation may not succeed.

Advanced Server uses the kernel resident NetBIOS transport included with the SCO UnixWare operating system whereas VisionFS provides its own NetBIOS transport. Both NetBIOS implementations attempt to attach to the same TCP/IP ports and this causes a conflict that results in either the TCP/IP NetBIOS or VisionFS failing to start.

To resolve this conflict, it is recommended that you remove VisionFS from the system before installing the TCP/IP NetBIOS package.

Installing backup servers

A PDC running Advanced Server or NT must be functional on the network for the installation of a backup server to succeed. Check the following:

Verify that the PDC is running properly by logging on to the domain from a workstation, or using the net start or net status commands on the UNIX server. If the server is not running see "Server problems".
If the primary and backup servers are separated by a router, you will need to configure the NetBIOS on both servers to use either WINS or /etc/lmhosts. If you do not already have a WINS service on the network, you will need to start the WINS service on one of the servers. The Advanced Server WINS service is started using the command net start wins. Alternatively, you can provide an /etc/lmhosts file on each server with the other server names, IP addresses, and domain name. The following is a example of an /etc/lmhosts file:
```
   134.148.205.67  sales           #DOM:chicago
   134.148.206.33  marketing       #DOM:chicago
```
If the server appears to be running but the output of net start does not show the NETLOGON service, it is likely that incorrect information was provided during the server installation. Use the joindomain command to reconfigure the server, taking care to enter the correct domain name, server role (backup) and administrator account password (must match administrator account password used on the PDC).

Server problems

To troubleshoot server problems, follow these steps:

Check the status of the server.
Determine the status of the network.
Look for other possible problems that may affect Advanced Server operation.

Server status

Verify that the server has been started:

   net start server

If the server is running, this command should display a message similar to the following:

  These Advanced Server for UNIX Systems services are started:
  BROWSER                  EVENTLOG                 NETLOGON                 
  ALERTER                  SERVER

Check the Advanced Server processes:

   ps -ef | grep lmx

By default, the following lmx processes should be running:

   lmx.ctrl
   lmx.srv -s 1
   lmx.dmn
   lmx.browser
   lmx.alerter

If the server did not start, check the networking protocols.

Network protocol status

The most common reason that Advanced Server will not start is that the underlying network protocols are not running.

Verify that NetBIOS is running:

   /etc/netbios start

If the NetBIOS is running, this command will display a message to that effect.

Check that /usr/sbin/in.nbd is running using

   ps -ef | grep in.nbd

If NetBIOS is not running, check TCP/IP and other possible causes.

If NetBIOS is running, check that the NetBIOS can reach the network using the command:

   nbtstat -a Workstation_name

where Workstation_name is the name of a Windows workstation (or server) known to be fully operational on the same IP subnet.

If it fails, there is a problem with the TCP/IP or NetBIOS configuration.

View /etc/inet/nb.conf and make sure the NB_ADDR and NB_SCOPE entries are correct for your system. Normally these parameters do not need to be changed from the following default definitions:

   NB_ADDR=
   NB_SCOPE=

Refer to the UnixWare Networking documentation for assistance with troubleshooting TCP/IP.

Other possible causes

When the Advanced Server starts, it broadcasts its name to the network so other machines will know of its existence. If another machine on the network has the same name, then Advanced Server will not start.

The best way to determine if there is an outside influence is to temporarily disconnect the Advanced Server machine from the network and then try starting the Advanced Server again. If it starts up correctly, then there is probably another machine on the network with the same name and the conflict must be resolved.

If Advanced Server still does not start, then it is a local problem. Check the following:

Startup errors
Run net start server to try to start the AFPS server. If the command fails, make a note of the error number and run the command net helpmsg [number] to get the full error message.
Error log
The log of all Advanced Server errors can be read with:
```
   /var/opt/lanman/bin/elfread -d system | more
```
This will display a list of any error messages that were generated when Advanced Server attempted to start. The messages are displayed with the most recent messages appearing first. Make sure to check the time stamps for the relevant messages to be sure that they do not relate to earlier server activity.

Connection problems

License limits

If a client is unable to connect to server resources, verify that Advanced Server is licensed to allow the number of attempted connections. To display information about the current state of license usage, use the command:

  /var/opt/lanman/bin/lmstat -n | grep clients

This command will result in a display similar to the following:

  max clients:             5
  clients                  3
  maxclients exceeded      1

The max clients value is the number of simultaneous client connections allowed by the server. This value matches the number of connections allowed for by the Advanced Server licenses applied to the system. The clients value shows the number of current client connections and the maxclients exceeded value shows the number of attempts made to connected to the server when the license limit has been reached.

If the value of max clients is 1, the server has not been licensed and is currently running with a single user evaluation license. You need to run the UnixWare license manager and provide details of the 5-user base license and any additional client licenses that have been purchased.

For further information on applying licenses, see "Licensing the server" in the SCO Advanced Server Installation and Release Notes.

Unable to log onto the network

When a workstation user sees a error message when attempting to log onto the network, check the following:

Verify that Advanced Server is running.
Check that the Advanced Server user account exists with net user.
Verify that the password is correct by resetting the password with net password.
Check the transport protocol. Check TCP/IP using ping from both UNIX and the workstation.
If ping is successful, check NetBIOS with the command:
```
  nbtstat -a server_name
```
from the workstation, and the command:
```
  nbtstat -a workstation_name
```
from the server.
Check the workstation configuration. Make sure to restart the workstation after making changes to the networking configuration.
If the workstation is separated from the server by a router or a dial-up connection, see the SCO Advanced Server Administration Guide, Chapter 5, Implementing WINS for details on using the WINS service.

Problems with administrative tools

UNIX commands not found

The Advanced Server administrative commands are installed into the directory /var/opt/lanman/bin. If an error message is returned that an Advanced Server command is not found, verify that the directory contains the command and that the PATH variable includes /var/opt/lanman/bin.

Unable to set file/directory permissions

After installing the Windows NT Server Tools on a Windows 95 workstation, performing a mouse right button click on a file or directory icon and selecting Properties from the pop-up menu will display a Window with a new tab labelled Security. Selecting this tab provides a display of buttons labelled Permissions, Auditing and Ownership. If clicking on these buttons has no effect, check the PATH variable in AUTOEXEC.BAT. It must include C:\SRVTOOLS before these buttons will operate correctly.

See the SCO Advanced Server Administration Guide Chapter 3, Installing Network and Administrative Client Software, for complete installation instructions.

Browsing problems

Advanced Server systems not listed

If Advanced Server systems are not displayed in the browse list of a workstation, check the following:

If the workstation is separated from a server by a router or a dial-up link, the workstation must be configured to use either LMHOSTS or WINS to resolve the name of the server. DNS can be used to resolve the name of a specified server but, unless the domain name is aliased to a server IP address, the workstation will be unable to logon to the domain or browse the network.

It is recommended that the WINS service is used in routed IP networks. See SCO Advanced Server Administration Guide, Chapter 5, Implementing WINS, for details on starting the Advanced Server WINS service. You will also need to configure the workstations to use the WINS service.

If a WINS service is not available, the workstation will need to be provided with an LMHOSTS file that contains the following entries:

  IP_address  PDC_name  #DOM:domain_name #PRE
  IP_address  "DOMAIN_NAME[spaces]\0x1c" #PRE
  IP address  "DOMAIN_NAME[spaces]\0x1b" #PRE

where IP_address is the IP address of a primary domain controller PDC_name of the domain domain_name. DOMAIN_NAME is the domain name, in upper case letters, and [spaces] is the number of space characters that make up a total of 15 characters including the domain name. The \0x1c and \0x1b values identify the PDC NETLOGON and BROWSER services respectively.

For example, for a PDC called PRIMARY in the domain COMPANY with the IP address 123.123.123.123, the LMHOSTS entries appear as follows:

  123.123.123.123  primary   #DOM:company  #PRE
  123.123.123.123  "COMPANY        \0x1c"  #PRE
  123.123.123.123  "COMPANY        \0x1b"  #PRE

Printer problems

Cannot share a UNIX printer

If a message is displayed that a device is already in use when trying to create a printer share, check the share name.

The share name cannot be the same as the UNIX printer name. Printer share names are not case-sensitive, so using the command net share APPLE=apple /print would produce an error message.

Consider using a naming convention such as sh_UNIXprinter.

Permission problems

Cannot access resource

Check the access permissions associated with the share using the command:

  net perms \\Share_name

To access the share, the user must have access permissions for that share either by making the share available to Everyone or by including the user, or group to which the user belongs, in the access control list.

Cannot access file/directory

Check the permissions associated with the file/directory using the command:

  net perms c:/Path

where Path is the full path to the file or directory.

To access the file/directory, the user must have access permissions for that file/directory either by making the file/directory available to Everyone or by including the user, or group to which the user belongs, in the access control list.

NOTE: Unless set explicitly using net perms or the Windows file properties menu, access permissions associated with a file/directory will be derived from the parent directory. If no access permissions have been set, the access permissions associated with the top level shared directory will apply to the full directory structure beneath that shared directory.

No longer able to access resources

If a user is unable to connect to shared resources, verify that the Advanced Server user account is mapped to a valid UNIX user account. If the mapped UNIX account has been deleted, the Advanced Server user will not have access to file and directories on the UNIX system.

If the UNIX account no longer exists, create a new UNIX account and map that user account to the Advanced Server user account using mapuname.

If the Advanced Server user account is deleted and recreated, access permissions which existed for that user prior to deletion will not be valid after the account is recreated. This applies even if the same user account name is used. Access permissions on shares, files and directories must be redefined for the new account.

See "Mapping User Accounts to the UNIX System" in the SCO Advanced Server Concepts and Planning Guide, Chapter 3, Working with User and Group Accounts.