Problem with AlbumArt (Naim)

[vithomme]

(29-05-2013 16:10)vithomme Wrote:  

(26-03-2013 08:02)simoncn Wrote:  

(08-03-2013 09:29)tbe2013 Wrote:  only to keep the community informed:
We are working on these issue (analyzing trace logs) and keep the thread updated if there are some new informations.

After further testing, this problem seems to be caused by having multiple active subnets in some Synology models with dual Ethernet ports.

If one port is left disconnected, the APIPA subnet for that port (169.254.x.x) is still active and accessible via the other port. This causes MinimServer to make itself available on two different IP addresses on different subnets via the connected port. Depending on how the network routing is set up, the control point and renderer might be accessing MinimServer using both IP addresses at the same time. This is causing the problem with tracks randomly failing to play.

The solution is to use the ohnet.subnet property to bind MinimServer to a single subnet IP address. For example, if the correct subnet is 192.168.0.x, the ohnet.subnet property should be set to 192.168.0.0.

Yes, I have a spare ethernet port and I'll try what you suggest. Thanks!

Dear Simon, I'm not clever enough to do as suggested right away. How and where do I bind MS to an IP address? Do I have to dig into the Synology (1512+) menus or do I have to change things in MinimServer through MinimWatch?

By the way, I use MinimWatch on my macbook and I can't see the properties, log file, or about. I've got MS .74 on the NAS... Restarting through MinimWatch does work though.

Your help is very much appreciated

[vithomme]

(31-05-2013 15:48)vithomme Wrote:  

(29-05-2013 16:10)vithomme Wrote:  

(26-03-2013 08:02)simoncn Wrote:  

(08-03-2013 09:29)tbe2013 Wrote:  only to keep the community informed:
We are working on these issue (analyzing trace logs) and keep the thread updated if there are some new informations.

After further testing, this problem seems to be caused by having multiple active subnets in some Synology models with dual Ethernet ports.

If one port is left disconnected, the APIPA subnet for that port (169.254.x.x) is still active and accessible via the other port. This causes MinimServer to make itself available on two different IP addresses on different subnets via the connected port. Depending on how the network routing is set up, the control point and renderer might be accessing MinimServer using both IP addresses at the same time. This is causing the problem with tracks randomly failing to play.

The solution is to use the ohnet.subnet property to bind MinimServer to a single subnet IP address. For example, if the correct subnet is 192.168.0.x, the ohnet.subnet property should be set to 192.168.0.0.

Yes, I have a spare ethernet port and I'll try what you suggest. Thanks!

Dear Simon, I'm not clever enough to do as suggested right away. How and where do I bind MS to an IP address? Do I have to dig into the Synology (1512+) menus or do I have to change things in MinimServer through MinimWatch?

By the way, I use MinimWatch on my macbook and I can't see the properties, log file, or about. I've got MS .74 on the NAS... Restarting through MinimWatch does work though.

Your help is very much appreciated

Terribly sorry: I CAN see the log and properties. They where hidden behind the browserscreen...

[simoncn]

(31-05-2013 15:48)vithomme Wrote:  Dear Simon, I'm not clever enough to do as suggested right away. How and where do I bind MS to an IP address? Do I have to dig into the Synology (1512+) menus or do I have to change things in MinimServer through MinimWatch?

You need to set the ohnet.subnet property from MinimWatch. No change to the Synology configuration is needed.

Quote:By the way, I use MinimWatch on my macbook and I can't see the properties, log file, or about. I've got MS .74 on the NAS... Restarting through MinimWatch does work though.

Your help is very much appreciated

There is no MinimServer 0.74 version. The latest MinimServer version is 0.72. You should update both MinimServer and MinimWatch to the 0.72 versions, if they are not at this level already.

[vithomme]

(31-05-2013 16:08)simoncn Wrote:  

(31-05-2013 15:48)vithomme Wrote:  Dear Simon, I'm not clever enough to do as suggested right away. How and where do I bind MS to an IP address? Do I have to dig into the Synology (1512+) menus or do I have to change things in MinimServer through MinimWatch?

You need to set the ohnet.subnet property from MinimWatch. No change to the Synology configuration is needed.

Quote:By the way, I use MinimWatch on my macbook and I can't see the properties, log file, or about. I've got MS .74 on the NAS... Restarting through MinimWatch does work though.

Your help is very much appreciated

There is no MinimServer 0.74 version. The latest MinimServer version is 0.72. You should update both MinimServer and MinimWatch to the 0.72 versions, if they are not at this level already.

Please forgive my stupidity, of course it is 0.72 MS. Updated MW as well to 0.72 (was still using 0.63)

Where do I go to change the ohne.subnet?

[vithomme]

about: running on host and port 10.0.1.3:40689

now go to properties, advanced, and fill out 10.0.1.3 ... for ohnet.subnet??

[simoncn]

(31-05-2013 19:09)vithomme Wrote:  about: running on host and port 10.0.1.3:40689

now go to properties, advanced, and fill out 10.0.1.3 ... for ohnet.subnet??

You need to combine the IP address with your netmask to get the correct value for ohnet.subnet. If you don't know what your netmask is, it's probably 255.255.255.0, which would give an ohnet.subnet value of 10.0.1.0.

[vithomme]

(31-05-2013 19:41)simoncn Wrote:  

(31-05-2013 19:09)vithomme Wrote:  about: running on host and port 10.0.1.3:40689

now go to properties, advanced, and fill out 10.0.1.3 ... for ohnet.subnet??

You need to combine the IP address with your netmask to get the correct value for ohnet.subnet. If you don't know what your netmask is, it's probably 255.255.255.0, which would give an ohnet.subnet value of 10.0.1.0.

Thanks Simon! 10.0.1.0 works. Since non-responding was a kind of random thing I'll be sure only after a few days, but this probably fixed the problem. Thanks again for your support.

[Clarandam]

Hi Simoncn, vithomme,

i'v got the same problem (port 9790) while re-installing minimserver on my Synology 214+ after a big update. So far i tried to wait, to reboot, to update minim watch but nothing worked, so i understood that i have to modify this ohnet.subnet. in minim server while using minimwatch, the fact is as minim server is not installed on my sinology i cannot access to any properties of it. In the minim watch menu they appears all "grey" only the one with (watch) are "open". As my english is far away from perfect did i miss understood something and what is the process to fix that in my situation? Thank very much for your help.

Regards

[simoncn]

(20-04-2014 20:20)Clarandam Wrote:  Hi Simoncn, vithomme,

i'v got the same problem (port 9790) while re-installing minimserver on my Synology 214+ after a big update. So far i tried to wait, to reboot, to update minim watch but nothing worked, so i understood that i have to modify this ohnet.subnet. in minim server while using minimwatch, the fact is as minim server is not installed on my sinology i cannot access to any properties of it. In the minim watch menu they appears all "grey" only the one with (watch) are "open". As my english is far away from perfect did i miss understood something and what is the process to fix that in my situation? Thank very much for your help.

Regards

It sounds like you may have the problem described in this thread. If you are seeing the same error, please try the solution suggested there.

[Clarandam]

Hi simoncn, many thanks it's the same problem and i'm happy to see that there's a solution :-) but I need a few more details as i'm not a specialist in all that. how can i login using SSH, where do i have to past this command?
Thanks