Microsoft KB Archive/172003

From BetaArchive Wiki
Knowledge Base

Article ID: 172003

Article Last Modified on 11/1/2006


  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition

This article was previously published under Q172003


In a multiple master domain environment, initiating a change password from a Macintosh client without specifying the domain name may fail. The error report to the Macintosh client is:

Your password could not be changed.
Please try again or see your server administrator.


Change password requests initiated by a Macintosh client are forwarded to a computer running Windows NT Server and running Services for Macintosh. The server then initiates the change password request on behalf of the Macintosh user. When the user account name is received with no specified domain name, requests are sent to a list of trusted domain controllers (DCs) under the multiple master domain model. In this case, an unexpected error was returned from the change password request because a DC in the list of trusted DCs was down. Because of the unexpected error, the complete list of DCs was not processed.


The workaround is for users to specify the domain [domain_name\username] in password change requests.


The Services for Macintosh file, sfmsvc.exe, was modified to handle the unexpected error code that was encountered.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Additional query words: prodnt

Keywords: kbhotfixserver kbqfe kbbug kbfix kbinterop kbnetwork KB172003