NS_E_SERVER_NOT_FOUND (0XC00D0035): Real Fixes for Windows Media Streaming

1. Windows Firewall Is Blocking Media Streaming

This is the #1 cause I see. Windows Firewall treats media streaming like a security risk, so it blocks the ports that Windows Media Player and Media Center use to find servers. The error pops up when you try to play a file from a network share or a streaming server — your PC simply can't see it.

Had a client last month whose entire home theater setup died because Windows Update flipped a firewall rule. Took me five minutes to fix. Here's how:

1. Open Control Panel (search for it, don't use the Settings app — that's for basic stuff).
2. Go to Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
3. Look for Windows Media Player and Windows Media Center in the list. If they're not there, click Change settings then Allow another app and browse to C:\Program Files\Windows Media Player\wmplayer.exe and C:\Program Files\Windows Media Center\ehshell.exe.
4. Make sure Private is checked for both. Don't check Public unless you're on a trusted network — that's asking for trouble.
5. Click OK and test the stream.

If that doesn't work, open Windows Defender Firewall with Advanced Security. Look for Inbound Rules and filter by Protocol: UDP. You should see rules for Windows Media Player Network Sharing Service on port 10243-10245. If they're disabled, enable them. This is the port range Windows uses for streaming — block it, and you get 0XC00D0035 every time.

2. Network Discovery and UPnP Are Off

Windows Media Player relies on network discovery and UPnP to find servers. If you turned them off for security or battery life, the error shows up. This is especially common on Windows 10 laptops that switch networks a lot.

I've seen this on a Dell XPS 13 running Windows 10 22H2 — the user couldn't stream from their NAS. Network discovery was off because Windows tagged the network as Public. Here's the fix:

1. Open Settings > Network & Internet > Wi-Fi (or Ethernet). Click on your network name.
2. Set Network profile type to Private. If it's Public, streaming won't work.
3. Go to Control Panel > Network and Sharing Center > Advanced sharing settings.
4. Under Private, turn on Network discovery and File and printer sharing. Also check Turn on automatic setup of network connected devices — that's the UPnP toggle.
5. Now open Services (type services.msc in Run). Find these two:

• UPnP Device Host — set to Automatic and start it.
• SSDP Discovery — set to Automatic and start it. This is the service that finds UPnP devices on your network.

After that, restart Windows Media Player. The server should appear. If it doesn't, check your router's UPnP settings — some routers have it disabled by default. Log into your router (usually 192.168.1.1 or 192.168.0.1) and look for UPnP under Advanced settings.

3. Media Streaming Options Are Misconfigured in Windows

If the firewall and network discovery are fine, the problem is often that Windows isn't configured to stream media at all. This happens when someone disabled the Media Streaming feature or set it to a different network.

Here's the fix:

1. Open Control Panel > Network and Sharing Center > Media streaming options (it's a link at the bottom left).
2. Click Turn on media streaming. Windows will ask you to name your media library — call it something identifiable like "Living Room PC".
3. Under Show devices on, select All networks (or the specific network you're trying to stream from).
4. Click OK and then go to Choose default settings. Make sure Use default settings is selected — don't overcomplicate it.

If you're using Windows Media Player 12 (the version in Windows 7 through 11), also check this:

• Open WMP, press Alt to show the menu, go to Tools > Options > Network tab.
• Under Streaming protocols, make sure Multicast and UDP are checked. HTTP is fine too, but the error usually involves UDP.
• Under Multicast streaming, select Use default proxy settings or No proxy — don't set a proxy unless you know what you're doing.

I've seen cases where a corporate VPN turned on a proxy setting and caused this error. If you're on a VPN, disconnect and test. If the error goes away, you know the VPN is the culprit.

Quick-Reference Summary Table