Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Exchange SMTP connector AUTH rejection

Posted on 2006-05-25
Medium Priority
Last Modified: 2010-05-18
This seems a little odd.

In SBS20003, the SMTP connector has been told to forward email via another server (linux box)
The outbound security is set to basic auth with the correct user name and password set.

The queue status information on this connector states "The remote SMTP service rejected the AUTH negotiation".   I know that normally means the user name or password is not set correctly.  I KNOW the user name and password is set correctly, because I have set additional debug information in the linux mail log that shows me both the connection coming in, along with the username and password being used and confirms that the connection has been accepted.

Yet the Exchange connector still insists that the AUTH negotiation was rejected.

Two questions:
1. Could exchange be incorrectly reporting this error.
2. Is there further debugging information available in the SBS2003  box that may allow me to see more detail of the connection from the Windows end.

There may be a clue in the error message - the NEGOTIATION was rejected rather than password.  Don't know how fine grained the connector reporting would be.


Question by:sheepfarmer
  • 3

Author Comment

ID: 16760723
Did some more testing on this.

- I deleted the SMTP connector
- Recreated SMTP connector
- Changed the SMTP account password on the linux box
- Added Basic auth name and password on SMTP connector
- Send some email from SBS2003 and it worked
- Noted SMTP queue was now empty
- Sent some more email from SBS2003
- This time the queue showed the connector had failed again with AUTH error.
* So, the last email was send through a working connector, but failed.

- Changed SMTP connector to use anonymous SMTP
- Forced queue
- Failed (expected)
- changed SMTP connector to use name/password AUTH
- forced queue - this time the email was sent.

Very confusing!


LVL 27

Accepted Solution

Exchange_Admin earned 1200 total points
ID: 16761042
Just a wild stab in the dark here, but could the issue be on your linux box?
Something like maybe it limits the number of emails it will accept during a given time?

Author Comment

ID: 16764724
I did think about and checked beforehand - there is a limit on the number of concurrent connections in from a specific IP address, but the limit is 6 and in the tests above, there was only one email (therefore connection required).

Is there a way to force Exchange to queue emails to only use one SMTP pipe to rule out that possibility.
LVL 104

Assisted Solution

Sembee earned 800 total points
ID: 16773081
Using an SMTP Connector with a smart host configured means that all the email goes down the same connection. Instead of the server looking up each domain, it just sends it to the host listed in the connector.

I was wondering if something was interfering in the SMTP traffic - which would explain the failure message.


Author Comment

ID: 16774622
Having done some more research, my current view is that it could indeed be the Linux box causing blocking or throttle restriction.  I am hoping that someone can throw some light on this http://www.experts-exchange.com/Operating_Systems/Linux/Linux_Administration/Q_21864821.html and I'll report back.


Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question