Roon Remote looking "infinitely" for roon remote libraries

Hi,

occasionally, I have a strange behaviour with my roon setup.

RoonServer is installed on a NUC5i3 (Win10 Home Edition, 128GB SSD, 16GB DDR3 RAM). I also have Roon Remote installed on the NUC, and run it whenever I want to visualize “Now Playing” on the big screen in parallel to running RoonServer in the background.

Before I plunge into trial and error I wanted your opinion regarding my issue:
Occasionally, my Roon Remote Devices (Pixel XL and Kindle Fire HD10) just won’t connect with my roon core/ roon server although it is running the whole time. The Pixel XL does not connect at all when trying but might connect 1 hour later and the Fire HD10 might show me “looking for roon remote libraries” for a couple of minutes before connecting to the roon core. In order to resolve that issue, I just restart the NUC (haven’t tried restarting roonserver yet, as I am controlling my NUC with a logitech remote and not with a mouse and keyboard)

I attached an extract of my log file which captures what happened at approximately the time when that happened (sorry, I didn’t check the exact time when it happened):

03/03 10:35:12 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:43037] lost client connection. Retrying
03/03 10:35:12 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:43037] connecting (attempt 1)
03/03 10:35:13 Warn: [rnet/RnetJsonClient] failed to connect No connection could be made because the target machine actively refused it 192.168.1.9:43037
03/03 10:35:13 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:43037] client connection failed. Retrying in 500ms
03/03 10:35:14 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:43037] connecting (attempt 2)
03/03 10:35:15 Warn: [rnet/RnetJsonClient] failed to connect No connection could be made because the target machine actively refused it 192.168.1.9:43037
03/03 10:35:15 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:43037] client connection failed. Retrying in 750ms
03/03 10:35:15 Trace: [raatserver] [RaatServer Kian s Pixel XL @ 192.168.1.9:39418] connecting (attempt 3)
03/03 10:35:15 Trace: [raatserver] [RaatServer Kians Pixel XL @ 192.168.1.9:39418] connected
03/03 10:35:15 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
03/03 10:35:15 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"device_id": "default", "type": "android", "config": {"external_config": {"max_sample_rate_multiplier": 1, "is_private": true, "max_bits_per_sample": 16}, "output": {"max_bits_per_sample": 16, "type": "android", "device": "default", "name": "Default Output"}, "volume": {"type": "android", "device": "default", "exclusive_mode": null}, "unique_id": "5472c5ad-03d6-308d-d391-f779b3fa82bc"}, "auto_enable": true, "name": "Default Output", "auto_name": "Kians Pixel XL", "is_system_output": true}]}
03/03 10:35:15 Info: [raatserver] GOT DEVICE 97566a5cc058162ec88c36ac8654a11c::default Type=android Name=Default Output 
03/03 10:35:15 Trace: [push] restarting connection (Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall.)
03/03 10:35:15 Trace: [push] retrying connection in 20115ms
03/03 10:35:21 Info: [stats] 1368mb Virtual, 417mb Physical, 191mb Managed, 1886 Handles, 63 Threads
03/03 10:35:26 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
03/03 10:35:26 Trace: [push] connecting to 159.203.179.219:9200
03/03 10:35:26 Trace: [push] connected
03/03 10:35:36 Info: [stats] 1364mb Virtual, 417mb Physical, 191mb Managed, 1865 Handles, 62 Threads
03/03 10:35:51 Info: [stats] 1360mb Virtual, 417mb Physical, 183mb Managed, 1697 Handles, 61 Threads
03/03 10:36:06 Info: [stats] 1364mb Virtual, 417mb Physical, 183mb Managed, 1698 Handles, 62 Threads

Any idea, what might cause this issue?

Problem seems to have vanished after reclassifying the network settings within Win10 as “private” instead of public…

thanks for all the “views” of the topic anyways…

A post was split to a new topic: Remote connections have improved but still having some issues