Troubleshooting Function Discovery Clients
Function Discovery clients:
- Always use UDP WS-Discovery for device discovery
- Always initiate HTTP or HTTPS connections for metadata exchange
- Sometimes use directed discovery
- Sometimes use a secure channel (HTTPS) for metadata exchange
The following list shows the typical sequence of messages sent and received by Function Discovery clients. Not all messages are mandatory.
- The client sends a Probe message to discover devices and services. If the client is using directed discovery then this message is sent over HTTP or HTTPS; otherwise, the message is sent by UDP multicast to port 3702.
- The client receives ProbeMatches messages from matching devices or services. Directed discovery messages are sent over HTTP or HTTPS; otherwise, these messages are sent by UDP unicast and originate from port 3702.
- If no XAddrs were included in the ProbeMatches message, then the client will send a Resolve message by UDP multicast to port 3702.
- If a Resolve message was sent, then the client receives a ResolveMatches message from matching services. This message is sent by UDP unicast from port 3702 to the port where the Resolve message originated.
- The client sends a Get message to request metadata from the device or service. This message is sent by HTTP or HTTPS.
- The client receives a GetResponse message with the device or service metadata. This message is sent by HTTP or HTTPS.
The following diagnostic procedures should be used (in order) to help identify problems with a Function Discovery client.
To troubleshoot a Function Discovery client
- If directed discovery is used, troubleshoot directed discovery.
- Inspect adapter and firewall settings.
- Use a generic host and client for UDP WS-Discovery.
- Use WSD Debug Client to verify multicast traffic.
- Inspect network traces for UDP WS-Discovery.
- Use a generic host and client for HTTP metadata exchange.
- Use WinHTTP logging to verify Get traffic.
- Inspect network traces for HTTP metadata exchange.
- 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.
Build date: 11/27/2012