| Previous | Next |
| NS_E_UDP_DISABLED | NS_E_HTTP_DISABLED |
NS_E_TCP_DISABLED
NS_E_TCP_DISABLED — 0xC00D00D2
Why no TCP connection is attempted
NS_E_TCP_DISABLED means TCP is not enabled for the requested Windows Media path. It is a configuration/selection result: a socket connect failure would be a different boundary because this result can occur before TCP is attempted.
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 URL/request and the transport-selection decision that chose TCP.
- Record the server or publishing-point setting that disables TCP and its configuration generation.
- Check whether the client is allowed to fall back to another enabled protocol or explicitly requires TCP.
Enable TCP intentionally or select an enabled transport, then repeat the identical request. Do not troubleshoot DNS, SYN/SYN-ACK or socket timeouts until logs show that a TCP attempt actually begins.
Verification
Confirm the same request reaches TCP connection/negotiation when TCP is enabled, and that a deliberately disabled configuration still returns this code without a connection attempt.
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.