Mosaic: No UPnP servers available

Hi,
I would like to report that, suddenly, my Mosaic app doesn’t find my servers on my Synology NAS, with the message: No UPnP servers available.
I checked my NAS configuration and my router and everything is correct, UPnP is enabled.
I rebooted my Bartok, router and NAS several times without success.
I can see my servers (MinimServer and Asset UPnP), I see them in Explorer (Windows) and Finder (Mac), I can log to my Bartok with its IP adress, no problem.
I can easily access to my Qobuz and Tidal libraries in Mosaic.

I really don’t know what to do next fix this problem with Mosaic not seeing my server.

Thank you for your help

Gilles

Checking the archives, one similar issue turned out to be that the user’s NAS had inadvertently been put into sleep mode. Check that this is not the cause of your problem.

Unfortunately not, my NAS is live,
up and running

Then maybe try dCS themselves for help:

[email protected]

Thanks Pete, I’ll do.

1 Like

I am convinced that this is the same problem I have. Reported to DCS when firmware 513 for the ethernet card built into the DCS Rossini appeared. Currently the solution is to downgrade to the previous version. We are still waiting for a solution. You are another person with this problem. There are not many of us so it is probably a low priority bug.

2 Likes

You are right.
I had to downgrade to get access to my UPnP servers on my NAS.
We are surely a lot using UPnP servers for local music files, no?
Why is the newest network board version wouldn’t use UPnP protocol?

It still uses UPnP. However, as I understand it at the moment (and I could be wrong :laughing:), the way that a UPnP Server is first discovered on the network changed from the UPnP Control point to the UPnP Renderer instead.

And this change appears to be a problem in a “handful” of cases. Majority of user’s networks don’t have any issue with the apparent change. Unclear what drove the change, or why it’s a problem in some networks.

1 Like

Thanks Anup for the info.
It would be great to know what can be done or changed to be part of the majority of users who don’t have any issue with the new Network board version.

Did you contact support at dCS as discussed earlier?

Yes, I did. Someone from the support team is very helpful to solve the problem.

1 Like

If the problem was replicable, it’d be easy to figure a fix. I think the issue is that it hasn’t been replicable outside of the specific individuals encountering the problem.

And even in those cases, I suspect reverting to the older firmware was a quick “band-aid fix” rather than a root-cause analysis as networking issues can be notoriously hard to troubleshoot, especially if it’s in someone else’s home :laughing:

Out of curiosity, what brand/model is your Router? And did you mean UPnP is enabled on the Router? It should be disabled on the Router actually. Otherwise, depending on the Router, it could quite possibly interfere with the Bartok discovering your UPnP Servers.

I agree with you that it’s difficult to find the root of the problem. For my part, the loss of my UPnP servers appeared only a few days ago, well after the Network board 513 update version. However, with version 511, everything works fine.

Where does the problem come from then?

I use the Internet provider Bell router (HomeHub 2000). The UPnP function has always been activated on my router for years and I have never encountered a connection problem. I deactivated it recently to see if it could be the cause, but without success.

Fortunately, with version 511, it currently works but I would like to be able to keep the Bartok versions updated without this UPnP problem.

Hard to say really, but typically something must have changed in the network environment.

A quick google search suggests that the Home Hub’s firmware gets updated automatically over the network. Any idea if that happened lately? (Are your Bartok and Synology both directly plugged into the Home Hub 2000?)

Thanks Anup for the Google search.
I don’t know if my Internet service provider have updated the router’s firmware lately, I’ll try tio get the information.
Yes, my Synology and my Bartok are connected directly to the Home Hub 2000 router.
Soon, I’ll update back the Bartok to the 513 version to see what happens…

Did you have this UPnP discovery problem since the launch of the 513 version a year ago and run the 511 version since then?

Fortunately no, I haven’t had any issues with 513, UPnP or otherwise, but I did notice an apparent change in how things work when I looked closely after the initial reports of issues with it;

I’m trying to find a solution! :grinning:
When you say you noticed an apparent change in how things work, can you clarify what you noticed.
Is there a link with what you said earlier about the way that a UPnP Server is first discovered on the network changed from the UPnP Control point to the UPnP Renderer instead. Does this mean that it changed from the Mosaic app (or the router?) to the Bartok? This could help me find the culprit !
Thanks again…

I meant at the network protocol level (via Wireshark).

Yes. Though, it’s not documented on any public posts/threads. Keep in mind this is all from “reverse” engineering what’s going on at the network protocol level :wink:

Browsing the UPnP Server music catalog is still performed directly by Mosaic to the UPnP Server, but it’s given the UPnP Server’s address by the dCS component, as opposed to Mosaic having discovered it for itself.

Early into the Bartok’s boot-up sequence it issues a SSDP Search request (multicast) on the network to identify/locate UPnP Servers. If for some reason that SSDP Search request is lost or not responded to or the response (unicast) is lost, then you’ll get that “No UPnP Server” when you select UPnP on Mosaic as a source.

I can imagine one possible reason for the change; In virtually all cases, Mosaic is running on a device connected to the network via WiFi, which is not always reliable in finding UPnP Servers as some WiFi Access Points have issues with multicast traffic. Whereas the dCS component is typically hardwired to the home network and should have no such issues.

1 Like

It makes perfect sense.
dCS support tells me that the software team is aware of the problem that affect a small number of users and is looking for a solution.
In the meantime, I will continue to search.
I know that I have not added or modified a component on my local network, remains to be seen if a firmware update somewhere (router) may have caused the problem and I’ll continue using the 511 version meanwhile to get access to my local music (UPnP servers).
Thanks again Anup for your help.

1 Like