FIX: Windows 2000 services cannot access some network resources

This article was previously published under Q266066
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When the Service Control Manager (SCM) starts a service under a specific user account, it must initiate a logon session for the user. In Windows 2000, the SCM does not notify credential managers and network providers of this new logon session. As a result, Win32 APIs that attempt to access a network resource, such as a printer or share, may fail with error 53 (ERROR_BAD_NETPATH) or error 68 (ERROR_INVALID_PASSWORD).

This problem will affect any service that relies on the network provider to supply credentials when connecting to a remote resource. For example, Microsoft's Gateway Services for NetWare and Novell's NetWare client experience this problem when accessed through a service that is running under a specific user account.
WORKAROUND
To work around this problem, the service can explicitly cause the credential managers and network providers to receive a logon notification by calling WNetAddConnection2 or WNetAddConnection3. These APIs require the user credentials (username and password). Note that the developer of the service should implement appropriate security measures to protect the user credentials from misuse. These include, but are not limited to, storing the password in a suitably encrypted form.
RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack

Hotfix information

The English version of this fix should have the following file attributes or later:
   Date        Time    Version         Size    File name   --------------------------------------------------------   09/29/2000   4:35p   5.0.2195.2394  83.7KB  services.exe   10/11/2000  11:13a   5.0.2195.2458  101KB   msv1_0.dll				
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 266066 - Last Review: 02/28/2014 04:19:21 - Revision: 5.1

  • Microsoft Win32 Application Programming Interface
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbkernbase kbscm kbservice KB266066
Feedback