Outlook 2013 with exchange online account disconnected, tryin to connect for hours or indefinitely

I posted this in another forum (office 365) and was told to copy it here as it wasn't an office 365 issue so here is what I posted there:

===================================

Let me see if I can clarify better. This issue has been ongoing as long as I have worked for this client (I started in January but have been told the issue has been going on since before November of last year). The client has multiple construction sites and its headquarters. There is a remote desktop server setup with a public IP address for the users "in the field" for accessing network resources at headquarters. At major construction sites (currently 3) they have high speed internet service installed since the projects typically are 1+ years to complete. So at current times we have the following:

Main office:

Remote Desktop Server with logins for all employees

Main 2012R2 server

50MB/s internet connection via CenturyLink ISP

Site 1:

3 main users of computers. 1 constant user, 2 minimal use users. All 3 have experience the issue 3+ times a week

Comcast 50MB/S ISP

Site 2:

3 Main users of computers. 1 constant, 2 medium use users. All 3 experience the issue 3+ times a week

Comcast 50MB/s ISP

Site 3:

4+ computer users. 1 constant, 2 medium use users and the rest check email couple times a day. They also experience the disconnect issue 3+ times a week

15 MB/S DSL from CenturyLink ISP

There have been instances where (as examples) user 1a called me to tell me it was happening. Users 1b and 1c were not experiencing the issue. I was able to use a remote tool called Teamviewer to connect to her computer. Once connected I tried to open OWA but it would not connect. I tried to ping the site and could not get a response. To verify I remoted into user 1b computer and his outlook was still connected and pinged fine. Both users being at the same site are on the same network. Had user 1a remote desktop into the RDserver at the main office. Remoted into the server at the office her outlook on that machine connected no issues (in my mind rules out account issue?).

I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was fine. I don't think it was her account because it worked fine from the RD Server plus email service to iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days).

Now to answer the questions for you:

1. it happens to all computers not at the main office but happens at random times to them. It also does not affect every computer at a remote location. It could be 1 or it could be multiple computers at the same time.

2. Affected users iPhones, iPads and outlook 2013 pro session on the RD Server at the main office continue to work no issues.

3. They cannot get to OWA on their machines when in that state, however can log into OWA on another machine plus the answer to #2 above.

4. It is all users at those locations, however I have experienced it myself at my house 1 time since January (I have a different exchange online plan/company than the one I am discussing in this post). The issue is random and it is uncertain if it will correct itself if left sitting long enough (longest time it has been left is about 20 minutes or so) however even 20 minutes is a long time to wait for the service to return so users just reboot.

Please let me know If you have any solutions/ideas.

Thanks,

Brandon Smith

Cadence Communications

====================================

Hi Branon,

Thanks for your detailed information.

After going your post carefully, I am impressed by your strong technical skills. Regarding I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was fine. I don't think it was her account because it worked fine from the RD Server plus email service to iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days) , I go along with you. Since the affected account could connect to other clients without issue , it indicates Office 365 account is no problem. And other computer were working fine and can connect to her computer, it shows the network environment does not cause the issue. In this situation, the issue should relate to the specific Outlook Client. However this forum mainly focuses on Office 365 online services, to get more accurate responses, its suggested that you raise the problem in the Outlook forum. If they got any result and you need further assistance from Office 365 side, please feel free to let us know.

In addition, about I have had the users try to use OWA when it gets disconnected but they cannot get to that URL either. IE comes up with page not found, Id like to collect some information:

1. Does the issue only happen to IE? Have you tried logging in other browsers using the OWA address (like Chrome or Firefox)? Does it work?
2. Does only this user have the issue? Does it happen to other users?
3. Which version of Internet Explorer browser does the user use?
4. Could you provide us with the whole screenshot of the error message? You can post screenshots in our forum by clicking Use rich formatting and selecting the Insert Image icon.

Also, please try the following steps for troubleshooting:

a. Clear the IE caches and cookies when you log into Office 365 again.
b. Use the InPrivate Browsing of Internet Explorer to login.
c. Reset Internet Explorers settings, and try again.
d. Try to login in another network environment.

