This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About samzor
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About samzor
03-31-2020
2Posts
0Likes
0Solutions
Mar 31, 2020Last Visited
User
Activity
User
Profile
Latest posts by samzor
| Subject | Views | Posted |
|---|---|---|
| 1672 | 03-21-2018 02:27 PM |
User Badges
Community Statistics
| Member Since | 03-17-2018 03:06 PM |
| Date Last Visited | 03-31-2020 01:08 PM |
| Posts | 2 |
03-21-2018
02:27 PM
Hello, My problem is that the Spotify connect features with sonos use mDNS with multicast 224.0.0.251 to discover device. I have multicast rules forChromecast already, it's working successfully and it use also the same address, so I'm wondering why it's not working with spotify. When looking in wireshark the "drop", I see the packet outgoing but never come, It looks like the firewall is not sending it to the correct VLANs, so why with chromecast it's working ? Another weird things, when initializing the spotify connect to a device in the same vlan as sonos, the sonos is appearing in the spotify application in both the one in the VLAN and the one in the other VLAN. I have this error when trying to use as mcast group 224.0.0.251: https://live.paloaltonetworks.com/t5/Management-Articles/Multicast-Configuration-Failing/tac-p/206160#M5290
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
03-31-2020
01:08 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks