Like many people we have hit up against the 32 MAPI sessions limit for a single user in Exchange. There are a number of solutions that have been proposed, ranging from increasing the number of allowed sessions, to sorting out the "TCP Chimney" problem.However, I don't understand why there is no way to simply kill of stale MAPI sessions. We are getting this problem for people on intermittent internet connections in the developing world - the VPN connection drops, then reconnects, and the user gets a new session. Some of the sessions that are listed in Exchange System Manager have been stale for almost a month.Does anyone know a way of manually ending these sessions? Or some way of having them time out after a certain period of activity? Is the only way rebooting our mail servers?Cheers,Duncan

I have doubt on ending up sessions manually but you can check James' response on reducing value of "KeepAliveTime" registry to end up session earlier... http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/ccd10104-8613-402b-90ab-9ffdcea03977Amit Tank | MVP Exchange Server | MCITP: EMA, MCSA: M | http://ExchangeShare.WordPress.com

Hello,I do not recommend to hack the registry... however i would like to you to implement this patch to your server if you're facing this issue.An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computershttp://support.microsoft.com/default.aspx/kb/948496Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

That patch is already in place on this server. Looking at the suggestions on this thread: http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/0e7283c6-9cf7-4923-8d0c-9996abd13c19