(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...
Search
Member List
Calendar
Help
