Skip to main content
Answered

Cannot connect to WMP library from laptop to all Sonos players. Affects FLAC files only.

A
  • Anonymous

This is probably the weirdest issue out there on this community page. Long post.

TL;DR: Need to know what firewall rule to edit for Sonos Library service to work. Am too scared to yeet my own connection.

So, since about less than a week ago, I recently acquired (hint: sail the high seas) some Free Lossless Audio Codec files of the Call of Duty: Modern Warfare (2019) OST. Of course, I was interested in hearing the differences between the 320kbps MP3 and the 44.1kHz 16-bit FLAC files I had on my hard disk drive.

My laptop and all Sonos devices are connected via several Ethernet cables to the router via a 24-port network switch. It cannot be my router.

On my laptop, I first used the Sonos Win controller. I received this error code in the Windows Sonos controller.

“Saturday, May 15, 2021 - 1:44 PM Canberra, Melbourne, Sydney
Unable to play 'Into the Furnace' - unable to connect to 192.168.0.54:10246.”

That local IP address is my laptop (confirmed by accessing router’s device list).

Alright, let’s try Windows Media Player’s Cast to Device. That should work, right? Wrong.

I got this error.

Unexpected device error.

An unexpected device error occurred. Restart the device and try again.

If you can’t resolve the issue, a device update may be required. Please contact the device manufacturer for the latest updates.

HRESULT: 0xc00dc3b6

Alright, time to check Google.

The above device error corresponds to this: https://windows-hexerror.linestarve.com/0xC00DC3B6

DLNA_E_RENDERER_FAILED_TO_PLAY: The Media Renderer failed to play the content.%0

I restarted my Playbar unplugging the double-barrel power cord. Waited 1 minute, replugged in, white light was seen. Showed in Win and Android controllers.

Right, so let’s see if it’s a Sonos issue or my lappy. I copied those same FLAC files and dumped them in my phone’s SD-card. I played the same songs on the Playbar from the Android controller (On this Mobile Device) and what the fook, those songs played as intended. I heard the full song for confirmation. No error codes popped up.

Now, how do I fix this?

I checked this support article: https://support.sonos.com/s/article/688?language=en_US

Yeah, that looks right, it’s a firewall issue on Windows 10. No idea how to proceed from there.

Best answer by Anonymous

Update: I fixed the issue. Very poggers!

I re-wrote and wrote two Windows Firewall rules using the ports mentioned here from https://support.sonos.com/s/article/688?language=en_US

In Windows Firewall with Advanced settings, I first went to Inbound rules.

I rewrote the rule for SonosLibraryService.

Under the Properties, I wrote this for the Ports and Protocols tab. Click on Protocol Type and click on UDP. Select local ports (= your connection between your Win machine, your router and your Sonos device, this should not affect your actual internet connection!).

This is what I wrote for the UDP section: 136-139, 1900-1901, 2869, 5353, 6969, 10243, 10246, 10280-10284 (copy and paste, the 10246 port was added because Sonos could not connect to that particular port for FLAC playback, if you don’t play/use FLAC files, it may not be necessary).

Again, for the TCP ports, I created a new rule, still labelled it as SonosLibraryService.

The TCP ports: 80, 443, 445, 3400, 3401, 3445, 3500, 4070, 4444.

Happy listening! I’m posting my answer to the r/Sonos community.

View original
Did you find what you were looking for?
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

3 replies

James L.
Forum|alt.badge.img+17
  • James L.
  • Retired Community Staff
  • 1058 replies
  • May 20, 2021

Hey @Noobgamer0111, welcome to the community.

 

If you’re only running Windows 10’s firewall then we have a detailed guide specifically for this. The changes aren’t massive and very unlikely to change how anything else functions. Once you’ve completed those steps, in the Sonos desktop controller, go to Manage → Update Music Library Now and wait for it to complete, then attempt playback again. If this fails, it would be useful to submit a system diagnostic and get in touch with our customer support team.

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
A
  • Anonymous
  • 0 replies
  • May 20, 2021

