The issue was mainly present on the LAN and was mitigated if users were on the guest or work wireless networks.As we are aware Outlook and the rest of the office suite do not perform their own check for connectivity but rather follow the operating systems lead so the root cause of the problem lies with the Microsoft Connect Test process, or so it would seem.Multiple tests were conducted that showed while the status showed No Internet we could actually connect to and query the DNS for the ncsi websites, so it wasn’t a connection, firewall or proxy issue causing the problems. We noted instantly that when switching to a network that shows as Connected the issues went away but would resurface. The Microsoft 365 connectivity test can help to identify the root cause of that problem leading to a recommended network performance improvement action.First off, Microsoft Windows does an internet connection test (Also referred to as NCSI and Microsoft Connect Test) which reaches out to a microsoft domain and verify’s it is able to connect, if the operating system isn’t able to connect to the site at that time it generates a flag which shows the message stating you have No Internet.For example: Microsoft Office Outlook Connectivity Tests a connectivity test that inspect Outlook client session that uses the Outlook Anywhere service.We have seen this issue for a good many years with minimal issues, until we switched our users to Office 365, initially everything was working as expected until we started to get users who simply could not connect to their mailbox using Outlook and installed copies of outlook unable to connect to the licensing server to check their validity. And delete items in the Microsoft Office Outlook Connectivity Tests mailbox.However, there was a further option we had not tried of “Disabled”, instantly on setting this the connection status was Connected, reverting the setting showed us the old Not Connected status and setting it to Disabled again would once again fix the issue. All of us, has properly gotten a call from someone whose Outlook client is having trouble connecting to their Exchange environment and a lot of us properly already known the infamous web based tool from Microsoft called Exchange Remote Connectivity Analyzer (ExRCA), which can be used to test external connections to your Exchange environment, for a lot of different client scenatios, such as Outlook Anywhere, ActiveSync etc.Microsoft have done a major updated their toolkit Remote Connectivity Analyzer, the new version of the tool is now able to analyze connection scenarios for: All had short term effects but as soon as another change was detected the problems would recur and reverting the changes had no effect, it would seem restoring the Connected status by anything we were doing was a complete fluke.It would seem the fix was overlooked slightly while we were looking into the advanced settings of the NIC itself one option was “ipv4 checksum offload” we had tried this set this as “Tx and Rx Enabled”, “Rx Enabled” and “Tx Enabled” – each time as reported above we had short term success. As well an a client based version of the RCA tool (currently in beta)The new name is Microsoft Remote Connectivity Analyzer.It is an awesome and highly recommended tool for troubleshooting Exchange, Lync and Office 365 environments.
You cannot use your Microsoft Office 365 federated credentials to authenticate Microsoft Outlook or Microsoft Exchange ActiveSync by using a smartphone to Exchange Online services. If you review URL ( ) it provides a few test test and possible solution. If your having issues with authentication or general configuration issues. So I have taken this opportunity to provide a few resources from MOSDAL and the Office 365 Support Team. However, it was only a certificate issue due to my router blocking port 443. I traced the issue to a certificate error using MOSDAL. Check whether the following conditions are true:The SSO-enabled user account cannot access Autodiscover and receives an "HTTP 401 authorized response" error message. – ExRCA is attempting to retrieve an XML Autodiscover response from URL htts://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user – Attempting to send an Autodiscover POST request to potential Autodiscover URLs Microsoft Office Outlook Connectivity Tests Code Is ReturnedRetype your credentials and try again""LogonUser() Failed with error code: 1789" after you enter enterprise administrator credentials in the Directory Synchronization Configuration Wizard in Office 365Error message when you try to run the Microsoft Online Services Directory Synchronization Configuration wizard: "The Enterprise Administrator credentials that you supplied are not valid. Microsoft Remote Connectivity Analyzer Office 365Microsoft Remote Connectivity Analyzer Office 365 SSO Sign-InMicrosoft Remote Connectivity Analyzer In ProgressMicrosoft Remote Connectivity Analyzer Passed with a warningMicrosoft Remote Connectivity Analyzer MSOL ResolvedIn addition, I have included a few references on ADFS2, DirSync and Office 365 in general belowActive Directory Federation Services 2.0 Related ResourcesHow to use custom URLs to enable a transparent single sign-on experience for identity federation in an Office 365 environmentYou cannot assign a federated domain to a user in the Microsoft Online Portal"Your organization could not sign you in to this service" error message occurs when a user tries to sign in to Microsoft Online Portal as a federated userYou cannot connect to Microsoft Online Services by using the Identity Federation Management toolA federated user is prompted for credentials or cannot sign in to Microsoft Online ServicesA federated user is prompted unexpectedly to enter their credentials when they access an Office 365 resourceA Federated user is repeatedly prompted for credentials, and then the user cannot connect to Microsoft Office 365How to reestablish trust with the Microsoft Online Services ID service after the AD FS 2.0 server stops respondingTroubleshooting AD FS 2.0 federation services published directly to the Internet using a firewall device instead of an ADFS Proxy serverA sub-domain does not inherit the changes that are made to the top-level domain in Office 365A token-signing certificate has expired or was renewed for Office 365 Identity FederationYou are prompted to enter your user name and password when you connect to Office 365 resources using a rich-client applicationFirewall prevents users from using Office 365 services from rich clientsInternet Explorer cannot display the Office 365 portal webpage when a federated user tries to sign inYou are repeatedly prompted for credentials when you try to log in to the AD FS 2.0 service endpoint in Office 365Active Directory Federation Services 2.0 hotfix information for Microsoft Lync and Office Professional Plus sign-in issues in the Office 365 environmentYou cannot open the Microsoft Online Services Module for Windows PowerShellFederated users cannot connect to an Exchange Online mailboxHow to change the ADFS 2.0 service communications certificate after it expiresUsers cannot sign out of Office 365 web servicesOffice 365 Identity Federation service implications of AD FS 2.0 implementation scenariosDomain name requirements to set up a federated domain for Office 365 identity or Exchange federation (rich coexistence)You receive a certificate warning when you try to access Microsoft Office 365 resources by using an identity-federated accountHow to troubleshoot identity federation user account issues in the Office 365 environmentHow to troubleshoot Identity Federation client devices in Office 365The "500" error code is returned when you send an HTTP SOAP request to the "/adfs/services/trust/mex" endpoint on a computer that is running Windows Server 2008 R2 or Windows Server 2008An identity-provider-initiated sign-on process is slow in Windows Server 2008 R2 and in Windows Server 2008Error message in the Microsoft Online Services Directory Synchronization tool in Microsoft Office 365: "Your version of the Microsoft Online Services Directory Synchronization Configuration Wizard is outdated"Error message when you try to run the Microsoft Online Services Directory Synchronization Configuration wizard in Office 365: "The user name must be provided in valid UPN format"Error message when you try to run the Microsoft Online Services Directory Synchronization Configuration wizard: "Your credentials could not be authenticated. I chose to run the Office 3665 SSO Test.Microsoft Remote Connectivity Analyzer –. If both conditions are true, you have confirmed that SSO failures are causing Outlook authentication to fail.You have a couple of choices when running the tool and its invaluable in resolving a number of issues.
0 Comments
Leave a Reply. |
Details
AuthorJames ArchivesCategories |