Announcement

Collapse
No announcement yet.

outlook client ramdomally diconnected from exhcnage

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • outlook client ramdomally diconnected from exhcnage

    Hi,
    this thing started to occur, when clients outlook (2003/2007) are connected with microsoft exchange 2003 standard (6.5.7638.1) on server 2003 R2 standard sp2, some of those outlook clients (randomally), for random period of time, gets disconnected from exchange and outlook is "Try to connect to exchange server...".
    the priv file is not larger than 50 GB.

    thanks all.
    Last edited by noamba; 28th March 2010, 09:33.

  • #2
    Re: outlook client ramdomally diconnected from exhcnage

    try to access the user account through OWA when the outlook is trying to connect to the server and also check if the required services are up and running on the server.

    Does the event logs on exchange show up any error messages ?

    Comment


    • #3
      Re: outlook client ramdomally diconnected from exhcnage

      OWA and OMA was working fine...
      some errors on exchange event viewer displaying: 9646
      Mapi session "/o=Exchange/ou=First Administrative Group/cn=Recipients/cn=user" exceeded the maximum of 32 objects of type "session".

      Comment


      • #4
        Re: outlook client ramdomally diconnected from exhcnage

        That (usually) indicates an unreliable network connection between the client PC and the server. Can also be caused by sending bulk mail, MS KB here. I've got a few clients with satellite offices connected over IPSec VPNs that got this a lot until we put the session limit up. Alternatively you can switch them to RPC over HTTPS.

        Clearing the error is trivial, simply restart the Exchange information store and it'll bin all the dead sessions. It takes seconds so will go unnoticed by your users.
        BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
        sigpic
        Cruachan's Blog

        Comment


        • #5
          Re: outlook client ramdomally diconnected from exchange

          The first thing I would check is that the server is fully patched.
          That means both Windows, Exchange and network card drivers. This sounds like the TCP Chimney issue, which is resolved by updating Windows and the NIC drivers. If the NIC drivers are not dated 2009 or later, then they need updating.n

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment

          Working...
          X