Technical article 112441

Some of my users can log on to AFPS and others can't.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

Some users aren't being authenticated when they try to log on to an AFPS server.

Cause

There are a number of potential causes.  Items to check for are:
1. Is AFPS running?
Use "ps -ef | grep lmx" to check to make sure that there
are lmx processes running.
2. Are any AFPS Services running?

Use "net start" to see what services are running.

3. Are any problems reported in the Event Viewer?

Use "/usr/net/servers/lanman/bin/elfread -d system | pg"

Problems detailed in the Event Viewer can be searched on from Microsoft's Knowledge Base web page:

http://search.support.microsoft.com/

4. Have the ACL files or SAM Databases become corrupted?

Use the following commands:
net stop server   (This will stop AFPS)
acladm            (To check the ACL/Permissions file)
samcheck -rv      (To repair the SAM Database)
samcheck -a       (To check for corruption, pipe through pg)
net start server

NOTE: acladm and samcheck are found in /usr/net/servers/lanman/bin Before running these commands, ensure that Support Level Supplement (SLS) APP606A, the Advanced File and Print Server 3.5.2n Supplement is installed.

5. If this server is a BDC, then it's possible that the PDC is not being seen correctly.

You may wish to restart the PDC.  Check the /etc/hosts and
/etc/lmhosts files.

If DNS or WINS (NetBIOS Name Resolution) is used, check the DNS entries, WINS entries, and/or Windows LMHOSTS file, which can be imported into the WINS database, for corruption and to ensure that the name and IP address are correct.

6. The most likely cause of SAM corruption is due to poor network performance or a fault on the line. It may be necessary to perform a network check.

Solution

In order to recover from a corrupted SAM the best approach is to
remove and re-add the AFPS chain with netconfig.  A new copy of
the SAM will get transferred to this server automatically from
the PDC (Primary Domain Controller), so you must ensure that
this server is a BDC (Backup Domain Controller) otherwise your
User Database will need to be re-created.

If you do this, your ACL or permissions database will get removed, so be sure to make a back up first. To do this, take these steps:

1. Type: "net stop server".

2. Take a copy of these files prior to running netconfig:

/usr/net/servers/lanman/lanman.ini
/usr/net/servers/lanman/sharefile
/usr/net/servers/lanman/datafiles/acl
/usr/net/servers/lanman/datafiles/Name
/usr/net/servers/lanman/datafiles/LongName
/usr/net/servers/lanman/datafiles/ShortName
/usr/net/servers/lanman/datafiles/chlog.lmx

3. Run "netconfig" and remove the AFPS chain.

4. On the PDC, use the Server Manager tool from:

Start | Administration Tools (Common) | Server Manager
to remove the server from the server list.  Reboot the PDC,
when appropriate, to ensure the Master Browser list is updated.

5. On the OpenServer server, run "netconfig" and re-add the AFPS chain. This will give the server a new SID on the PDC.

6. Type: net stop server

7. Copy the files, above, back to their original location, to put back the original lanman.ini changes, the server's shares and the server's permissions for files residing on the server.

8. Type: net start server
NOTE:     Alternate commands to this are available, in
          /usr/net/servers/lanman/bin:
getrole -drp    (Tells you the domain, role and PDC of this server.
setdomain       (Tool to change the domain this server is in)
setdomainname   (For PDC's to change the Domain Name)
setservername   (Change the name of this server here and on the PDC).
joindomain      (For AFPS 4.0.2, re-specify the AFPS config for
                this server.  Will also remove and re-add the
                entry for the Computer Name on the PDC)

After running the commands, check to make sure the change has been successful, using these commands:

net logon                       Can you log on as Administrator?
net status                      Has AFPS started successfully?
elfread -d system | pg          Read the Event Viewer
samcheck -a | grep <user_name>  Check the SAM Database on this server
net user <user_name>            Check the existence of this user in
                                the domain

See also

ta100037, "What is the "lmhosts" facility and how is it used?"

ta100041, "My AFPS server does not respond for large numbers of '/etc/lmhosts' entries."

ta110526, "What is SLS APP606A, the Advanced Server 3.5.2 Supplement?" or go to: https://ftp.scoexpert.com/SLS

The AFPS Online Manual available from:
http://<Your Server Name>:457/asuhome.html

From the Xinuos technical article database, record 112441. Reproduced with permission. The original is at www.sco.com/ta/112441, 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.