Microsoft KB Archive/213063

= SMS: NW_Logon_Server_Manager Unable to Connect to Bindery Server After Bindery Server Is Renamed =

Article ID: 213063

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



This article was previously published under Q213063



SYMPTOMS
NW_Logon_Server_Manager is unable to connect to a bindery server after the bindery server is renamed.



CAUSE
Once the bindery server is renamed, the redirector still caches the old server name to allow current user connections to continue. However, new connections fail because the SMS site attempts subsequent connections using the new bindery server name. As a result, Systems Management Server is unable to connect to the bindery server CAP and logon point until a reboot of the site server occurs. The reboot of the server allows the redirector cache to clear, allowing successful connection.



WORKAROUND
The following steps outline the recommended procedure for changing the name of a NetWare resource that is acting as an SMS Site System role:
 * 1) Delete the NetWare logon point and/or CAP from the SMS Administrator Console.
 * 2) Wait until the logon point and CAP are removed from the bindery server.
 * 3) Rename the bindery server.
 * 4) Restart the SMS Site server.
 * 5) Create new a logon point and CAP using the new server name.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Additional query words: prodsms

Keywords: kbbindery kbbug kbcap kbconfig kbinterop kbnetwork kbnofix kbosnovell kbserver kbsmsadmin KB213063

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.