If there is any update, please let us know. I ll keep on monitoring this thread.

Best regards,
Jamie

===============================

As of today we still randomly experience this disconnect issue. Just today I had my test user call me to say she was disconnected. She is in location 2 where I have a test laptop also setup with her logged in. When she called I had her check the test laptop and the outlook profile on that machine (same network) was still connected while her computer was not connected. I had her run the online analyzer tool on her machine (the one that would not connect) which ran for almost 2 hours. The tool finished right at the same time that her outlook finally connected back to the server.

If anyone has any ideas/solutions please let me know.

Thanks in advance,

Brandon Smith

Cadence Communications Inc. 

April 16th, 2015 1:41pm

Oddly enough my computer is right at this moment in this same disconnected state. Outlook shows an exclamation point in a yellow triangle. Its state is disconnected. If I go to portal.office.com I get to the login page but get page can't be displayed after entering my credentials. I tried using google and found this for login https://outlook.office365.com/owa/ it too times out and can't be displayed.
if I try and ping these sites I get:
====================================================================
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\brandon.CAD1>ping portal.office.com

Pinging us.portal.office.akadns.net [2a01:111:f100:4001::4625:61ea] with 32 byte
s of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2a01:111:f100:4001::4625:61ea:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\brandon.CAD1>ping login.microsoftonline.com

Pinging aadg.windows.net.nsatc.net [168.62.24.150] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 168.62.24.150:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
===============================================================================

If I remote into another machine at a client site I can log into portal.office.com using my email account.

I ran the outlook connectivity analyzer tool and got this if it helps:
===============================================================
Testing Outlook connectivity.
 The Outlook connectivity test completed successfully.
 
Additional Details
 
Elapsed Time: 41017 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for brandon@cadcom.us.
 Autodiscover was tested successfully.
 
Additional Details
 
Elapsed Time: 12161 ms.


 
Test Steps
 
Attempting each method of contacting the Autodiscover service.
 The Autodiscover service was tested successfully.
 
Additional Details
 
Elapsed Time: 12161 ms.


 
Test Steps
 
Attempting to test potential Autodiscover URL https://cadcom.us:443/Autodiscover/Autodiscover.xml
 Testing of this potential Autodiscover URL failed.
 
Additional Details
 
Elapsed Time: 475 ms.


 
Test Steps
 
Attempting to resolve the host name cadcom.us in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 184.168.55.1

Elapsed Time: 173 ms.

Testing TCP port 443 on host cadcom.us to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 149 ms.

Testing the SSL certificate to make sure it's valid.
 The SSL certificate failed one or more certificate validation checks.
 
Additional Details
 
Elapsed Time: 152 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server cadcom.us on port 443.
 The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
 
Additional Details
 
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.

Elapsed Time: 91 ms.

Attempting to test potential Autodiscover URL https://autodiscover.cadcom.us:443/Autodiscover/Autodiscover.xml
 Testing of this potential Autodiscover URL failed.
 
Additional Details
 
Elapsed Time: 9000 ms.


 
Test Steps
 
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8, 2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8

Elapsed Time: 304 ms.

Testing TCP port 443 on host autodiscover.cadcom.us to ensure it's listening and open.
 The specified port is either blocked, not listening, or not producing the expected response.
  Tell me more about this issue and how to resolve it
 
Additional Details
 
A network error occurred while communicating with the remote host.


Elapsed Time: 8696 ms.

Attempting to contact the Autodiscover service using the HTTP redirect method.
 The Autodiscover service was successfully contacted using the HTTP redirect method.
 
Additional Details
 
Elapsed Time: 2684 ms.


 
Test Steps
 
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8, 2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8

Elapsed Time: 39 ms.

Testing TCP port 80 on host autodiscover.cadcom.us to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 57 ms.

The Microsoft Connectivity Analyzer is checking the host autodiscover.cadcom.us for an HTTP redirect to the Autodiscover service.
 The redirect (HTTP 301/302) response was received successfully.
 
Additional Details
 
