MinimServer Forum

Full Version: Naim App loses Minimserver
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
While playing music the Naim App will just lose my Minimserver connection. I am using a Naim NDX2 system version 3.8.0.5335 and the Naim app version 5.23. To get it back I have to re scan or restart Minimserver through the MinimWatch program on my Windows 10 computer. I have copied over the info from the Log and a debug. I am new to using the log, so I may have done it wrong. My log shows Minimserver running and then I re scanned to get it to appear again in the Naim app. To force the app to lose the connection, I switched from one wifi connection to another and back. When I came back the Naim app did not see the Minimserver so I re-scanned. I know this has to have something to do with a refresh going on between the Naim Ipad app and Minimserver on my Synology DS 218+. My Synology is running DSM 7.0. I do not know the correct setting to possibly make in Minimwatch to correct this behavior.

Any help would be greatly appreciated.

Thanks,
Mark

MinimServer 2.1, Copyright © 2012-2021 Simon Nash. All rights reserved.
MinimStreamer 2.0.9, Copyright © 2012-2021 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode)
Platform default charset is UTF-8
System platform is linux-x64
Setting language to English (en)
Current time is Sun Dec 19 14:34:10 EST 2021 in time zone US/Eastern
starting MinimServer[F-117]
Library contains 29900 audio files in 3225 folders
MinimServer[F-117] is running

