Troubleshooting the Network Explorer

Troubleshooting the Network Explorer

The Network Explorer:

  • Always uses UDP WS-Discovery for device discovery
  • Always initiates a HTTP or HTTPS connection for metadata exchange
  • Sometimes uses a secure channel (HTTPS) for metadata exchange

The following diagnostic procedures should be used (in order) to help identify problems with the Network Explorer.

Bb648700.wedge(en-us,VS.85).gifTo troubleshoot the Network Explorer

  1. Inspect adapter and firewall settings.
  2. Use a generic host and client for UDP WS-Discovery.
  3. Use WSD Debug Client to verify multicast traffic.
  4. Inspect network traces for UDP WS-Discovery.
  5. Use a generic host and client for HTTP metadata exchange.
  6. Use WinHTTP logging to verify Get traffic.
  7. Inspect network traces for HTTP metadata exchange.
  8. If a secure channel is used, troubleshoot HTTPS secure channel communication.

The Network Explorer uses Function Discovery to enumerate network devices. For more troubleshooting information, see Troubleshooting Function Discovery Clients.

If the source of the problem cannot be identified using the above diagnostic procedures, follow the directions in Enabling WSDAPI Tracing and contact Microsoft support.

Related topics

Getting Started with WSDAPI Troubleshooting
Troubleshooting Function Discovery Clients



Community Additions

© 2016 Microsoft