| Previous | Next |
| NS_E_NOREGISTEREDWALKER | NS_E_NO_LOCALPLAY |
NS_E_NOFUNNEL
NS_E_NOFUNNEL — 0xC00D000C
Diagnosing NS_E_NOFUNNEL
NS_E_NOFUNNEL identifies this Windows Media Services boundary: there is no data connection established.
Why this boundary matters
This HRESULT belongs to a specific network or control-path stage. Keep the resolved endpoint and selected protocol fixed, and preserve the first socket/protocol result so DNS, connection, negotiation, response parsing and media delivery are not collapsed into one generic network failure.
Evidence to collect
| Field | What to preserve |
|---|---|
| Peer | Resolved server/peer endpoint and the protocol actually selected for the request. |
| Stage | Last completed stage: resolution, connection, control exchange, response parsing or media delivery. |
| Transport result | First socket/protocol status, timeout/reset indication, and byte counts when data transfer started. |
| Intermediaries | Proxy, gateway or second Content Server involved in the same path, including its identity. |
Decision rule
Keep endpoint and protocol fixed while changing one network precondition; a later socket or parser result is a new boundary and should be diagnosed separately.
Focused test
Record the session and expected data connection, including the control connection that should create it. Verify that the data channel is established before retrying media delivery.
Verification
Repeat the same request to the same endpoint with the same selected protocol. Confirm it passes the previously failing network stage; if it advances and fails later, diagnose the later socket/protocol result separately.
Technical references
- System control protocol plug-ins
- Microsoft Media Server protocol
- WMS HTTP proxy interaction
- Microsoft HRESULT values for the Windows Media namespace
Looking for a different code? Search another status or error code.