| Previous | Next |
| NS_E_TITLE_SIZE_EXCEEDED | NS_E_TCP_DISABLED |
NS_E_UDP_DISABLED
NS_E_UDP_DISABLED — 0xC00D00D1
Why UDP is not used
NS_E_UDP_DISABLED means UDP is not enabled for the selected Windows Media operation. Treat it as transport policy, not as evidence of UDP packet loss, firewall filtering or NAT behavior, because those require a UDP attempt to have occurred.
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 checks
- Record the protocol-selection result and the destination that would have been used for UDP.
- Record the configuration object that disables UDP and whether the client permits fallback to TCP/HTTP.
- Check server logs for absence of a UDP send/bind path at the same request timestamp.
Enable UDP intentionally or select an enabled transport while keeping content and endpoint fixed. If UDP then starts but fails later, preserve that later socket/protocol result as a separate error.
Verification
Confirm an enabled configuration reaches the expected UDP setup/data path and a disabled configuration continues to stop before UDP activity.
Technical references
- Windows Media Services system control protocol plug-ins
- Microsoft Media Server protocol
- Windows Media HTTP proxy interaction
- Windows Media HRESULT values
Looking for a different code? Search another status or error code.