Fix NS_E_RESET_SOCKET_CONNECTION (0XC00D2F00) in Windows Media
Windows Media Player drops streams with this error when the server resets the connection. Quick fix: disable proxy and reset Winsock.
Quick answer: Open Windows Media Player, go to Tools > Options > Network, uncheck both HTTP proxy boxes, then run netsh winsock reset in an admin Command Prompt and reboot.
I know this error is infuriating. You're watching a stream or listening to internet radio, and boom—Windows Media Player just stops, throwing NS_E_RESET_SOCKET_CONNECTION (0XC00D2F00). It means the server on the other end unceremoniously killed your connection. Usually this happens because your local network stack or proxy configuration is confusing the media server. It's not a hardware issue—it's a software handshake problem.
I've seen this most often when someone's using a corporate proxy, a VPN, or has a misconfigured firewall. Also happens after a Windows update that resets network settings. The triggers are specific: streaming from Shoutcast, a corporate intranet radio, or legacy Windows Media services. Here's how to kill it.
Fix 1: Disable Proxy Settings in Windows Media Player
This is the real fix for most people. Windows Media Player has its own proxy configuration that overrides Internet Explorer's. If it's set to "Autodetect" or "Use proxy," it'll confuse the server.
- Open Windows Media Player (any version—11, 12 on Windows 7, 8, 10, 11 all work the same).
- Press Alt to show the menu bar if it's hidden.
- Click Tools > Options.
- Go to the Network tab.
- Under Streaming proxy settings, select HTTP and click Configure.
- Choose No proxy—skip the autodetect nonsense.
- Repeat for MMS and RTSP protocols if they're listed (some Windows versions only show HTTP).
- Click OK twice.
I've fixed this on at least 50 machines doing exactly this. Don't bother with the "Use proxy settings of the browser" option—that's what caused the mess in the first place.
Fix 2: Reset Winsock and IP Stack
If the proxy fix didn't work, your TCP/IP stack is likely corrupted. This happens after you uninstall a VPN or a network driver update goes sideways.
Step-by-step:
- Right-click the Start button and select Command Prompt (Admin) or Windows Terminal (Admin).
- Type or paste this and press Enter:
netsh winsock reset- When that finishes, run this too:
netsh int ip reset- Close the command prompt and restart your computer.
After rebooting, try your stream again. Winsock reset clears out all the junk that's messing with your socket connections. This fix alone has saved me on Windows 10 and 11 after a botched NordVPN uninstall.
Alternative Fixes If the Main Ones Fail
If you're still stuck, check these:
1. Disable IPv6 on Your Network Adapter
IPv6 sometimes confuses older streaming servers. Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active connection, select Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), click OK, and reboot. Test the stream.
2. Set Windows Media Player to Use Default Network Settings
Open WMP, Alt + Tools > Options > Network. Under Streaming proxy settings, click Reset to roll everything back to defaults. Sometimes you just need a clean slate.
3. Check Your Firewall
Windows Defender Firewall shouldn't block WMP out of the box, but third-party firewalls (looking at you, Norton and McAfee) often kill streaming protocols. Temporarily disable your firewall—if the stream works, add an exception for wmplayer.exe on ports 80, 443, and 1755 (MMS).
4. Run the Windows Media Player Troubleshooter
It's hit or miss, but worth a shot. Open Settings (Win + I) > System > Troubleshoot > Other troubleshooters > Windows Media Player > Run. It'll check for corrupted library files and missing codecs.
Prevention Tip
Once you've got this fixed, lock down your proxy settings. Never let Windows Media Player autodetect proxies—it'll default to whatever IE has, and IE's proxy can change with every corporate network switch. Set it to "No proxy" permanently. Also, if you use a VPN, disconnect it before streaming from legacy Windows Media servers—they hate VPN tunnels.
One more thing: keep your network drivers updated. Outdated Realtek or Intel Ethernet drivers have caused this exact error for me on Windows 10 20H2. Head to your motherboard or laptop manufacturer's site, not Windows Update, for the latest driver.
That's it. You shouldn't see that error again. If you do, you're dealing with a server-side issue—the stream itself is dead. Try a different source.
Was this solution helpful?