Spotify Connect Network Interface Prioritization (updated)

desentizised — Fri, 30 Jun 2017 17:05:42 GMT

So I've had this problem with my Sonos speakers not showing up in Spotify for Windows. Reached out to Sonos Support on their community forums where a representative pinpointed the problem to my VPN. When I disconnect from VPN the Sonos speakers show up in Spotify.

So my question is this then: Is there any way to tell Spotify to prioritize my LAN over the VPN or outright ignore the VPN for Network Discovery of remote speakers and stuff? Right now all I can really do is work around the problem by not having the VPN connected when starting the Spotify client.

Thanks in advance.

edit 30th of June 2017:

So I've been in direct contact with Spotify right now and after some initial confusion about what I actually mean by VPN the conclusion seems to be that Spotify for Windows just behaves the way it does and there's nothing I could influence about it as the end-user. So I've been told that my issue would be passed on including a link to this forum-post here.

One additional thought I had during that live-chat was that the reason why Spotify is preferring the VPN over my LAN might be because the VPN has the more common 192.168.1.0/24 subnet while my LAN (which the Sonos-Speakers are wired to) has 192.168.9.0/24. So this is just a thought on why Spotify for Windows behaves the way it does.

Either way I'd say there's no reason for it to behave like that when there are multiple active network-interfaces. It should either be checking all of them or make the educated guess that a physical network-connection is probably more likely to have relevant devices on it than a virtual one.

Live-chat transcript attached in the interest of full disclosure.

topic Spotify Connect Network Interface Prioritization (updated) in Desktop (Windows)

Spotify Connect Network Interface Prioritization (updated)