Redirect URL: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Pragma: no-cache
X-FEServer: BY2PR07CA071
Connection: close
Content-Length: 0
Cache-Control: no-cache
Date: Tue, 21 Apr 2015 04:40:05 GMT
Location: https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET


Elapsed Time: 47 ms.

Attempting to test potential Autodiscover URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
 Testing of the Autodiscover URL was successful.
 
Additional Details
 
Elapsed Time: 2540 ms.


 
Test Steps
 
Attempting to resolve the host name autodiscover-s.outlook.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2

Elapsed Time: 345 ms.

Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 44 ms.

Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Additional Details
 
Elapsed Time: 177 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.
 The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.

Elapsed Time: 119 ms.

Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 
Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.

Elapsed Time: 0 ms.

Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
 One or more certificate chains were constructed successfully.
 
Additional Details
 
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.

Elapsed Time: 18 ms.

Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 
Additional Details
 
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Elapsed Time: 3 ms.

Testing the certificate date to confirm the certificate is valid.
 Date validation passed. The certificate hasn't expired.
 
Additional Details
 
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM

Elapsed Time: 0 ms.

Checking the IIS configuration for client certificate authentication.
 Client certificate authentication wasn't detected.
 
Additional Details
 
Accept/Require Client Certificates isn't configured.

Elapsed Time: 146 ms.

Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
 The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
 
Additional Details
 
Elapsed Time: 1827 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user brandon@cadcom.us.
 The Autodiscover XML response was successfully retrieved.
 
Additional Details
 
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol Type="mapiHttp">
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<MailStore>
<ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us</ExternalUrl>
</MailStore>
<AddressBook>
<ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us</ExternalUrl>
</AddressBook>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 443c7500-1216-4307-b195-8d742873d0f0
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=JYEVNJSG0UERWBME1PF2A; expires=Wed, 20-Apr-2016 04:40:07 GMT; path=/; secure; HttpOnly,EXOBasicAuth=compactTicket=&key=brandon%40cadcom.us+microsoft.exchange.autodiscover+157.56.138.143+&signature=QJdNVZ9GjQrYkxZg4iXgN8XbU7ZlhTifQyXVjqCwqbBgJL14yiG8oVRxKprB6LXqEBx90YDherBvRURQmGweF+XHW5Eg4gKIhRhSgy6XhMdQslO+PSV1TuZJIHB0g8KcM1MDr4LEuS19bT1HFPpLEUf7A+tmrfTQyy6l21zaUohb/Z0XZUn1o/pkbIcBBSb+tOVAemIsTyHN/p0VbbkA2AeMdVVJIz1wHLW7s9o7fCtJ7cM33Wzz9M6g5k/bNv/NAe9a2nbCZjpyqdmDkKrdmalekhBVkusIskPX5p8aVU8CuiTRtyIcRq8IWxvDhwyH3RiFnyVd5ytNy42M0r7+gQ==&puid=100300008CF2A4C2&expireTime=635651446880000000&membername=brandon%40cadcom.us&flags=False&userType=ManagedBusiness; expires=Mon, 20-Apr-2015 16:38:08 GMT; path=/Autodiscover; secure; HttpOnly,X-BackEndCookie2=brandon@cadcom.us=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,X-BackEndCookie=brandon@cadcom.us=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 4345


Elapsed Time: 1525 ms.

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user brandon@cadcom.us.
 The Autodiscover XML response was successfully retrieved.
 
Additional Details
 
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us</Server>
<ServerDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us</ServerDN>
<ServerVersion>73C18088</ServerVersion>
<MdbDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<AuthPackage>Anonymous</AuthPackage>
<PublicFolderServer>outlook.office365.com</PublicFolderServer>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsPartnerUrl>
<GroupingInformation>CO1PR04</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 4412d758-013f-4700-bde1-06dc5e66bf6d
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=YVWYC2UW3EAOSJXJYJDCDW; expires=Wed, 20-Apr-2016 04:40:08 GMT; path=/; secure; HttpOnly,X-BackEndCookie2=brandon@cadcom.us=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,X-BackEndCookie=brandon@cadcom.us=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 9631