Hey @James L. Thanks for the quick reply.

I also checked out that guide before, but it’s not specific enough to know which firewall rule I need to edit/change.

Any updates to the Music library have also not helped.

I’ll chuck this sys diag up: 337164260

Error log dump: 

Saturday, May 15, 2021 - 1:43 PM Canberra, Melbourne, Sydney
Unable to play 'I Want It That Way' - unable to connect to 192.168.0.54:10246.

Saturday, May 15, 2021 - 1:44 PM Canberra, Melbourne, Sydney
Unable to play 'I Want It That Way' - unable to connect to 192.168.0.54:10246.

Saturday, May 15, 2021 - 1:44 PM Canberra, Melbourne, Sydney
Unable to play 'I Want It That Way' - unable to connect to 192.168.0.54:10246.

Wednesday, May 19, 2021 - 1:33 PM Canberra, Melbourne, Sydney
Unable to play 'Party Up' - the connection to 192.168.0.15:10246 was lost.

Wednesday, May 19, 2021 - 1:33 PM Canberra, Melbourne, Sydney
Unable to play 'Party Up' - the connection to 192.168.0.15:10246 was lost.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play the selected item.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 7:58 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 8:02 PM Canberra, Melbourne, Sydney
Unable to play 'Call of Duty®: Modern Warfare (Original Game Soundtrack)' - unable to connect to //Noobgamer0111/Music.

Thursday, May 20, 2021 - 8:13 PM Canberra, Melbourne, Sydney
Unable to browse music

Thursday, May 20, 2021 - 8:14 PM Canberra, Melbourne, Sydney
Unable to browse music

Thursday, May 20, 2021 - 8:14 PM Canberra, Melbourne, Sydney
Unable to browse music

Thursday, May 20, 2021 - 8:14 PM Canberra, Melbourne, Sydney
Unable to browse music

I’m also uploading the text file from the ping test from my lappy to Playbar and vice versa.

C:\Users\Noobgamer0111>ping 192.168.0.3

Ping test (Using standard Command Prompt on Windows 10):

Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time=1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Elevated Cmd prompt:

C:\Windows\system32>ping 192.168.0.3

Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64
Reply from 192.168.0.3: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
From Playbar (using http://192.168.0.3:1400/tools.htm)

running /bin/ping -c 3 192.168.0.15PING 192.168.0.15 (192.168.0.15): 56 data bytes64 bytes from 192.168.0.15: seq=0 ttl=128 time=1.495 ms64 bytes from 192.168.0.15: seq=1 ttl=128 time=0.975 ms64 bytes from 192.168.0.15: seq=2 ttl=128 time=0.940 ms--- 192.168.0.15 ping statistics ---3 packets transmitted, 3 packets received, 0% packet lossround-trip min/avg/max = 0.940/1.136/1.495 ms
A
  • Anonymous
  • 0 replies
  • Answer
  • May 21, 2021

Update: I fixed the issue. Very poggers!

I re-wrote and wrote two Windows Firewall rules using the ports mentioned here from https://support.sonos.com/s/article/688?language=en_US

In Windows Firewall with Advanced settings, I first went to Inbound rules.

I rewrote the rule for SonosLibraryService.

Under the Properties, I wrote this for the Ports and Protocols tab. Click on Protocol Type and click on UDP. Select local ports (= your connection between your Win machine, your router and your Sonos device, this should not affect your actual internet connection!).

This is what I wrote for the UDP section: 136-139, 1900-1901, 2869, 5353, 6969, 10243, 10246, 10280-10284 (copy and paste, the 10246 port was added because Sonos could not connect to that particular port for FLAC playback, if you don’t play/use FLAC files, it may not be necessary).

Again, for the TCP ports, I created a new rule, still labelled it as SonosLibraryService.

The TCP ports: 80, 443, 445, 3400, 3401, 3445, 3500, 4070, 4444.

Happy listening! I’m posting my answer to the r/Sonos community.

Related Topics

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings