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 |
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.