Sonos has moved to http share on port 3445 to avoid SMB1

[edsyl]

I was having issues with re indexing my Music share on my Desktop, and had some communications with Sonos about this.
They had to go to http share because of the SMB1 deprecation and the move away from same by Microsoft.

My question is that since the speakers are on my private internal network, what would the router close the port? Or is it a requirement to open it for any custom port required?
I am probably missing something obvious.
Thanks and Cheers
Ed

 

[ColinTaylor]

what would the router close the port?

 

[edsyl]

Well my understanding is that all external network access to the ports would be closed, but should be passed as part of the internal LAN?
My port scanner shows that it closed to the router and speakers all within my private network.

Correct me if I am wrong in my assumptions??

 

[ColinTaylor]

Yes, this port is only used on your local network by Sonos and therefore has nothing to do with the router. If you're having trouble accessing your music check the firewall settings on that device, e.g. Windows Firewall (not the router).

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

 

[edsyl]

Yes, this port is only used on your local network by Sonos and therefore has nothing to do with the router. If you're having trouble accessing your music check the firewall settings on that device, e.g. Windows Firewall (not the router).

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

Thanks for that.
The instructions are incomplete.
I had to create a rule in Defender to allow the Sonos index service access to port 3445. Port scans now work fine, nothing closed on that port in my private network.
Thanks for the assist, you pointed me to the right port in the storm....so to speak...lol