If I switch back to the Innuos switch it works again. I was hoping that Ansuz fixed the problem with Gen3…
You may want to start a new thread on this (and link to it here), as this thread is about non-audiophile switches i.e. someone simply looking for a port replicator.
That must be hugely frustrating. Keep us posted - wherever!
1 Like
Oh, that’s too bad.
By the way, what mode is your Melco’s “UPnP Compatibility” set to?
Do you happen to have a generic/stock/budget switch anywhere on the premises? If the Innuos works and a generic switch works, I’d be asking for a refund if you can’t get this sorted; you’ve been loyal in sticking with the brand and have the right to be disappointed.
I’m struggling to imagine why any switch would stop UPnP (or anything else for that matter) from working… whatever magic it’s doing to stop noise in its tracks, ethernet should be working how ethernet works and how UPnP works.
1 Like
You might want to read this thread for the history behind this issue with Ansuz Switches;
The problem seems to stem from the lack of support (or testing?) for mDNS (which UPnP depends on).
All switches should support it, yet some appear not to. The most common culprit appears to be some home routers, followed (it seems) by a few high-end switches.
1 Like
Well that’s really too bad. Looks like Ansuz is continuing to OEM that crappy $20 D-Link DGS-108 Switch 
That said, there are a couple of possible technical work-arounds though.
The simplest is to install an “IGMP Snooping Querier” on that LAN segment; it will periodically send out an IGMP general query to all hosts which will then elicit an IGMP responses from both your UPnP Server and the dCS, thus preventing the Switch from timing-out and filtering multicast packets on any port.
There used to be an IGMP Querier software package for Synology, but it’s no longer maintained and I doubt it works with the current DSM.
The next option would be to add yet-another-Switch on you LAN, one that support IGMP Querying, like the Netgear GS108Tv2, but that’s a managed Switch, and you’d need to know what you’re doing…
All in, that’s jumping through big hoops just to band-aid a bad product. 
3 Likes
Funnily enough, I read the other day someone saying that IGMP Snooping should be turned off to prevent it breaking things like UPnP.
This doesn’t appear to make sense given that it exists (I thought) to help with not hinder multicast traffic (but, then, many things have been invented to make life easier with unintended consequences!).
Not quite actually; IGMP Snooping was designed to help prevent layer2 Switches from having to flood all ports with multicast traffic by snooping the layer3 IGMP packets to know which port are actually participating in multicast groups, and filtering out multicast traffic for all other ports.
It’s becoming less and less important these days for consumers as folks migrate towards unicast video services (i.e. Netflix etc).
1 Like
But it shouldn’t actually break multicast while doing so 
I guess it’s one of those well intentioned proposals!
It doesn’t, normally.
A proper Switch with configurable IGMP Snooping usually has configurable timeouts to ensure applications that rely on some aspect of multicast doesn’t break. Managed Switches which have it On by default, usually have appropriate timeouts that avoid breaking applications like UPnP.
Unfortunately, it seems the unmanaged D-Link GS-108 used by Ansuz is just rubbish.
That’s interesting, as I was beginning to wonder whether Ansuz were actually using a managed switch for the innards and had set it up incorrectly.
The Ansuz must sound substantially better than the PhoenixNET if @T38.45 is going to persist in sorting this.
Many thanks for responses- appreciate folks!!
Ok, yes - the SQ is superior, it’s the best switch I had for testing (I had Melco, innuos, Cisco, Ansuz, some cheap other vendors as well…). And yes, it seems that they’re still using the D-Link engine. So the IGMP problem is not fixed (I hoped they would fix it with Gen3.)
I would compare their approach with a DAC vendor- many DAC vendors are using ESS chips but their DACs sound all different because the chip is one part of the chain. Powersupply, filter, clocking etc is very important too. Look f.ex. what Audio Note or Naim are doing (very old chips…).
So here the point that drives me nuts- it seems that one or two folks here got that switch up&running in a dCS setup…
Again- thx! I will send the switch back again…
Interesting re SQ, I’ve always considered the PhoenixNET the one to beat but have yet to hear an Ansuz. Not sure I buy the Tesla coils thing but they’re clearly doing something right to your ears!
Agreed. Far more to a switch than the board. Or there damned well should be if it attracts the audiophile tax!
Whoa. Don’t rush. If this is true, you need to do some sleuthing. Obviously there is something, er, special about the Ansuz which means it doesn’t work with UPnP for you while other switches do; on the other hand, if other folk have the A2 or A3 working in their dCS setups then why doesn’t yours work? There must be something somewhere in your network/topology which is different from theirs. Have you investigated?
If you really do like the switch so much, you basically have to make it work with UPnP or settle for an inferior (to your ears) non-Ansuz switch. I’d personally exhaust the first of these.
Good luck, whatever.
2 Likes
Indeed Nigel, I had a call with a customer (my dealer initiated). He runs AVM/Fritzbox as well with a Mcintosh amp, Bartok and Ansuz A2 switch but he’s using a Mac with upnp service on it- maybe that’s reason why the upnp service/server is always visible (Mac is permanently broadcasting ?)
Anyway- If you can try to listen to an A3 or even better a D3 
1 Like
I don’t know if this is helpful but I had some trouble initially with my Ansuz D2 Powerswitch but it was due to a failing ATT router. The Powerswitch actually worked very well with the Rossini Apex.
1 Like
Thanks Lee- does it mean you’re running Rossini + dnla/upnp? What NAS server do you use!
Tx!
Well, unlike analog components, “fine tuning” the PSU and Clocking sections are relatively insignificant to an Ethernet Switch functioning as it should.
Fact is, Ansuz uses the entire D-Link Ethernet Switch board, not just a chip or “engine”, even to the point of pasting a sticker to cover D-link’s PCB labels. It’s just absolutely hilarious 
That said, doesn’t Ansuz have any support channel to properly address this issue? Have you asked them directly about this? (Although, from what I’ve seen, I suspect Ansuz doesn’t have the expertise to properly address or fix this).
@Anupc Looking at the Ansuz website, it would appear they’re using something similar to either a bank of modified inductors or transformers to clean up the power (it’s difficult to tell).
What do you make of these components? I’m not sure I’ve seen anything quite like them (similar, but not the same).