Elapsed Time: 301 ms.

Autodiscover settings for Outlook connectivity are being validated.
 The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
 
Additional Details
 
Elapsed Time: 0 ms.

Testing MAPI over HTTP connectivity to server outlook.office365.com
 MAPI over HTTP connectivity was verified successfully.
 
Additional Details
 
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET


Elapsed Time: 3246 ms.


 
Test Steps
 
Attempting to resolve the host name outlook.office365.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2

Elapsed Time: 152 ms.

Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 70 ms.

Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Additional Details
 
Elapsed Time: 251 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
 The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.

Elapsed Time: 141 ms.

Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.

Elapsed Time: 3 ms.

Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
 One or more certificate chains were constructed successfully.
 
Additional Details
 
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.

Elapsed Time: 34 ms.

Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 
Additional Details
 
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Elapsed Time: 6 ms.

Testing the certificate date to confirm the certificate is valid.
 Date validation passed. The certificate hasn't expired.
 
Additional Details
 
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM

Elapsed Time: 0 ms.

Testing HTTP Authentication Methods for URL https://outlook.office365.com/mapi/emsmdb/?MailboxId=c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us.
 The HTTP authentication methods are correct.
 
Additional Details
 
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET


Elapsed Time: 190 ms.

Testing the MAPI Address Book endpoint on the Exchange server.
 The address book endpoint was tested successfully.
 
Additional Details
 
Elapsed Time: 1987 ms.


 
Test Steps
 
Testing the address book "Check Name" operation for user brandon@cadcom.us against server outlook.office365.com.
 Check Name succeeded.
 
Additional Details
 
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon

Elapsed Time: 1987 ms.

Testing the MAPI Mail Store endpoint on the Exchange server.
 We successfully tested the Mail Store endpoint.
 
Additional Details
 
Elapsed Time: 594 ms.


 
Test Steps
 
Attempting to log on to the Mailbox.
 We were able to log on to the Mailbox.
 
Additional Details
 
Elapsed Time: 594 ms.

Testing RPC over HTTP connectivity to server outlook.office365.com
 RPC over HTTP connectivity was verified successfully.
 
Additional Details
 
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET


Elapsed Time: 25606 ms.


 
Test Steps
 
Attempting to resolve the host name outlook.office365.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2

Elapsed Time: 42 ms.

Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 61 ms.

Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Additional Details
 
Elapsed Time: 223 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
 The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.

Elapsed Time: 121 ms.

Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.

Elapsed Time: 1 ms.

Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
 One or more certificate chains were constructed successfully.
 
Additional Details
 
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.

Elapsed Time: 36 ms.

Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 
Additional Details
 
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Elapsed Time: 5 ms.

Testing the certificate date to confirm the certificate is valid.
 Date validation passed. The certificate hasn't expired.
 
Additional Details
 
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM

Elapsed Time: 0 ms.

Checking the IIS configuration for client certificate authentication.
 Client certificate authentication wasn't detected.
 
Additional Details
 
Accept/Require Client Certificates isn't configured.

Elapsed Time: 173 ms.

Testing HTTP Authentication Methods for URL https://outlook.office365.com/rpc/rpcproxy.dll?c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6002.
 The HTTP authentication methods are correct.
 
Additional Details
 
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET


Elapsed Time: 27 ms.

Attempting to ping RPC proxy outlook.office365.com.
 RPC Proxy was pinged successfully.
 
Additional Details
 
Elapsed Time: 2099 ms.

Attempting to ping the MAPI Mail Store endpoint with identity: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6001.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 47 ms.

Elapsed Time: 5049 ms.

Testing the MAPI Address Book endpoint on the Exchange server.
 The address book endpoint was tested successfully.
 
Additional Details
 
Elapsed Time: 6447 ms.


 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6004.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 218 ms.

Elapsed Time: 4230 ms.

Testing the address book "Check Name" operation for user brandon@cadcom.us against server c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us.
 Check Name succeeded.
 
Additional Details
 
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon

Elapsed Time: 2216 ms.