14:48:34.203 Thread-26: Log action: SetLogStart
14:48:34.203 Thread-26: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:58401
14:48:34.203 Thread-26: StartPosition=615
14:48:34.204 Thread-26: Log action complete: SetLogStart
14:48:34.233 Thread-24: Log action: GetLogStart
14:48:34.233 Thread-24: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:58403
14:48:34.234 Thread-24: Log response: GetLogStart
14:48:34.234 Thread-24: StartPosition=615
14:48:51.889 Thread-22: Log action: GetLogDataLength
14:48:51.889 Thread-22: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56947
14:48:51.889 Thread-22: Log response: GetLogDataLength
14:48:51.889 Thread-22: DataLength=1509
14:48:51.905 Thread-24: Monitor action: GetProperty
14:48:51.905 Thread-24: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56948
14:48:51.905 Thread-24: ComponentName= PropertyName=logLevel
14:48:51.905 Thread-24: Monitor response: GetProperty
14:48:51.905 Thread-24: PropertyValue=debug
14:48:51.930 Thread-25: Log action: GetLogStart
14:48:51.930 Thread-25: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56949
14:48:51.930 Thread-25: Log response: GetLogStart
14:48:51.930 Thread-25: StartPosition=615
14:48:51.966 Thread-22: Monitor action: GetAllPackageStatus
14:48:51.966 Thread-22: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56951
14:48:51.967 Thread-22: Monitor response: GetAllPackageStatus
14:48:51.967 Thread-22: PackageStatusList=minimjre-14.0.1,MinimJRE,Active+Original,minimserver-2.1,MinimServer,Active+Original,minimstreamer-2.0.9,MinimStreamer,Active
14:48:51.982 Thread-24: Log action: GetLogStart
14:48:51.982 Thread-24: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56955
14:48:51.982 Thread-24: Log response: GetLogStart
14:48:51.982 Thread-24: StartPosition=615
14:48:51.983 Thread-25: Monitor action: GetProperty
14:48:51.983 Thread-25: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56953
14:48:51.983 Thread-25: ComponentName=minimserver PropertyName=lastNewVersionCheck
14:48:51.983 Thread-25: Monitor response: GetProperty
14:48:51.983 Thread-25: PropertyValue=
14:48:51.996 Thread-26: Monitor action: GetProperty
14:48:51.996 Thread-26: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56957
14:48:51.996 Thread-26: ComponentName= PropertyName=programName
14:48:51.996 Thread-22: Log action: GetLogStart
14:48:51.996 Thread-22: version=1, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56956
14:48:51.997 Thread-26: Monitor response: GetProperty
14:48:51.997 Thread-26: PropertyValue=MinimServer
14:48:51.997 Thread-22: Log response: GetLogStart
14:48:51.997 Thread-22: StartPosition=615
14:48:52.012 Thread-24: Monitor action: GetAllPackageProperties
14:48:52.012 Thread-24: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56958
14:48:52.012 Thread-24: PropertyNames=.name,.updatePackage,.newVersion,.newVersionURL,.versionUpdate,.ve​rsionUpdateURL,.update,.version
14:48:52.012 Thread-24: Monitor response: GetAllPackageProperties
14:48:52.012 Thread-24: PackagePropertyList=minimjre-14.0.1,Active+Original,MinimJRE,,,,,,minimjre-14.jmupd,14.0.1,minimserver-2.1,Active+Original,MinimServer,,,,,,minimserver-2.jmupd,2.1,minimstreamer-2.0.9,Active,MinimStreamer,,,,,,minimstreamer-2.jmupd,2.0.9
14:48:52.026 Thread-26: Monitor action: GetProperty
14:48:52.026 Thread-26: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56960
14:48:52.026 Thread-26: ComponentName= PropertyName=#ltc
14:48:52.027 Thread-26: Monitor response: GetProperty
14:48:52.027 Thread-26: PropertyValue=3
14:48:52.244 Thread-25: Monitor action: GetProperty
14:48:52.244 Thread-25: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56963
14:48:52.244 Thread-25: ComponentName= PropertyName=#ltc
14:48:52.245 Thread-25: Monitor response: GetProperty
14:48:52.245 Thread-25: PropertyValue=3
14:48:52.367 Thread-22: Monitor action: GetProperty
14:48:52.367 Thread-22: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:56966
14:48:52.367 Thread-22: ComponentName= PropertyName=#ltc
14:48:52.367 Thread-22: Monitor response: GetProperty
14:48:52.367 Thread-22: PropertyValue=3
14:50:25.156 Thread-25: Monitor action: SaveProperty
14:50:25.156 Thread-25: version=2, adapter=172.20.180.13, uriPrefix=http://172.20.180.13:9791/17d11015-6ad6-477c-b40f-5cdce9356ce4/Upnp/resource/, clientEndpoint=172.20.180.239:49538
14:50:25.156 Thread-25: ComponentName= PropertyName=logLevel PropertyValue=info
14:50:25.157 Thread-25: saveProperty: compName=null propName=logLevel propValue=info
14:50:25.157 Thread-25: getSaveValue: compName= propName=logLevel propValue=info saveValue=
14:50:25.157 Thread-25: writeConfigProperty: propFullName=.logLevel propValue=
14:50:25.169 Thread-25: updateActiveProfile: propFullName=.logLevel
14:50:25.169 Thread-25: RootContextImpl: called writeActiveProfile
14:50:25.170 Thread-25: writeActiveProfile: activeProfile=default
14:50:25.170 Thread-25: writeProfile: default
14:50:25.175 Thread-25: creating backup for default.profile
14:50:25.177 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.177 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.177 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.178 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.178 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.178 Thread-25: writeActiveProfile: activeProfile=null
14:50:25.178 Thread-25: writeActiveProfile: activeProfile=null
restarting MinimServer[F-117]
Current time is Sun Dec 19 14:52:21 EST 2021 in time zone US/Eastern
starting MinimServer[F-117]
Library contains 29900 audio files in 3225 folders
MinimServer[F-117] is running
This is a multicast discovery problem with your network, not a problem with MinimServer or the Naim app. For more information and some suggestions on how to solve this problem, see the Troubleshooting page.

If the suggestions on this page don't help, please post a detailed description of your network configuration incluing the make and model of your router. Has this problem started recently or has it always been this way?
Simon,

