Troubleshooting WSDAPI Applications Using Directed Discovery
Applications that use directed discovery send Probe messages over HTTP or HTTPS to discover devices. The corresponding ProbeMatches messages sent in response are also sent over HTTP or HTTPS. Directed discovery can be initiated by the Add Printer Wizard, a Function Discovery client, or a WSDAPI application. The Probe and ProbeMatches messages are structurally identical to those sent over UDP. The messages are prefixed with the appropriate HTTP or HTTPS headers.
The following diagnostic procedures should be used (in order) to help identify problems with an application using directed discovery.
To troubleshoot a WSDAPI application using directed discovery
- Inspect adapter and firewall settings.
- Use a generic host and client for HTTP metadata exchange.
- Use WinHTTP logging to verify Get traffic.
- Inspect network traces for an application using directed discovery.
- If a secure channel is used, troubleshoot HTTPS secure channel communication.
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.
- Getting Started with WSDAPI Troubleshooting
- Troubleshooting the Add Printer Wizard
- Troubleshooting WSDAPI Applications
Build date: 11/17/2013