Re: Too many simultaneous connections - but in reality it's different. [message #145470 is a reply to message #145436] |
Mon, 08 April 2019 16:53   |
Maerad
Messages: 275 Registered: August 2013
|
|
|
|
First of all, you can change the settings in the admin GUI. Services > click a service > access > max. number of concurrent connections.
Also check if you have the ip address groups right (all local IP's) and if under SMTP SErver > Security Options those are excliuded "do not apply to ip address group".
Otherwise, instead of trying something, enable additonal debug logs and check the security log, to find the reason WHY the client(s) was/were banned or how many connection trys are there.
You can see how many connections are open in Status > Active connections.
Also the thing that shouldn't happen is a block because of too many http connections. I have disabled the http service and do a url rewrite with IIS to the https site. IMHO there shouldn't be HTTP open in any case. Or at least turn to requite encrypted connection on under the security tab (Security Policy).
If there are over 1k open HTTP concurrent connections, somethings not right.
|
|
|