Solved

Error 450 sending internal mail

Posted on 2016-11-21
6
41 Views
Last Modified: 2016-11-29
Exchange 2010 SP3 RU15, single CAS, 2 DAGs. Receive connector configured to receive internal messages from our voicemail server to relay to the internal users mailbox who received a voicemail. Connector had been working up until about 2 weeks ago.

When attempting to send a message via telnet from the voicemail server I receive a message at the RCPT TO stage stating "450 too many connections from your IP (rate controlled)"

The connector had the MaxInboundConnectionPerSource orignally set at 50, changed to 500, restarted the Transport Services service and the issue still persists.

No recent changes made to the network or the servers. Any ideas where to look next?
0
Comment
Question by:Lee James
[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
  • 2
  • 2
  • 2
6 Comments
 
LVL 9

Expert Comment

by:Justin Moore
ID: 41896267
Try restarting the "System Attendant" if that doesn't try the "Information Store". The second one will briefly disconnect everyone for the period of the restart. If those two don't work you know you your limits need to be changed elsewhere.
0
 
LVL 15

Accepted Solution

by:
Jason Crawford earned 250 total points
ID: 41896278
That doesn't look like an error generated by an Exchange server.  I know you said it was internal, but do you have a firewall or spam filtering appliance in between the voicemail appliance and the end user?
0
 

Author Comment

by:Lee James
ID: 41896297
There are no firewalls or spam filtering appliances in between. Restarting the services will have to wait until after hours later this evening.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 15

Expert Comment

by:Jason Crawford
ID: 41896318
If  you haven't already done so, enable verbose logging on all Receive Connectors:

Get-ReceiveConnector | Set-ReceiveConnector -ProtocolLoggingLevel Verbose

Open in new window


After enabling verbose logging, send another email via the voicemail appliance.  Give it a few minutes and check the most recent SMTPReceive log located here - C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive.  Open the .log file and search for the recipient address.
0
 
LVL 9

Assisted Solution

by:Justin Moore
Justin Moore earned 250 total points
ID: 41896385
I think Jason's right, 450 is not an Exchange error but a Telnet error your seeing. Telnet is quirky at best. Sometimes just hitting the backspace key can cause a failure. I would be cautious when going down that path to focus on the 450 error. you may end up troubleshooting two different problems. The fact that the voicemail stuff was working and then stopped means that MaxInboundConnectionPerSource isn't the issue either. I would check and make sure you don't have a hung service and I would check your logs and make sure you don't have a DNS issue somewhere. A lot of times we make small minute changes that don't seem relevant and we forget about or even MS Updates can snowball into unseen issues.
1
 

Author Closing Comment

by:Lee James
ID: 41905650
Routing issue was the root cause. Thanks for the assistance.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

710 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