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

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1278
  • Last Modified:

HUB Transport Error - Ex2010

Hi Team,

below is the error i am getting in Hubtransport server

“Receive connector Exchange Users rejected an incoming connection from IP address 203.134.205.XXX. The maximum number of connections per source (20) for this connector has been reached by this source IP address.”

i found the solution is as below.

The “MaxInboundConnectionPerSource” parameter specifies the maximum number of inbound connections that this Receive connector serves at the same time from a single IP address. The default value is 100. The valid input range for this parameter is from 1 through 10000.

here my question is  what this
“MaxInboundConnectionPerSource” ? why we require to increase the number ? what it is ?

looking foroword for your suggestions

AK Reddy
0
KBRaju
Asked:
KBRaju
  • 5
  • 4
1 Solution
 
Azhrei1Commented:
It means that one single user is creating a lot of connections to your server at once. This could indicate the user is running several instances of outlook by accident (as happens in Windows 7 sometimes using the 'new' taskbar). It could also be malicious software or other software faults.

I'd take a look at the workstation that has that IP and figure out why it is making so many connections to your exchange server.

If it seems legitimate, you can increase the number to allow more connections instead of blocking them.
0
 
KBRajuAuthor Commented:
Hi Azhre,

Tnank you for your support,


when i was running into this issue,  MAPI Services were running wihout issues.

i found dificulty only with POP and IMAP users, when i was restarted  servers, mailflow was normal.

but still i am seeing these kind of errors.

if i increase the  number what would be the impact.

is it the good sign to increase the number ?

or is there any  tools to check which user is running out of connections and all.

AK Reddy
0
 
Azhrei1Commented:
Ah, you mean this IP is not internal? Then it's a little harder to find out who it is...

In general, when this happens, one of your users should report that he/she is not getting email, for the others it should be fine, unless they are using the same IP? If you have a lot of users connecting from the same IP (maybe a second office?) then you definitely have to increase this number.

If it's one user per IP, you know which user is having issues and causing these multiple connections.

If you want to increase the number, I recommend running perfmon.msc first on the server, to check its performance. If the CPU/Memory and Disk are not too busy, you can safely increase it. Monitor again afterwards, it should have none or barely any impact on your server, perfmon is just a precaution.

There are probably some tools to check, but I only know those for Exchange 2003...if you find one or another expert knows of one I'd be interested too :)
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
KBRajuAuthor Commented:
wonderfull info,

as per my environment, we have around 1000 are in same platform, but on those  around 150 users were complained about this, that too who is using POP/IMAP.

can we disconnect the users who are using more resource on the server. what is the tool.
0
 
Azhrei1Commented:
are those 150 users in the same building? Or do they roam with phones or laptops?

I don't know how to disconnect those users as I don't know about any tools. It's probably possible to do that in powershell, but that's a lot of work. I'd recommend raising the number while keeping a good eye on performance.
0
 
KBRajuAuthor Commented:

they are located on some other place, and using POP/IMAP services.

and also they are using Blackberry mobiles for access emails. via BIS.

0
 
Azhrei1Commented:
ok, then you can't do much about their end, so you can only raise the number or reboot, or try to find a way to reset individual users. I don't know how to reset individual users, so I'd raise the number.
0
 
KBRajuAuthor Commented:
ya... it seems good idea.

Thanks for your support Azheri.

once i reaise the number will let you know, if there is any dificulties when i monitor the performance.

AK Reddy
0
 
KBRajuAuthor Commented:
good one
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now