Fix WMP Error 0XC00D11C3 (DNS Timeout) Fast

WMP can't resolve the server's DNS name, so it times out before streaming. This usually means your DNS, VPN, or the stream URL is broken, not WMP itself.

Quick answer: Flush your DNS cache, switch to a public DNS like 1.1.1.1, and disable IPv6 in your adapter properties — that clears 0XC00D11C3 for 9 out of 10 people.

I know this error is infuriating. You double-click a stream, WMP thinks for a few seconds, then throws that generic "Windows Media Player cannot play the file because a network problem occurred" dialog. Error 0XC00D11C3 is NS_E_WMP_SERVER_DNS_TIMEOUT, which is Microsoft's way of saying "I asked for the server's IP address and nobody answered in time." The file itself is fine. The player is fine. What's broken is the name resolution between your machine and whatever server is hosting that .wmv, .asf, or MMS stream.

Where does this hit in real life? Classic triggers: you're on a corporate VPN that pushes its own internal DNS and blocks external lookups, you're behind a hotel or dorm captive portal that hijacks DNS, or you're trying to open an old MMS:// URL from a 2005 archive and your ISP's DNS just returns nothing. I've also seen it fire when Windows Update silently reset your NIC to prefer IPv6, and the stream server only publishes A records.

Before you touch anything, confirm it's really DNS and not a dead server. Open Command Prompt and run:

nslookup media.example.com
ping media.example.com

If nslookup says "server can't find" or times out, this article is for you. If it resolves cleanly but WMP still fails, skip to the alternative fixes — you've got a firewall or TLS problem instead.

Step-by-step fix for 0XC00D11C3

Flush your DNS cache. Stale entries are the #1 cause. Open an elevated Command Prompt (Windows key, type cmd, right-click, Run as administrator) and run:
```
ipconfig /flushdns
ipconfig /release
ipconfig /renew
ipconfig /registerdns
```
This takes about 15 seconds. On Windows 10 and 11 that /registerdns call matters because WMP sometimes uses the machine's own name record for the RTSP handshake.
Switch to a known-good DNS resolver. Your ISP's DNS is often the culprit — some block MMS and RTSP lookups entirely. Go to Settings → Network & Internet → your adapter → Edit DNS. Set both IPv4 fields manually:
- Preferred: 1.1.1.1
- Alternate: 8.8.8.8
Cloudflare and Google both resolve legacy streaming hostnames reliably. Reboot, then try the stream again.
Disable IPv6 temporarily. This gets overlooked constantly. In Control Panel → Network and Sharing Center → Change adapter settings, right-click your active adapter, Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). WMP's streaming stack predates IPv6 and sometimes picks an AAAA record that the server never actually serves. Click OK and retry.
Clear the WMP network cache. Close WMP completely, then delete everything inside:
```
%LOCALAPPDATA%\Microsoft\Windows Media\12.0\Network\
```
If that folder doesn't exist, look under %USERPROFILE%\AppData\Local\Microsoft\Windows Media\. Restart WMP.
Check your VPN or proxy. Split-tunnel VPNs love to send only corporate subnets through the tunnel and drop external DNS. Disconnect the VPN entirely and test. If the stream works, your VPN's DNS suffix is the problem — add a public resolver to the VPN adapter, or set WMP to bypass the proxy under Tools → Options → Network → Configure Proxy.
Re-register WMP's networking components. Still failing? Open an elevated Command Prompt and run these one at a time:
```
regsvr32 jscript.dll
regsvr32 vbscript.dll
regsvr32 wmp.dll
regsvr32 wmpdxm.dll
```
Reboot. This rebuilds WMP's stream handlers and clears corrupted DLL registrations that can cause false DNS timeouts.

If the main steps don't work

Try opening the same URL in VLC first. If VLC plays it, WMP's stack is broken and you should just use VLC — no shame in that, it handles MMS and RTSP better than WMP ever did. If VLC also fails with a DNS or connection error, the server is down or your network is blocking port 1755 (MMS) or 554 (RTSP). Test with PowerShell:

Test-NetConnection media.example.com -Port 1755

A TcpTestSucceeded : False result means the port is blocked. That's on the network, not your machine. Call your ISP or switch to a mobile hotspot to confirm.

One more thing people miss: Windows Defender Firewall sometimes flags legacy WMP stream handlers after a major update. Open Windows Security → Firewall & network protection → Allow an app through firewall, find Windows Media Player Network Sharing Service, and make sure both Private and Public are ticked. I've seen this exact error surface after the 22H2 update because the rule got reset to Private-only.

Prevention tip

Pin a reliable DNS resolver permanently and stop letting Windows Update flip your network settings behind your back. Set 1.1.1.1 in your router, not just the PC — that way every device on the network gets consistent lookups and you never chase this again. And if you stream old MMS content regularly, just install VLC and set it as the default handler for mms:// and rtsp:// protocols. WMP is a 2005 tool trying to do 2024 networking, and DNS timeouts are how it tells you it's tired.