Thanks for the reply. I have used Minimserver since 2014 without any issues. Yesterday I upgraded my Synology DS 218+ to DSM 7.0. I then updated Minimserver to 2.1 and Minimwatch as well. Once I had everything updated, the problem started. It happens if you use the button on the top of the ipad to turn the screen off. When you push the button to turn the screen on again, you have to go back into the Naim app and the connection to Minimserver is lost. This never happened before yesterday. My network has not changed. The firewall in the Synology blocked the TCP ports 9790,9791 and UDP port 1900. I edited the firewall settings to allow these ports. Not sure if this is a culprit or not.

Mark
Simon,

My router is an Asus AX11000
I use a Netgear EAX80 as a wireless access point in the room with the Naim NDX2. The NDX2 is hard wired to the Netgear EAX80 access point
The Netgear tunnels the connection from the AX11000 on a 5G connection. In the room with the NDX2 the Netgear broadcasts a wireless channel in 2.4G.
The Ipad connects to the 2.4G connection on the Netgear EAX80.
The IGMP Snooping feature has been disabled the whole time I have had the router, so this is not a fix.

Mark
An incorrect setting in the Synology firewall could cause this issue. Please try completely disabling the Synology firewall for a short period as a test to see whether this solves the problem.

If this doesn't fix it, try powering all your network equipment off and on. When there is no other obvious cause, this is often the solution.
Simon
I completely disabled the firewall and that did not fix the issue. I shut the cable modem router, wireless access point, small non managed switch, ipad, and NDX2 for over 5 minutes. This did not fix anything either. The ipad keeps the lock on Minimserver as long as the app is not closed - I have to keep the screen on at all times, which is a real waste of power. Before the upgrade to the following yesterday:
DSM 7.0
Minimserver 2.1
Minimwatch 2.0.9
NDX2 firmware 3.8.0.5355
Naim app 5.23

I could play as song and turn the screen off. When I turned the screen Minimserver would be there ready to go.

Do you have any other ideas?

Mark
Simon,

I went as far as to reload Minimserver. I used the X64 file for my DS 218+. When I reloaded the firewall warning did not come up, as I had left my settings alone. I must have it right.

Mark
Simon and all who are reading this post,

If you are using Minimserver, a Synology, a Naim NDX2, and an Ipad, please be aware of the following things I learned the hard way. When upgrading to DSM 7.0 and Minimserver 2.1 follow the excellent directions Simon and Synology give. I did and it helped tremendously. My issue was spread across two items. The Synology firewall needs updated to specifically allow TCP ports 9790,9791 and UDP port 1900. The way my firewall was set up prior to the update to 7.0 had a blanket name for the ports (MinimServer UPnP media). Be sure to get rid of this old rule and create two new ones for these specific ports. The second and biggest issue is to have your Ipad on the latest software (in this case VS 15.2). When I updated the NDX2 and Ipad Naim app on the Last version of apple software I had intermitent connectivity to Minimserver. I fixed the problem of connectivity by doing the following two things:

1) Editing the Synology Firewall settings to the specific ports
2) Updating the Ipad to the VS 15.2 software.

I spent hours trouble shooting this mess. I hope this helps anyone with these components.
Thanks for posting this very helpful information.

MinimServer provides suitable preconfigured Synology firewall rules. To enable these rules, do the following:

1) From Control Panel, select Security
2) Select the Firewall tab
3) Check "Enable firewall" (if not already checked)
4) Under Firewall Profile, click the Edit Rules button
5) Click the Create button
6) Under Ports, select "Select from a list of built-in applications"
7) Click the Select button
8) Scroll down until you see MinimServer UPnP media server
9) Select the two rules with this name (TCP 9790, 9791 and UDP 1900)
10) Click OK 3 times
11) You should see a message "Firewall settings have been saved successfully." Click OK to dismiss this message.

The pointer to updating the iPad software will be helpful for other users. I haven't experienced intermittent connectivity from my iPad but I am updating to 15.2 now to make sure all is well.
Simon,

Without your help I could not have solved the problem. Minimserver is the gold standard for music libraries. Love the work you do!

Mark
Reference URL's