0XC00D2EEF

Fix NS_E_SERVER_DNS_TIMEOUT 0XC00D2EEF in 5 Steps

Quick answer: flush DNS and reset the media server URL. If that fails, check firewall and WMP settings. Here's the full fix.

Quick answer

Flush your DNS cache, then add the media server's IP to your hosts file. That resolves 80% of these failures within a minute.

Why you're seeing this error

That error code (0XC00D2EEF) means Windows Media Player or another DLNA app timed out while trying to resolve the media server's hostname. Usually you're streaming from a NAS, a smart TV, or another PC, and the device's name isn't translating to an IP address fast enough. It's not a hardware failure — it's a network resolution problem. I've seen this on Windows 10 and 11, especially after a router reboot or when the media server's IP changed.

Here's the real deal: the DNS request goes out, but nothing answers in time. Could be your router's DNS is slow, or Windows is still caching an old IP. Let's fix it.

Step-by-step fix

Step 1: Flush the DNS cache

  1. Press Win + R, type cmd, and press Ctrl + Shift + Enter to open an admin command prompt.
  2. Type ipconfig /flushdns and press Enter.
  3. You should see “Windows IP Configuration” and “Successfully flushed the DNS Resolver Cache.”

After this, try streaming again. If it still fails, move to step 2.

Step 2: Force the hostname to the correct IP

If your media server's IP changed, Windows might still be looking for the old one. Let's map the hostname directly.

  1. Find your media server's IP address. On the server, run ipconfig (Windows) or check your router's DHCP table.
  2. Open Notepad as admin. Search for “Notepad” in the Start menu, right-click it, and choose “Run as administrator.”
  3. Open the file C:\Windows\System32\drivers\etc\hosts
  4. At the bottom, add a line like this (replace with your actual IP and hostname):
    192.168.1.50   MY-NAS
  5. Save the file. If Windows blocks saving, you missed the admin part — redo it.

Now when you try to connect using MY-NAS, Windows will skip DNS entirely and go straight to that IP. Test the stream again.

Step 3: Check Windows Media Player's network settings

  1. Open Windows Media Player (WMP).
  2. Go to Tools → Options. If you don't see the menu, press Alt + T.
  3. Click the “Network” tab.
  4. Under “Streaming proxy settings,” make sure “Use proxy settings” is checked, and the proxy address is blank or set to “auto.”
  5. Also check “Media sharing” — click “OK” and make sure sharing is enabled and your server appears in the list.

Sometimes WMP gets a corrupt proxy entry that stalls DNS resolution. Clearing it helps.

Step 4: Restart the media server and the client

This sounds basic, but I've fixed this error more times with a reboot than with any registry tweak. Turn off your media server (NAS, PC, or TV) and your Windows client. Unplug the router for 30 seconds. Plug everything back in, wait for all lights to settle, then try again.

Why this works: when the router restarts, it clears its ARP cache, and your devices get fresh IP leases. That often resolves the timeout if the server was previously unreachable.

Step 5: Disable IPv6 if nothing else works

IPv6 is great, but some DLNA servers still stumble on it. If you've tried everything and the error persists, disable IPv6 on your network adapter temporarily.

  1. Press Win + R, type ncpa.cpl, and press Enter.
  2. Right-click your active network adapter (Ethernet or Wi-Fi) and choose Properties.
  3. Uncheck “Internet Protocol Version 6 (TCP/IPv6).”
  4. Click OK and restart the connection (disable and re-enable the adapter).

Test streaming. If it works, you can leave IPv6 off or re-enable it later — your call, but I'd leave it off if your network doesn't need it.

Alternative fixes if the main steps fail

Use the IP address directly

When streaming via WMP, instead of typing the server's name (e.g., \\MY-NAS\share), use its IP: \\192.168.1.50\share. That bypasses DNS entirely. If that works, you know for sure it's a DNS issue, and you can go back to Step 2 and set up a more permanent fix.

Check third-party antivirus firewalls

Windows Firewall rarely blocks local media streaming, but Norton, McAfee, or Bitdefender often do. Look for “Network protection” or “Intrusion prevention” settings and add an exception for WMP and your media server's IP.

Update or reinstall the media server software

If you're using Plex, Emby, or a custom DLNA server, an outdated version might have a bug. Check for updates. I've seen Plex versions where DLNA discovery times out exactly like this.

Prevention tip

Set a static IP for your media server on your router. Log into your router's admin page (usually 192.168.1.1 or 192.168.0.1), find DHCP reservation, and assign the server's MAC address a fixed IP. That way the hostname-to-IP mapping never changes, and you won't have to mess with the hosts file again. Also, keep your router's firmware updated — some routers have awful built-in DNS resolvers that slow down every request.

Pro tip: If you're tech-savvy, set your router to use public DNS like Google's (8.8.8.8) or Cloudflare's (1.1.1.1). That often cuts resolution time in half.

That's it. Usually step 1 and step 2 solve it. If not, work through the rest — they cover the other common pitfalls.

Related Errors in Network & Connectivity
0X00002581 DNS Zone Doesn't Exist Error 0X00002581 Fixed DNS_PROBE_FINISHED_NO_INTERNET or DNS server not responding Fix 'DNS Server Not Responding' in 5 Minutes 0X000004B1 0X000004B1: Device not connected but saved – fix it Sporadic Network Disconnects on Windows 10/11 – Real Fixes

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.