Password Change Fails Using DNS to Resolve Names

 Last reviewed: April 11, 1997
Article ID: Q137554
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SUMMARY

When DNS is used to resolve names from Windows NT 3.5, the operation of changing a password may fail.

MORE INFORMATION

This problem occurs over TCP/IP because the client computer sending the request to resolve the name of the domain receives a response for the IP address of the PDC (Primary Domain Controller) from the DNS Server, but attempts to form a session with the PDC with the name of the domain as the destination instead of the name of the PDC. This results in a Negative Session Response from the primary domain controller with status Caller Name Not Found.

Under Windows NT 3.51, the three way-handshake and session setup are preceded by a NetBT request from the client computer for registered services on the PDC. Upon receiving the response, the client correctly establishes a session to the PDC with the PDCs machine name as the destination.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in Windows NT 3.51.

Additional query words: prodnt unable change C00000E5 service
Keywords : kbbug3.50 kbfix3.51 kbnetwork ntconfig ntinterop ntnetserv nttcp
Version : 3.5 3.51
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.