(18-09-2014 21:18)gnomus Wrote:  However, I have discovered that, as you suspected, Kinsky is losing the QNAP whilst it is still active.

(18-09-2014 22:00)simoncn Wrote:  

(18-09-2014 21:18)gnomus Wrote:  However, I have discovered that, as you suspected, Kinsky is losing the QNAP whilst it is still active.

How long does it take for this to happen? Does MinimServer[QNAP] suddenly disappear from the Kinsky screen? What exactly do you observe when this "losing the QNAP" happens?

Could you try running another server (such as Twonky) on the QNAP? It would be interesting to know whether Kinsky loses everything on the QNAP or just loses MinimServer.

(19-09-2014 09:45)gnomus Wrote:  OK. I've never seen it disappear before my eyes, so to speak. However, it seems that it can lose the server within only a few minutes of finding it. Incidentally, I get the same behaviour when using Kinsky on the PC. This morning it had found MinimServer[QNAP] and within 5 minutes had lost it again.

At your suggestion, I installed Twonky on the QNAP this morning and I have been able to get to a state whereby Kinsky can see Twonky on the QNAP, but not MinimServer on the QNAP. I attach a screenshot from Kinsky (Windows) showing this. MinimServer[DiskStation] is the server running on the Synology, of course.

(19-09-2014 10:30)simoncn Wrote:  If you do right-click > View > Rescan Network in Kinsky Windows when MinimServer[QNAP] isn't showing, does this find MinimServer[QNAP]?

(19-09-2014 10:30)simoncn Wrote:  If you do right-click > Tools > Debug Console in Kinsky Windows when MinimServer[QNAP] isn't showing, does the log contain any messages that look relevant?

(19-09-2014 10:30)simoncn Wrote:  Please produce an ohNet debug log for MinimServer[QNAP] by doing the following:

1) In the System tab of the Properties window for MinimServer[QNAP], set the ohnet.debug property to All-Timer
2) In the log window for MinimServer[QNAP], set the logging level to Debug
3) Stop and restart MinimServer from the QNAP App Center
4) Use Kinsky Windows to discover MinimServer[QNAP]
5) As soon as you notice that Kinsky Windows isn't seeing MinimServer[QNAP], copy the minimserver.log file from the Public share of MinimServer[QNAP] to your Windows PC
6) Reset the values that you changed in steps 1 and 2
7) Zip the minimserver.log file and post it here

Many thanks!

(19-09-2014 17:07)gnomus Wrote:  

(19-09-2014 10:30)simoncn Wrote:  If you do right-click > View > Rescan Network in Kinsky Windows when MinimServer[QNAP] isn't showing, does this find MinimServer[QNAP]?

No

(19-09-2014 17:25)simoncn Wrote:  

(19-09-2014 17:07)gnomus Wrote:  

(19-09-2014 10:30)simoncn Wrote:  If you do right-click > View > Rescan Network in Kinsky Windows when MinimServer[QNAP] isn't showing, does this find MinimServer[QNAP]?

No

This indicates that the QNAP is not receiving UPnP discovery messages sent by Kinsky. This is probably caused by a multicast issue with your network that is sometimes preventing UPnP discovery messages sent by Kinsky from being received by MinimServer[QNAP]. What exactly are the network components that a multicast message would need to traverse in its journey from Kinsky to MinimServer[QNAP]?

Note: This problem is not affecting Twonky[QNAP] because Twonky floods the network with very frequent "alive" messages that are being received by Kinsky. The ohNet UPnP stack used by MinimServer doesn't do this flooding because it shouldn't be needed if the network is working correctly.

(19-09-2014 17:41)gnomus Wrote:  1) My Internet connection comes into an upstairs room. That is where the router (and hence the source of the wireless) is sited.
2) My Listening Room is downstairs. That is where the Akurate DS, Kontrol and the QNAP is sited. These are connected together with a Network switch (recommended by yourself).
3) Getting the Control Point(s) to communicate reliably with the network has been a bit of a pain. I did have HomePlugs for a while. However, these proved to be worse than useless. Eventually (and on the advice of another forum member) I opted for the Apple Airport Extreme (which is connected to the Router upstairs and is now the Wireless source in the house). This communicates with an Apple Airport Express, which is connected to the Network Switch downstairs.

For the avoidance of doubt the switch to the Apple devices is relatively recent (ie the last week) - the current problems pre-date the Apple gear (which was bought partly in the hope that it would solve the lost QNAP issue). It was only when the Apple gear didn't solve the issue that I posted here.

(19-09-2014 18:04)simoncn Wrote:  

(19-09-2014 17:41)gnomus Wrote:  1) My Internet connection comes into an upstairs room. That is where the router (and hence the source of the wireless) is sited.
2) My Listening Room is downstairs. That is where the Akurate DS, Kontrol and the QNAP is sited. These are connected together with a Network switch (recommended by yourself).
3) Getting the Control Point(s) to communicate reliably with the network has been a bit of a pain. I did have HomePlugs for a while. However, these proved to be worse than useless. Eventually (and on the advice of another forum member) I opted for the Apple Airport Extreme (which is connected to the Router upstairs and is now the Wireless source in the house). This communicates with an Apple Airport Express, which is connected to the Network Switch downstairs.

For the avoidance of doubt the switch to the Apple devices is relatively recent (ie the last week) - the current problems pre-date the Apple gear (which was bought partly in the hope that it would solve the lost QNAP issue). It was only when the Apple gear didn't solve the issue that I posted here.

Thanks for this. To complete the picture, how is the PC running Kinsky connected to the network?

(19-09-2014 19:10)gnomus Wrote:  OK - Kinsky did eventually lose MinimServer[QNAP]. I got the log file. I zipped it. I cannot upload it, however, because it is bigger than 1024Kb. The file itself was nearly 24 meg which has zipped down to ~1.9MB.

Any suggestions?