Updated: December 23, 2009
Applies To: Windows 7, Windows Server 2008 R2
In general, NDF diagnostics fall into one of two categories:
The following sections describe the differences between in-context and out-of-context diagnostics.
In-context diagnostics are launched from within programs or features that are designed with the option to launch NDF diagnostics. In-context diagnostics are typically launched as a direct response to the failed connection attempt of an application or feature; for example, a failed browse session to a particular Web site. When using in-context diagnostics for any given diagnostic session, it is the program of feature that provides the context in which diagnostics will operate. Examples of in-context diagnostics are:
Internet Explorer fails to connect to the target resource, and then provides the option to Diagnose Connection Problems.
A failed attempt to connect to a wireless network presents the option: Troubleshoot problems.
A failed attempt to access a shared folder renders the option to Diagnose.
Unllike in-context diagnostics, out-of-context diagnostics are not launched in direct response to a failed connection by a program or feature. Diagnostics requests the user to provide the context (or parameters) that NDF will use for troubleshooting in that diagnostic the session. For example, diagnostics might request the user to specify a web site address (URL), or to select which network adapter to diagnose on a multi-homed computer.
There are numerous methods to launch out out-of-context diagnostics. For example, you can launch out-of-context diagnostics by using either the Action Center or the Network and Sharing Center icons in the Notification Area, or by launching diagnostics from the predefined Network and Internet Troubleshooters.
Examples of out-of-context diagnostics include the predefined Network and Internet troubleshooters:
Connection to a Workplace by Using DirectAccess
In this section
The following sections provide examples that demonstrate how to start NDF diagnostics: