We recently patched four NetWare 6.5 SP3 servers to NetWare 6.5 SP5.
After the updates, NWCONFIG.NLM was loaded on each servr to verify the
versions of certain products. On each server, when NWCONFIG was
launched, CIFS.NLM was autostarted. Now when, CIFSSTOP.NCF is launched,
the script starts, but fails to complete.

Below is an excerpt of the LOGGER.TXT file from one of the servers:
Module NWI.NLM load status OK

Module NWCONFIG.NLM load status OK

Loading module CIFS.NLM

CIFS Semantic Agent (Build 558 MP)

Version 3.24.01 March 15, 2006

Copyright 1987-2003 Novell, Inc. All Rights Reserved.



The share point "_ADMIN" is now active on volume _ADMIN.

The share point "SYS" is now active on volume SYS.

The share point "VOL1" is now active on volume VOL1.

The share point "VOL2" is now active on volume VOL2.

Module CIFS.NLM load status OK

Why does NWCONFIG think that it needs to launch CIFS?