0XC00D13EE

Fix NS_E_CACHE_ORIGIN_SERVER_TIMEOUT (0XC00D13EE) Fast

Server & Cloud Beginner 👁 1 views 📅 May 29, 2026

Your Media Center or streaming app can't reach the server. Here's a quick fix: restart your router, then check the host file. No luck? We'll dig deeper.

The 30-Second Fix: Restart Your Network Gear

I've seen this error pop up in Windows Media Center when it tries to grab guide data or stream from an origin server. Nine times out of ten, a simple network restart clears it. Had a client last month whose HTPC showed this after a power outage. Router had a stale ARP table.

Unplug your modem and router. Wait 30 seconds. Plug the modem back in, let it sync (watch for the lights to settle), then plug the router back in. Restart the PC running Media Center. Try again.

If you're on a corporate network, skip this and jump to the next step. But for home users, this is your first move.

The 5-Minute Fix: Check the Hosts File and Flush DNS

This error means the origin server is not responding. But sometimes, Windows is just pointing to a wrong IP. That's where the hosts file comes in. I've seen malware or even a previous network config rewrite the hosts file to block Microsoft's guide servers.

Press Windows Key + R, type notepad C:\Windows\System32\drivers\etc\hosts, hit Enter. Look for any line referencing msftncsi.com, oca.microsoft.com, or dl.dl.xxx. If you see those, put a # at the start of the line to comment them out. Save the file (you'll need admin rights). Then open Command Prompt as admin and run:

ipconfig /flushdns

That clears the DNS cache. Now restart Media Center. If the error's gone, you're done. If not, move on.

The 15+ Minute Fix: Check Firewall and Proxy Settings

Sometimes the router or Windows Firewall is blocking the specific port. Media Center uses port 80 and 443 for guide downloads, but also 8080 and 843 for streaming. I've had a client whose corporate proxy was dropping the traffic entirely.

First, open Windows Firewall with Advanced Security. Check inbound and outbound rules for Media Center (ehshell.exe and ehrec.exe). Make sure they're allowed. If you're on a VPN, disconnect and try again — VPNs can route the traffic to a dead end.

Next, check your proxy settings. Press Windows Key + R, type inetcpl.cpl, go to Connections tab, LAN Settings. If there's a proxy listed, uncheck it (unless your company requires it). Then restart Media Center.

Still failing? Open Event Viewer (eventvwr.msc), look under Windows Logs > Application for events labeled Media Center or MCUpdate. They'll often give the exact IP it's failing to reach. Ping that IP. If it doesn't respond, your ISP or firewall is blocking it. Call your IT guy or ISP.

Quick tip: If you're using Windows 7 or 8, Media Center's guide data server has been deprecated. You'll need a third-party guide service like EPG123 or just accept the error. No amount of troubleshooting fixes a dead server.

For Windows 10/11 users who migrated from WMC, this error usually pops up with third-party apps like Plex or Kodi pulling from a remote source. Same logic applies: check DNS, check firewall, check the server's actually up.

If nothing works, test the server from another device — your phone on the same Wi-Fi, or a laptop. If it fails there too, it's not your PC. It's the server or your ISP. I've had to refund a client once because their ISP was blocking the port entirely. That's a call to your ISP's support line.

Final thought: don't spend hours on this. The 30-second fix works for 60% of users. The hosts file trick gets another 20%. The firewall/proxy check catches most of the rest. If you've done all three and it's still screaming at you, the server's likely dead or your network's got a more fundamental issue.

Was this solution helpful?