Testing the MAPI Referral service on the Exchange Server.
 The Referral service was tested successfully.
 
Additional Details
 
Elapsed Time: 6271 ms.


 
Test Steps
 
Attempting to ping the MAPI Referral Service endpoint with identity: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6002.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 640 ms.

Elapsed Time: 4630 ms.

Attempting to perform referral for user /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon on server c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us.
 We got the address book server successfully.
 
Additional Details
 
The server returned by the Referral service: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us

Elapsed Time: 1640 ms.

Testing the MAPI Address Book endpoint on the Exchange server.
 The address book endpoint was tested successfully.
 
Additional Details
 
Elapsed Time: 923 ms.


 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6004.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 62 ms.

Elapsed Time: 72 ms.

Testing the address book "Check Name" operation for user brandon@cadcom.us against server c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us.
 Check Name succeeded.
 
Additional Details
 
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon

Elapsed Time: 851 ms.

Testing the MAPI Mail Store endpoint on the Exchange server.
 We successfully tested the Mail Store endpoint.
 
Additional Details
 
Elapsed Time: 4286 ms.


 
Test Steps
 
Attempting to ping the MAPI Mail Store endpoint with identity: c59498dd-fab9-4c96-a42a-0a46dc42cfea@cadcom.us:6001.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 656 ms.

Elapsed Time: 3656 ms.

Attempting to log on to the Mailbox.
 We were able to log on to the Mailbox.
 
Additional Details
 
Elapsed Time: 628 ms.
=============================================================================

Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 12:55am

I still have users (and myself now) that have experienced and continue to experience this issue. Does anyone have any ideas at all to try on these?

I have ensured all windows/office updates are installed on the clients. I have recreated the outlook profiles on several of them as well. The accounts still function logging in on alternate machines even on the same network so I believe it rules out network and account issues.

I am at a loss and would appreciate any help offered at all.


Thanks and have a great day,
Brandon

April 23rd, 2015 1:32pm

Still having this issue. Here is latest from another thread on the subject below. Anyone have any ideas??????

Hi Brandon,

Thank you for coming back.

Please try the followings steps for further troubleshooting:
1. Try other email clients in these PCs to check whether the issue persists.
2. Try to set up other email accounts (Hotmail, Yahoo, Gmail) in the problematic Outlook client to check whether the issue occurs.

Any updates will be appreciated.

Thanks,
Brook

Thanks for the feedback.

 

                
<fieldset class="field-list"> You have posted to a forum that requires a moderator to approve posts before they are publicly available. </fieldset> <fieldset class="field-list">
    • <input class="suggest-answer" name="suggest-answer" type="checkbox" /><label class="suggest-answer-label">Suggested Answer</label><textarea cols="160" rows="3"></textarea>Reply Use rich formatting Cancel
    </fieldset>
  • BrandonSmith Posted by BrandonSmith on 5/4/2015 5:58 PM

    Sorry for the delayed response.

    1. We have the users setup with iPad and iPhone to access their exchange online accounts as well. Those do not lose connectivity like the Outlook/laptop combinations. If there is another client you would like to test let me know and I can try that but am fairly sure given the ipad/iphone connectivity not dropping it will result in the same.

    2. I setup a test Gmail account and added it to one of the user's machines to test. Unfortunately it has taken a while for her machine to get into the disconnected state but she informed me this morning that it occurred. She was able to send and receive emails to/from the gmail account but could not get outlook/exchange online to connect. This did however correct itself and both worked after she rebooted the computer.

    It appears to me that for some reason the outlook to exchange online connection periodically has issues that seem to remedy themselves if you leave the machine for approximately 2 hours or more and/or reboot the computer (this causes outlook to work instantly). It seems to have no effect on the apple devices connected to the same account and the account still functions if logging into another computer or RDSever.

    Please advise where to go or what to do next as this is still occurring randomly.

    Thanks in advance,

    Brandon

  • Free Windows Admin Tool Kit Click here and download it now
    May 4th, 2015 1:10pm

    This topic is archived. No further replies will be accepted.

    Other recent topics Other recent topics