Unable to Connect - Corporate Environment

  • 17 May 2018
  • 0 replies
  • 492 views

We're trying to set up a Sonos Connect on a corporate network. The Connect device, as well as the client device (an Android phone) are both on the same SSID, using the same VLAN. We have allowed broadcasts between devices on this network. However, the setup process still fails with the error "Wireless problem ... There was a connection problem...". Some users of this wireless platform (Aruba) report that Sonos uses a set of Service IDs. Here's what I've got so far:

id "urn:schemas-upnp-org:service:VirtualLineIn:1"
id "urn:schemas-upnp-org:service:GroupRenderingControl:1"
id "urn:schemas-sonos-com:service:Queue:1"
id "urn:schemas-upnp-org:service:GroupManagement:1"
id "urn:schemas-upnp-org:service:ZoneGroupTopology:1"
id "urn:schemas-upnp-org:service:SystemProperties:1"
id "urn:schemas-upnp-org:service:DeviceProperties:1"
id "urn:schemas-upnp-org:service:AudioIn:1"
id "urn:schemas-upnp-org:service:MusicServices:1"
id "urn:schemas-upnp-org:service:AlarmClock:1"
id "urn:smartspeaker-audio:service:SpeakerGroup:1"
id "urn:schemas-upnp-org:service:ConnectionManager:1"
id "urn:schemas-upnp-org:service:ContentDirectory:1"
id "urn:schemas-upnp-org:device:ZonePlayer:1"
id "urn:schemas-tencent-com:service:QPlay:1"
id "urn:schemas-upnp-org:service:RenderingControl:1"
id "urn:schemas-upnp-org:service:AVTransport:1"

However, the app still doesn't find the Connect.

Are there any more IDs that are required?

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.