Knowledge Base

XCON: Messages In RAS Connector Queue NDR when Modem is Busy

Article ID: 152666

Article Last Modified on 10/28/2006

Microsoft Exchange Server 4.0 Standard Edition
Microsoft Exchange Server 5.0 Standard Edition
Microsoft Exchange Server 5.5 Standard Edition

This article was previously published under Q152666

SYMPTOMS

When you send a message over the Microsoft Exchange Dynamic Remote Access Service (RAS) Connector, you might receive a Non-Delivery Report (NDR) after a specific period of time. The NDR will look like this:

The following recipient(s) could not be reached:

'TO USER' on 6/14/96 1:35:13 PM
The recipient could not be processed due to congestion in the message transfer service
[MSEXCH:MSExchangeMTA:EXCHANGE:MAIL1]

This can happen if the modem on the RAS server is in use by another RAS connection.

WORKAROUND

There two ways to avoid this problem:

Schedule the Dynamic RAS Connector to dial out at predetermined time when the modem will be available.
Install another modem on the server. In the phone book entry for the Dynamic RAS connector, specify the new modem port or any available modem port.

MORE INFORMATION

The Microsoft Exchange Message Transfer Agent (MTA) will try to send the message over the current RAS connection and this will fail. It will keep trying until the retry value set on the MTA override page for the RAS Connector has been exhausted. At this time, the MTA will send an NDR to you. This is by design.

Additional query words: RAS NDR mta busy

Keywords: kbprb kbusage KB152666