Control point cant see minimserver

[steve.pratt46]

Hi.
I'm having trouble with my control point seeing minimserver.
All had been working fine until i updated to minimserver 0.8.4 update 94.
I also installed JAVA SE embedded 8 on my NAS.
I have Synology NAS DS112+ . I use BubbleUPnp on my android as my control point
I have a BT homehub4 router. Ive tried disabling the 5GHZ network but this do not help.
What happens is occasionally i can see the minimserver on my control point but when i logout and try and re-connect its not seeing Minimserver.
I also have a pioneer streamer which also now is sometimes visible and sometimes not.
My NAS is connected to the LAN via a switch and a DP link homeplug. The router is also LAN connected to same DP link
My streamer is connected to the same switch as the NAS along with TV, play station, freesat box.
My MinimWatch is connecting fine to the minimserver.
I did add 2 more TP link homeplugs about a week ago but all was working fine after that, its just been since the resent software upgrades that Ive been having trouble.
Ive attached latest MinimWatch log.
I suspect its a network issue but not sure what to do.

Thanks

[simoncn]

There wasn't any attachment to your post. However, I don't think the MinimWatch log is likely to show the reason for the problem as MinimWatch is able to see MinimServer.

Homeplugs are notorious for causing problems like this. The best way to debug this kind of problem is to strip down your network to an absolute minimum to establish a configuration that works reliably, then add back your other network components one by one until you find the component that is causing the issue. For example, you could use a long ethernet cable to temporarily eliminate Homeplugs for testing purposes.

[Klaus57]

(20-12-2016 22:37)simoncn Wrote:  There wasn't any attachment to your post. However, I don't think the MinimWatch log is likely to show the reason for the problem as MinimWatch is able to see MinimServer.

Homeplugs are notorious for causing problems like this. The best way to debug this kind of problem is to strip down your network to an absolute minimum to establish a configuration that works reliably, then add back your other network components one by one until you find the component that is causing the issue. For example, you could use a long ethernet cable to temporarily eliminate Homeplugs for testing purposes.

Sorry to say, but I have the same situation; I use Lightning DS as Control Point and the Auralic streaming bridge. NAS: QNAP HS210 and HS 251 - both running the newest Firmware.
Since the latest minimserver update I have the situation, that my Control Point sometimes sees the Minimserver and sometimes not. Today I connected all devices directly - using a long ethernet-cable - with my router but could not see any difference.
For nearly 2 years I use minimserver and homeplugs -without any problems.

In my perception the trouble began with the latest updates. Maybe this is not causal, but it is really frustrating.
So for the moment I change to asset (which is not my favorite) and lightning server, which is not ideal with classical music.
Best reguards, Klaus L.

[DavidHB]

(27-12-2016 12:02)Klaus57 Wrote:  I have the same situation; I use Lightning DS as Control Point and the Auralic streaming bridge. NAS: QNAP HS210 and HS 251 - both running the newest Firmware.

This sounds like a network discovery issue. The update may indeed have triggered some sort of change or the issue may have been coincidental, but the problem is unlikely to lie with MinimServer as such (if it did, there'd be a lot more people complaining!)

In the circumstances you describe, my immediate suspicion would be directed at the one system component you don't mention - your router, and specifically its multicast settings. These are differently arranged and accessed on each router model, so it is very difficult to give specific advice. You might try powering down the whole system, and them powering it back up progressively, starting with the router. Let each component boot fully before starting the next one. This approach can sometimes clear network glitches.

David

[Klaus57]

(27-12-2016 16:23)DavidHB Wrote:  

(27-12-2016 12:02)Klaus57 Wrote:  I have the same situation; I use Lightning DS as Control Point and the Auralic streaming bridge. NAS: QNAP HS210 and HS 251 - both running the newest Firmware.

This sounds like a network discovery issue. The update may indeed have triggered some sort of change or the issue may have been coincidental, but the problem is unlikely to lie with MinimServer as such (if it did, there'd be a lot more people complaining!)

In the circumstances you describe, my immediate suspicion would be directed at the one system component you don't mention - your router, and specifically its multicast settings. These are differently arranged and accessed on each router model, so it is very difficult to give specific advice. You might try powering down the whole system, and them powering it back up progressively, starting with the router. Let each component boot fully before starting the next one. This approach can sometimes clear network glitches.

David

Thanks for your advice. I will follow your Recommendations.

Klaus

[Klaus57]

(27-12-2016 16:31)Klaus57 Wrote:  

(27-12-2016 16:23)DavidHB Wrote:  

(27-12-2016 12:02)Klaus57 Wrote:  I have the same situation; I use Lightning DS as Control Point and the Auralic streaming bridge. NAS: QNAP HS210 and HS 251 - both running the newest Firmware.

This sounds like a network discovery issue. The update may indeed have triggered some sort of change or the issue may have been coincidental, but the problem is unlikely to lie with MinimServer as such (if it did, there'd be a lot more people complaining!)

In the circumstances you describe, my immediate suspicion would be directed at the one system component you don't mention - your router, and specifically its multicast settings. These are differently arranged and accessed on each router model, so it is very difficult to give specific advice. You might try powering down the whole system, and them powering it back up progressively, starting with the router. Let each component boot fully before starting the next one. This approach can sometimes clear network glitches.

David

Thanks for your advice. I will follow your Recommendations.

Klaus

For several days everything seems to be ok. There were some router default settings in combination with running two minimserver which probably caused the troubles. Minimserver was not the reason.
Klaus