Launching Diagnostics In-Context

Published: November 11, 2009

Updated: December 23, 2009

Applies To: Windows 7, Windows Server 2008 R2

The following examples demonstrate how to launch diagnostics for several in-context scenarios.

Launch Internet Explorer, and then attempt connect to the resource of your choice. If the connection fails, the Windows Network Diagnostics wizard opens. For example, you might attempt to connect to http://www.msn.com

When the connection attempt fails, Internet Explorer displays the message; Internet Explorer cannot display the web page, as shown in the following figure.

Internet Explorer cannot display the webpage

 

Click Diagnose Connection Problems, to launch the diagnostics. The Windows Network Diagnostics wizard opens.

After the diagnostic completes its initial analysis, review the information, and then follow the steps that diagnostics provides to resolve your problem.

The wireless Connect to a network icon indicates that wireless is not connected, and that connections are available, as shown in the following figure.

Wireless not connected - Connections available

 

Click the wireless Connect to a network icon, to view the available wireless networks, as shown in the following figure.

Listed available wireless networks

 

Select a wireless network, and then click Connect. The Connect to a Network connection status opens, as shown in the following figure.

Connecting to the selected network

 

If the connection attempt fails, a message is displayed, indicating that Windows was unable to connect to the specified network. An example is shown in the following figure.

Troubleshoot problems

 

Click Troubleshoot problems to launch diagnostics. The Windows Network Diagnostics Wizard opens. This is shown if the following figure.

NDF - Detecting problems

After the diagnostic completes its initial analysis, review the information, and then follow the steps that diagnostics provides to resolve your problem.

Problems accessing file shares can happen for numerous reasons. Some common reasons for problems accessing shared resources are:

  • The user does not have sufficient permissions to access the share.

  • The user has not provided the correct path to access the share.

  • Network connectivity problems are preventing a connection to the shared resource.

Attempt to connect to a shared resource of your choice. For example, you might attempt to connect to \\Example\SharedResource\NDF. If the connection attempt fails, a message is displayed, indicating Windows cannot access the share you specified, as shown in the following illustration.

Windows cannot access network resource

 

Click Diagnose , to launch diagnostics.

After the diagnostic completes its initial analysis, review the information, and then follow the steps that diagnostics provides to resolve your problem.

Community Additions

ADD
Show: