SMS: SMSCliToknAcct Connection Attempts to Mapped Drives in Path

ID: Q239590

The information in this article applies to:

Microsoft Systems Management Server version 2.0

SYMPTOMS

If your path contains network drives and you have a Novell NetWare redirector installed (either Microsoft Client Services for NetWare (CSNW) or Novell intraNetWare Client version 4.5 or earlier), you may experience connection attempts to those network drives using SMSCliToknAcct. These connection attempts can lead to SMSCliToknAcct being locked out if an account lockout policy is enabled for the domain.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

NOTE: This hotfix only addresses the problem if you have Microsoft CSNW installed. To resolve this problem if you have Novell IntraNetWare client installed, upgrade to the latest version of the redirector.

The English-language version of this fix should have the following file attributes or later:


   Date      Time                 Size      File name    Platform
   --------------------------------------------------------------

   8/6/99   2:53pm              201,056   Bindcli9.dll   Intel 
   8/6/99   2:53pm              256,864   Bindclin.dll   Intel
   8/6/99   2:53pm              254,304   Bindsvrn.dll   Intel
   8/6/99   2:54pm            1,325,294    Ccmcore.exe   Intel
   8/6/99   2:54pm            3,210,567    Clicore.exe   Intel
   8/6/99   2:53pm              206,176    Ndscli9.dll   Intel
   8/6/99   2:53pm              266,592    Ndsclin.dll   Intel
   8/6/99   2:53pm              264,544    Ndssvrn.dll   Intel
   7/29/99  6:46pm              336,736   Mslmclin.dll   Intel
   8/6/99   2:49pm                   69    Compver.ini

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

WORKAROUND

To work around this problem, remove all network drives from the path.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

MORE INFORMATION

To install the hotfix, perform the following steps at the Systems Management Server site server:

Stop the SMS_EXECUTIVE and the SMS_SITE_COMPONENT_MANAGER services.

Replace the Ccmcore.exe file in the SMS_root\Inboxes\Clicomp.src\Base\i386 folder with the version obtained from the hotfix.

Replace the Clicore.exe file in the SMS_root\Inboxes\Clicomp.src\Base\i386 folder with the version obtained from the hotfix.

Replace the Compver.ini file in the SMS_root\Inboxes\Clicomp.src\Base folder with the version obtained from the hotfix.

Replace the Bindsvrn.dll file in the SMS_root\Bin\i386 folder with the version obtained from the hotfix.

Replace the Ndssvrn.dll file in the SMS_root\Bin\i386 folder with the version obtained from the hotfix.

Replace the Mslmclin.dll file in the SMS_root\Bin\i386 folder with the version obtained from the hotfix.

Start the SMS_EXECUTIVE and the SMS_SITE_COMPONENT_MANAGER services.

NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfixed files to be propagated to the clients. To speed up this process, you can stop and restart the SMS Client Service on each client. You can also create a software distribution for one of the Resource Kit tools Setevnt.exe or Cliutils.exe along with the appropriate parameter(s) to start a CCIM work cycle. For information on the proper syntax to use with these tools, see the Resource Kit documentation.

Additional query words: prodsms novel

Keywords : kbSMS120 kbSMS120bug
Version : winnt:2.0
Platform : winnt
Issue type : kbbug