none
Users not able to reconnect Outlook 2007/Outlook 2010 to Exchange 2010 server after connecting to our Wireless on a different VLAN

    Question

  • We have a handful of users who disconnect their laptop from their docking station which immediatley connects them to our wireless which is on a different vlan.  Outlook 2007/2010 is opened at the time they undock their laptop and automatically reconnects Outlook through the wireless.  The problem is when they leave the wireless with Outlook open and return back to their docking station, Outlook stops responding.  From that point on, the user gets the message "Outlook cannot connect to the Exchange Server.  The weird thing is that the user has problems connecting to Outlook even on a totally different pc and alomost appears to be user account specific.  User does not have a roaming profile.  Sometime connecting back to the same wireless vlan will then allow them to start outlook again.  This is only happening to a few employees.  Others doing the same routine continue to work.

    This started after upgrading our domain to 2008 and upgrading from Exchange 2003 to Exchange 2010.  These two changes were made within 2 days of each other which is complicating the troubleshooting of this.  When doing a connection test, it cannot establish a connection to the Directory.  Rebuilding the Outlook Profile does not correct the issue. 

    Any ideas?

     

     

    Tuesday, March 22, 2011 2:19 AM

Answers

  • You need to check the eventviewer logs application on your Exchange server for 9646 to see if these users are maxing out on their 32 session limit. Since they doc and undoc frequently, they leave stale sessions on the servers once it reaches 32 they will not be able to connect until the stale session times out.

    Event ID 9646 is logged in the application event log of your Exchange Server 2003 computer when a client opens many MAPI sessions
    http://support.microsoft.com/kb/842022


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    • Marked as answer by Gavin-Zhang Tuesday, April 05, 2011 9:44 AM
    Tuesday, March 22, 2011 3:22 PM
  • The issue turned out to be our Barracuda Load Balancer.  Apparently the version did not fully support Exchange 2010.  Upgrading to latest firmware corrected our issue.

     

    • Marked as answer by Jerry_R Wednesday, November 09, 2011 9:52 PM
    Wednesday, November 09, 2011 9:52 PM

All replies

  • Well, try to find out what the affected users have in common that the un-affected users doesn't have and go from there.
    Jesper Bernle | Blog: http://xchangeserver.wordpress.com
    Tuesday, March 22, 2011 9:03 AM
  • Are you using CAS Array?


    Gulab | MCTS-MCITP Messaging: 2010 | MCTS-MCITP Messaging: 2007 | MCC 2011 | Skype: Gulab.Mallah
    Tuesday, March 22, 2011 2:20 PM
  • You need to check the eventviewer logs application on your Exchange server for 9646 to see if these users are maxing out on their 32 session limit. Since they doc and undoc frequently, they leave stale sessions on the servers once it reaches 32 they will not be able to connect until the stale session times out.

    Event ID 9646 is logged in the application event log of your Exchange Server 2003 computer when a client opens many MAPI sessions
    http://support.microsoft.com/kb/842022


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    • Marked as answer by Gavin-Zhang Tuesday, April 05, 2011 9:44 AM
    Tuesday, March 22, 2011 3:22 PM
  • Hi Jerry,

    Above gave some good suggestion, any update for your issue?
    If the issue still coccur, please feel free to tell us.

    Regards!
    Gavin
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Saturday, March 26, 2011 7:36 AM
  • The issue turned out to be our Barracuda Load Balancer.  Apparently the version did not fully support Exchange 2010.  Upgrading to latest firmware corrected our issue.

     

    • Marked as answer by Jerry_R Wednesday, November 09, 2011 9:52 PM
    Wednesday, November 09, 2011 9:52 PM