Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

exchange 2013 receive connector reject

Posted on 2015-01-01
3
Medium Priority
?
169 Views
Last Modified: 2015-01-07
Hi.
I am getting the following warning in my exchange 2013 error logs:

Receive connector Internet Connector HFC-EKHAT rejected an incoming
connection from IP address 1xx.2xx.1xx.1xx.
The maximum number of connections per source (20)
for this connector has been reached by this source IP address.


This appears constantly in the logs.  This is incoming from a country that we don't usually send or receive mails from often.

Is this normal or could this point to something more sinister?

Thanks.
0
Comment
Question by:fijiboy
  • 2
3 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40527028
Sounds like someone is trying to perform some sort of denial of service attack. It sounds like Exchange is your first hop. Do you have any kind of message hygiene software, appliance or cloud service in front of your Exchange server? If not, I'd recommend it.
0
 

Author Comment

by:fijiboy
ID: 40527123
Thanks Gareth. We currently do not have a service in front of our email server apart from our corporate firewall. Am looking at some security for email security etc. Is there something I can do hardware the server in the meanwhile? They seem to be connecting on port 25.
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 2000 total points
ID: 40527249
A temporary solution may be to block that IP at your firewall. But they will often change IPs so this is a temporary solution at best.

If you have the Edge Transport role in your environment you could also do an IP Block List Provider - might help.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

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

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
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…
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…
Suggested Courses

824 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