http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url="">
This shows the setting that 'appears' to allow one to override the
limit of 64 connections. I recall seeing an article in the past from a
competing mail server vendor describing hot to tweak these settings for
optimal performance on a very high volume server. Maybe someone can
come up with that article.
Matt
Darin Cox wrote:
If you're having problems with sockets not being closed by the OS for
what seems like ages, try this Registry tweak:
HKLM_SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime
REG_DWORD 60000 ( = 1 minute)
Some, if not all, abnormally ended client connections should be
cleaned up by this setting. The default, before you added this
setting, was two hours.
Hi Sandy,
Very informative "lay of the land"...thanks.
On the reg tweak - if you have other services, like HTTP and FTP running, on
the same box wouldn't it cause their connections to be cleaned up as well?
HTTP shouldn't be that long, but with FTP, instead of having a 5 or 10
minute timeout by the FTP server, wouldn't this cause connections to be
dropped after 1 minute?
So for multi-function servers, perhaps a compromise of, say, 10 minutes?
Darin.
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
--
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================