Example 3: Diagnostics cannot Identify or Repair the Problem
Updated: December 23, 2009
Applies To: Windows 7, Windows Server 2008 R2
In this scenario, the user is experiencing network connectivity problems and uses the Network and Sharing Center icon in the notification area of the task bar to launch diagnostics. The following section demonstrates the steps and phases that are used to launch diagnostics and attempt to detect network connectivity problems.
Diagnostics cannot fix the problem preventing network access, or suggest corrective actions
Right-click the Network and Sharing Center icon. The options to Troubleshoot problems and Open Network and Sharing Center are displayed. This is shown in the following figure.
Click Troubleshoot problems to launch diagnostics and automatically start a diagnostic session. This is shown in the following figure.
Status indicates that the detection phase of diagnostics started. This is shown in the following figure.
Status indicates that diagnostics is reviewing Web connectivity for problems. This is shown in the following figure.
Status indicates that diagnostics is checking for name resolution problems. This is shown in the following figure.
Diagnostic status signifies that it is checking for network security problems. This is shown in the following figure.
Status is updated to show that diagnostics is collecting configuration details, as shown in the following figure.
Diagnostic status reports that it is resolving problems. This is shown in the following figure.
Diagnostics reports that it is verifying if the corrective steps in the previous phase corrected the domain connectivity problem, as shown in the following figure.
Status shows that diagnostics has transitioned back to resolving problems; indicating additional problems were found in the previous phase, shown in the following figure.
Status verifies that diagnostics detected additional problems. This is shown in the following figure.
Status shows that diagnostics has restarted the network diagnostic process. This is shown in the following figure.
Diagnostic status reports that troubleshooting steps were not able to automatically correct the detected problems. Details of the problem found suggest the problem might be caused because the computer might have been incorrectly detected as being outside the domain network. Diagnostics presents options for the user to view the diagnostic details, explore additional options, or end the diagnostic session.
Summary of this example diagnostic session
Diagnostics correctly identified a problem with Inside-Outside detection on the DirectAccess client, but was unable to resolve the problem locally, or suggest corrective steps to resolve the problem.
Conclusion: NDF diagnostics were not able to automatically correct the problem, or provide the user with suggestions for corrective actions. Resolution of this problem requires a transition to a manual examination of the data provided within the Event Trace Logs (ETL) files that Windows 7 NDF automatically renders for each diagnostic session. An example of this type of examination is provided in the section Example 4: Performing a Manual Investigation of Diagnostic Log Files When Diagnostics cannot Identify or Repair the Problem of this guide.