Example 2: Diagnostics can Identify the Problem but cannot Repair or Provide a Recommended Solution

  • Article

Updated: December 23, 2009

Applies To: Windows 7, Windows Server 2008 R2

In this example, a user with a computer running Windows® 7 is attempting to connect to a resource on the network.

Diagnostics cannot correct access to a network resource, but suggests corrective steps

Upon failing to connect to the specified resource, Windows 7 indicates that no items match the specified parameters entered by the user. This is shown in the following figure.

 

A Network Error message is automatically displayed, indicating that the computer cannot access the specified resource. Windows 7 displays an option to diagnose the problem. This is shown in the following figure.

 

The user clicks Diagnose. Windows Network Diagnostics is launched and begins investigating the problem. This is shown in the following figure.

 

Diagnostics is not able to automatically correct the problem. However, diagnostics suggests several actions that the user can take to attempt to resolve the problem. This is shown in the following figure.

 

Diagnostics indicates that the session has ended and that it was not able to correct the problem. Options are provided to show additional options or close diagnostics. This is shown in the following figure.

 

Summary of this example diagnostic session

  • The user launched diagnostics, in response to an option that is automatically provided by Windows 7 when the connection attempt to a network resource was unsuccessful.

  • Diagnostics identified that a name resolution problem existed, and made attempts to automatically correct connectivity problems. The corrective steps were unsuccessful.

  • Diagnostics background processing determined that the problem was either caused by an incorrectly specified resource – possibly a spelling error - or was external to the local computer.

  • Diagnostics provided the user with suggested actions to resolve the problem. Additionally, diagnostics provided the user with a link to relevant product documentation.

Conclusion:Windows Network Diagnostics was not able to automatically correct the problem, but indicated the most probable causes, and suggested actions that the user could take to resolve the problem.