since you helped with connecting my PC DAC to Roon everything worked like a charm and brought me many joyful hours. Until this evening: When I came home, none of my remotes (PC via cable, iPhone/Android Blackberry via Wifi) would be able to connect to the core. They do see the core , but they are unable to connect.
There were no changes between this morning - when Roon played internet radio on a squeezebox - and tonight. To my knowledge no firewall, firmware or whatsoever was touched.
The core is running on a QNAP TS-251+ (8GB). The PC and the core are connect through a switch (trendnet TEG 582g). The switch is connected the router (Fritz!Box 7360) via a Fritz!Powerline 1000E. All other systems are just fine.
I already cleared the cache (deleted cache folder on QNAP), restarted every device a couple of times, even updated the QNAP firmware. The Roon-core itself does not complain
I’m wondering if your firewall could still be the reason why you are not able to connect. Can you check to make sure that both Roon and RAATServer are listed as exceptions? We have previously seen issues with Powerline adapters so it would be a good test if you could temporarily connect your QNAP to the router instead of the powerline adapter.
We have also seen FritzOS cause some communications issues with router firmware updates that happen behind the scenes, do you by any chance have “Software Packet Acceleration” as an option on that box? I would recommend disabling it as per our Networking Best Practices. Please let me know if that helps!
I have gone ahead and enabled diagnostics mode for your account and what this action does is automatically upload a set of logs to our diagnostic server. I’m reviewing the diagnostics and noticed something here:
I am seeing a file on your HH-Q1 potentially causing some issues and causing your QNAP to be stuck: 01/09 01:13:46 Trace: [analysis] analyzing trackid=2571314 url=/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/Musik/Lossless/000 - Backup/Lyambiko/Muse/02 - I Went To Heaven_ADMIN_Jan-27-113424-2016_Conflict.aiff
Can I please ask you to move this file out of that folder and then reboot the server? Please do not delete the file just yet because if we narrow it down to the cause for this issue I’d like to get it over to QA to take a look.