Programs may not connect to the server with mismatched security DLLs in Windows NT 4.0
This article was previously published under Q322051 On This PageSYMPTOMS After you install the Microsoft Windows 2000 Security
Rollup Package (SRP), or if you use NTLM version 2 to connect to a Windows NT
4.0-based server with the SRP installed, your programs may not connect to the
server. If Microsoft Exchange Server 5.5 is installed on a computer that is running Windows NT 4.0 with the SRP installed, and you try to move a mailbox from this server to a server that is running Microsoft Exchange 2000 Server, the following error may also be logged:
Event Source: MSExchangeAdmin Also, mail flow could stop. One of the following events could be logged in the Application event Log on the server:Event Category: Move Mailbox Event ID: 1008 Description: Unable to move mailbox. Error: Could not bind to the Microsoft Exchange Directory server. The Microsoft Exchange Server does not respond. Event Type: Warning Event Source: MSExchangeMTA Event Category: Interface Event ID: 9318 Description: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 4, NT/MTA error code: 5. Comms error 5, Bind error 0, Remote Server Name xxxx [MAIN BASE 1 500 %10] (14) Event Type: Warning Event Source: MSExchangeMTA Event Category: Interface Event ID: 9322 Description: An interface error has occurred. An MtaBindBack over RPC has failed. Locality Table (LTAB) index: 13, NT/MTA error code: 5. Comms error 5, Bind error 0, Remote Server Name xxxx , Protocol String ncacn_ip_tcp:16.37.164.181[4749] [BASE IL INCOMING RPC 23 507] (14) CAUSEThis behavior may occur if you install the SRP on Windows NT
4.0 with the 56-bit version of Service Pack 6a (SP6a) and Microsoft Internet
Explorer 6, because the following mismatched dynamic-link libraries (DLLs) may
be installed:
RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesTo apply this hotfix, you must have Microsoft Windows NT 4.0 Service Pack 6a installed.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Size File name Platform ----------------------------------------------------------- 16-Jul-2001 12:05 36,112 Ntlmssps.dll I386 - 128-bit (SRP) 23-Sep-1999 11:04 59,152 Security.dll I386 - 128-bit (SP6a) 16-Jul-2001 12:05 36,112 Ntlmssps.dll I386 - 56-bit (SRP) 18-Nov-1999 12:04 59,152 Security.dll I386 - 56-bit (SP6a) WORKAROUND To work around this problem, install the hotfix that is
mentioned in the "Resolution" section. This upgrades the computer to 128-bit
security. If you must use the 56-bit versions of the DLLs in Windows NT 4.0, you can manually replace the Schannel.dll and Ntlmssps.dll files with the 56-bit versions from the SRP:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION This problem may occur with Microsoft Exchange 5.5
administrative programs connecting to Exchange 5.5-based servers. This causes
the following error message: DS_E_COMMUNICATIONS_PROBLEM
When you join a Microsoft Exchange 2000 server to a Microsoft
Exchange Server 5.5 site, you may receive the following error message: Error code 0XC103FC93 (64659): Could not bind to the Microsoft
Exchange Directory server EXCHANGE1. The Microsoft Exchange Server
computer does not respond.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
311401 (http://support.microsoft.com/kb/311401/)
Windows 2000 Security Rollup Package 1 (SR), January 2002
For more information about how to install multiple hotfixes while restarting only one time, click the following article number to view the article in the Microsoft Knowledge Base:
296861 (http://support.microsoft.com/kb/296861/)
How to install multiple Windows updates or hotfixes with only one reboot
APPLIES TO
| Article Translations
|
Back to the top
