Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Error 450 sending internal mail

Posted on 2016-11-21
6
Medium Priority
?
53 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:jmac44
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 16

Accepted Solution

by:
Jason Crawford earned 1000 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
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 16

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:jmac44
jmac44 earned 1000 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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
In this video we show how to create an Accepted Domain 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 >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

664 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