Microsoft KB Archive/170056
Article ID: 170056
Article Last Modified on 4/28/2005
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q170056
Messages may back up on the Microsoft Exchange Server Message Transfer Agent (MTA) queues, and the following Event IDs will be written to the Windows NT Event Viewer Application log:
Event ID: 9318 Source: MSExchangeMTA Type: Warning Category: Interface Description An RPC communications error occurred. Unable to bind over RPC. The locality table (LTAB) index is 76. Windows NT error code: 1722. [BASE IL MAIN BASE 1 500] (12) Event ID: 9215 Source: MSExchangeMTA Type: Warning Category: Operating System A sockets error 10061 on a connect() call was detected. The MTA will attempt to recover the sockets connection. Control block index: 1. [BASE IL TCP/IP DRVR 8 274] (12)
The above errors indicate that the server that the messages are destined for is either down or cannot be reached on the network.
Things to check for:
- Try to ping the other server by both IP address and Servername.
- Try to do a NET VIEW \\Servername to verify NetBios name resolution.
- Try to do a NET USE \\Servername\IPC$ to verify rights issues.
If steps 1 and 2 fail, the problem is one of basic network connectivity. Check the IP address and the WINS/DNS/HOSTS files.
If step 3 fails, check the Windows NT access rights for the Exchange Service Account being used.
Note: If you are running DHCP on your server, you should run IPCONFIG /RELEASE and IPCONFIG /RENEW.
In the 9318 RPC error message, the Windows NT error code 1722 indicates that the RPC server is unavailable.
In the 9215 error, the sockets 10061 message indicates that the connection was refused.
This behavior is by product design.
Additional query words: exfaq
Keywords: kbprb KB170056