Solved

Internal Server not able to send email after changing which HubTransport server to use

Posted on 2013-05-16
1
216 Views
Last Modified: 2013-05-22
We have several servers that send SMTP email internally. These emails are typically server status notices after a process is complete.
To prep for some DR tests, I changed the Exchange HubTransport server used to receive the emails into Exchange.
I double and triple checked both of the HubTransport servers had the exact same Receive connector.

After the change of the HubTransport server, mail flowed properly and I could see in the header that the new HubTransport server was used for a majority (more than 10) of the servers sending emails.

But we had 4 servers that received "5.7.1 Client was not Authenticated" and the mail did not flow.

Since this was during the day and it was hours after the change with still no mail flow on these problem servers, we had to change the HubTransport server BACK to the original one. When we did this 3 of them still did not work. We got a brainstorm and did a DNS Flush on the problem servers which corrected the issue.

With this information, we feel that we can put the new HubTransport server change back in and be prepared to just Flush the DNS on the problem servers and result in the email flowing from these servers.

Is anything I may have missed? If the Receive connector is the same on both HubTransport servers is there anything else that could have caused this issue?

This is an Exchange 2007 server environment on Win 2008 boxes.

Thank you,
0
Comment
Question by:swfwmd2
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39174441
Are you sure the connectors are 100% identical, because from the error you have posted it would appear not.

run

get-receiveconnector | fl and then compare the output.

How are you controlling the server they use? DNS entry? If so, turn the TTL time down, so any changes are effective quickly. Running it with a 10 or 15 minute TTL internally wouldn't cause a problem.

Simon.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create a Contact 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 Recipients >> Contact ta…
To show how to create a transport rule 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 Mail Flow >> Rules tab.:  To cr…

705 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