Problem
When AFPS 3.5.2n starts the Event Viewer contains the error message:
"Error 2186: Service is not Responding to Control Function"
This error message has also been seen when trying to shut the AFPS server down with the command "net stop server".
Cause
There is likely to be some corruption in the AFPS SAM or "Blob" file. These files contain information passed to the server from the server's Primary Domain Controller (PDC). The corruption is normally caused by poor network response or a fault on the line and can be rectified by addressing the network issue first.
In order for the netlogon service to start this server, a Backup Domain Controller (BDC) must communicate with the server's PDC.
This operation can time out if the server does not respond quickly enough (within about 45 seconds). If this problem occurs, you will see a message similar to the following:
Could not start the NETLOGON service on \\<server>. Error 2186: The service is not responding to the control function.
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. Therefore, this must be backed up first.
The steps to take are:1. net stop server.If you are not able to run the command "net stop server", you can add "exit 0" to /etc/rc2.d/S95asusrv and re-boot the server so AFPS does not start.
2. Take a copy of the following 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.lmx3. Check to see if the ACL files or SAM Databases have become corrupted.
Use the following commands:acladm -CPv (To check and prune the ACL/Permissions file)
samcheck -rv (To repair the SAM Database)
samcheck -a (To check for corruption, pipe through pg)Please note: acladm and samcheck are found in /usr/net/servers/lanman/bin.
Before running these commands, ensure that APP606A, the Advanced File and Print Server 3.5.2n Supplement is installed.
Clear the Event Viewer of any corrupted entries from a Windows client.
If you had to modify the /etc/rc2.d/S95asusrv earlier, re-edit and remove the "exit 0" and either re-start the script with:
/etc/rc2.d/S95asusrv startor:re-boot your server.4. Run "netconfig" and remove the AFPS chain.
5. On the PDC, use the Server Manager tool from:
Start | Administration Tools (Common) | Server ManagerTo remove the server from the server list, re-boot the PDC,
when appropriate, to ensure the Master Browser list is updated.6. On the OpenServer server, run "netconfig" and re-add the AFPS
chain. This will give the server a new SID on the PDC.7. net stop server8. Copy the files listed 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.
9. net start serverAfter running the commands, check to ensure that the change has been successful with the commands:
net logon Can you log on as Administrator?net status Has AFPS started successfully?elfread -d system | pg Read the Event Viewersamcheck -a | grep <user_name> Check the SAM Database on this servernet user <user_name> Check the existence of this user in
the domainCheck printing from a client. If the printers no longer print,
re-create them using the script: SHARE_PRN="SP_TEST"
UNIX_PRN="pr_test"
DESC="Test Printer for Unix/AFPS"
if [ -d /usr/net/servers/lanman ]; then
echo "\nAdding Printer as the SHARE ${SHARE_PRN}
... "
net share ${SHARE_PRN}=${UNIX_PRN} /PRINT
net share ${SHARE_PRN} /REMARK:"${DESC}"
net print ${SHARE_PRN} /REMARK:"${DESC}"
net share | grep ${SHARE_PRN}
net access \\${SHARE_PRN}
echo "Done!"
else
echo "\nNon AFPS Server !"
fiNOTE: It can take a few minutes for the LSA Builtin and SAM database to
synchronize and you may get failure messages in the Event log
initially. 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."
ta112441, "Some of my users can log on to AFPS and others can't."
Support Level Supplement (SLS), APP606A, the Advanced File and Print Server 3.5.2n Supplement available from "https://ftp.scoexpert.com/SLS"
The AFPS On-Line Manual available from: http://<Your Server Name>:457/asuhome.html