Outlook 2013 DISCONNECTED Status
We have Outlook 2013 rolling out to users. We uninstall Outlook 2010 and do a fresh full install of 2013. Our mail is handled by Exchange 2010 SP2.
I have a number of users that are experiencing the "DISCONNECTED" status in Outlook. We use the default Logon network security of "Negotiate Authentication".
The only way that this seems to CONNECT again is if we drill down to the mailbox properties in Outlook, in the Security Tab, and change Logon Network Security to "Password Authentication (NTLM)". Then it magically connects and stays connected.
None of these steps seem to work;
We have tried rebuilding the users Outlook Profile
Running in Safe Mode
Switching to "Work Offline" and back to "Work Online"
Users credentials are fine as we can log into OWA
Turned off wifi just to be sure the connections werent swapping
Uninstalled all iTunes plugins and disabled all third party plugins
Does anyone have any ideas?
We have Barracudas LBs and Riverbeds in between these sites.
2013-08-16-13-12-17-Microsoft-Ex.jpg
I have a number of users that are experiencing the "DISCONNECTED" status in Outlook. We use the default Logon network security of "Negotiate Authentication".
The only way that this seems to CONNECT again is if we drill down to the mailbox properties in Outlook, in the Security Tab, and change Logon Network Security to "Password Authentication (NTLM)". Then it magically connects and stays connected.
None of these steps seem to work;
We have tried rebuilding the users Outlook Profile
Running in Safe Mode
Switching to "Work Offline" and back to "Work Online"
Users credentials are fine as we can log into OWA
Turned off wifi just to be sure the connections werent swapping
Uninstalled all iTunes plugins and disabled all third party plugins
Does anyone have any ideas?
We have Barracudas LBs and Riverbeds in between these sites.
2013-08-16-13-12-17-Microsoft-Ex.jpg
Mohammed Khawaja
Please go to www.testexchangeconnectivity.com and test Outlook Anywhere (RPC over HTTP) and Outlook Autodiscover. Also advise if you are using Outlook Anywhere.
ASKER
We weren't using OA until about 2 months ago. Still on Outlook 2010. Didn't have trouble with 2010.
Outlook Anywhere passes on the test connectivity site.
Outlook Anywhere passes on the test connectivity site.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Exactly what update level are you on with Exchange 2010? Which rollup?
- Microsoft Exchange Server 2010 SP2, Rollup 3
Any reason you haven't deployed Exchange 2010 SP3?
- Third party Legal Hold software isn't compatible yet.
If you use a fresh installation of Office (So not one that previously had Outlook 2010 installed on it) does that work correctly?
- I don't have a resource right now to do this. I will try.
Are you able to bypass the Riverbed as a test? I have seen that break authentication before.
- I'm leaning towards it being the Barracudas or Riverbeds, just need to find proof. Not sure how to test this. I guess Id have to create the email profile pointing it to the internal IP of the Exchange server instead of it using autodiscover. Id still pass thru the riverbed though since Exchange is in a data center offsite.
- Microsoft Exchange Server 2010 SP2, Rollup 3
Any reason you haven't deployed Exchange 2010 SP3?
- Third party Legal Hold software isn't compatible yet.
If you use a fresh installation of Office (So not one that previously had Outlook 2010 installed on it) does that work correctly?
- I don't have a resource right now to do this. I will try.
Are you able to bypass the Riverbed as a test? I have seen that break authentication before.
- I'm leaning towards it being the Barracudas or Riverbeds, just need to find proof. Not sure how to test this. I guess Id have to create the email profile pointing it to the internal IP of the Exchange server instead of it using autodiscover. Id still pass thru the riverbed though since Exchange is in a data center offsite.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please note the testexchangeconnectivity.c
@ mnkhawaja
TestExchangeconnectivity isn't going to prove anything in this scenario. The problem is between two sites, not the external traffic.
Simon.
TestExchangeconnectivity isn't going to prove anything in this scenario. The problem is between two sites, not the external traffic.
Simon.
ASKER
This turned out to be a riverbed issue. We continue to troubleshoot with Microsoft and Riverbed, but as soon as Mapi Exchange Optimization is disabled Outlook 2013 stays connected.
The other work around was to disable Encryption in Outlook if you leave the Riverbed Mapi Exchange Optimization enabled. But we didnt want to pass unencrypted traffic around the network.
The other work around was to disable Encryption in Outlook if you leave the Riverbed Mapi Exchange Optimization enabled. But we didnt want to pass unencrypted traffic around the network.