If I remember correctly the 32 limit is for MAPI sessions per client. I have seen this happen when users install Xobni. Anything in the event logs?
Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Thu, Feb 11, 2010 at 3:19 PM, Oliver Hansen <oliver.han...@gmail.com> wrote: > Hello, > > We have been having a problem between Outlook and Exchange at the office and > I know this is a pfSense support list but I wanted to check if there was any > possible way pfSense could be causing any of the problems before I contact > MS for a paid support call and have them blame pfSense. The problem seemed > gradual so I can't say for sure or not but it was not too long after we > upgraded a lot of 1.2.2 boxes to 1.2.3-RC3. > > The problem manifests itself as exchange keeping idle connections alive and > then not allowing the client to connect because exchange has reached the > maximum connections of 32. This KB describes the error received on Exchange: > http://support.microsoft.com/kb/842022 and then this one is where I have > found myself after determining that the connections are being held too long: > http://support.microsoft.com/kb/948496/ Note it mentions "Inactive Outlook > connections to the Exchange server may not be cleaned up." as one of the > symptoms. > > Now, I've done everything on those KB articles but I just wanted to ask the > pfSense community if anyone has experienced this or if there was something I > could do to rule out pfSense as a part of the issue. It is only happening at > remote locations and not at the central office. Also, all of those locations > are where a pfsense router is in place remotely. We still have some sites on > linksys VPN systems and none of those sites have had the problem. > > Thanks for any suggestions! > > > --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
