- Microsoft Office Connectivity Tool
- Remote Connectivity Tool Microsoft
- Microsoft Test Connectivity Analyzer
Figure 1 - Multi-tier web application
Figure 2 - Connectivity Check – access from portal
In this example, a connectivity check was done from the VM running the application tier to the VM running the database tier. The status is returned as unreachable, and it’s important to note, one of the hops indicated a red status. Clicking on the hop indicates the presence of an NSG rule that is blocking all traffic, thereby blocking end-to-end connectivity.
Figure 3 - Unreachable status
The NSG rule configuration error was rectified and a connectivity check was repeated as illustrated below, where the results now indicate an end-to-end connectivity. The network latency between source and destination, along with hop information is also provided.
Figure 4 - Reachable status
We believe the Connectivity Check feature will give you deeper insights to network performance in Azure. We welcome you to reach out, as your feedback from using Network Watcher is crucial to help steer the product development and eco system growth.
- Outlook Test E-mail AutoConfiguration | Autodiscover troubleshooting tools | Part 1#4 | Part 21#36
- Microsoft Remote Connectivity Analyzer (ExRCA) | Autodiscover troubleshooting tools | Part 2#4 | Part 22#36
- Microsoft Connectivity Analyzer (MCA) | Autodiscover troubleshooting tools | Part 3#4 | Part 23#36
- Using Fiddler for Autodiscover troubleshooting scenarios | Part 4#4 | Part 24#36 ExRCA (Microsoft Remote Connectivity Analyzer Tool) When using the ExRCA (Microsoft Remote Connectivity Analyzer Tool) web-based tool, we are acutely using and external public server who uses for simulating the Autodiscover flow. In reality, the Autodiscover communication channel can be implemented from the internal private organization network or from a public network. The important issue is that the way that the Autodiscover channel is implemented in a scenario of private organization’s network versus external public network is different because different components are involved in the Autodiscover process. An additional important observation regarding the Microsoft Connectivity Analyzer (MCA) toll is – that although this tool is installed on the user desktop, the Microsoft Connectivity Analyzer (MCA) tool cannot use for checking or using the Autodiscover method which is implemented in an Active Directory-based environment. In other words, we cannot use the Microsoft Connectivity Analyzer (MCA) tool for testing the Autodiscover LDAP method in which the Autodiscover client addresses the local Active Directory.
Microsoft Office Connectivity Tool
- Software component versus web application The most noticeable difference between the Microsoft Connectivity Analyzer (MCA) and the ExRCA (Microsoft Remote Connectivity Analyzer) is that the MCA is a software component which we need to install versus the ExRCA that is implemented as a web application (Using the ExRCA is implemented by accessing the ExRCA URL etc.).
- Restricted number of “tests” options An additional difference is that we can relate to the Microsoft Connectivity Analyzer (MCA) as a “minimized version” or a limited version that offers only a restricted set of “tests” compared to the option that are available when using the Remote Connectivity Analyzer Tool.
- User interface The user interface of the Microsoft Connectivity Analyzer (MCA) is different from the ExRCA (Microsoft Remote Connectivity Analyzer). Versus the Microsoft Remote Connectivity Analyzer that is based on the concepts of “tabs” and a list of optional tests that the user can choose from, the MCA (Microsoft Connectivity Analyzer) interface is on a “wizard-based” interface. The user chooses the description if the problem that he experiences and, based on the “user section” the Microsoft Connectivity Analyzer (MCA) offers the most appropriate test.
- Integrated test implemented – Autodiscover + Outlook Anywhere. As part of the simplified user interface, the MCA (Microsoft Connectivity Analyzer) combines two separate tests into one. When a user reports that he cannot create a new Outlook mail profile the problem could be related to the Autodiscover infrastructure or to the Outlook Anywhere sitting on the server side. In the previous article (Microsoft Remote Connectivity Analyzer (ExRCA) | Autodiscover troubleshooting tools | Part 2#4 | Part 22#36) we review the ExRCA interface and the option of choosing a “dedicated” Autodiscover test. Versus this option, the MCA (Microsoft Connectivity Analyzer wizard offers the user to choose an option named – “I can’t log on with office Outlook”. In case that the user selects this option, the MCA will perform two different tests at the same time – the Autodiscover test + the Outlook Anywhere (RCP/HTTPS) test. General notes about the MCA interface My opinion or wish is that – the user interface should have designed differently and provide an interface that is similar or even identical to the Remote Connectivity Analyzer Tool. I hope that in future, somebody will read what I have written and adapt my recommendations (yes, I know that I live in a la la land; -)) Download and install the MCA (Microsoft Connectivity Analyzer) software component. Go to the -Microsoft Remote Connectivity Analyzer (https://testconnectivity.microsoft.com/) site and, choose the Client tab and click on the Install now option.
Remote Connectivity Tool Microsoft
- Autodiscover infrastructure test
- Outlook Anywhere infrastructure (RPCHTTPS) test In our scenario, we can see that both of this test were completed successfully. The result’s screen is divided into two parts:
- General summary of the test results (Part A in the screenshot)
- A detailed report about each of the operations that was included in the test (Part B in the screenshot)