· None of the above quite fits
· None of these quite match
· Random port in ARC and request to login upon almost every reboot
· Wired, but not relevant
Please note that i reset the ARC port to it’s correct value a few days back, after i had used a different server. Now this time this port is completely random and has no connection to my chosen port, and i have not authorized another server.
The second issue which has arisen within the two last releases of Roon is the fact that most often i need to login to authorize the server after reboots! I have had some issues with the hardware, but even so if i make changes to other config (not Roon related) after the reboot (which of course closes Roon Server on this headless/fanless machine) Roon won’t autostart, as i requests a re-authorization. I have never seen this before build 2.65/2.66…
Hi @Mikael_Ollars,
Thank you for the report. Just to clarify, the port number regenerates on each restart, even if you don’t switch servers or change network interfaces on this server machine?
And any time you do make a change to the network interface on the machine, auto-launch fails and you need to login again?
We might have something interesting in logs. It looks like the Npcap driver installed by your SOtM device is registering virtual network adapters without an IPv4 stack, which is causing Roon’s port negotiation to fail and fall back to a random port. Try disabling the SOtMLink virtual adapters in Device Manager and see if that gets your assigned port sticking. We’ll escalate this in the meantime to see what we can do.
Thanks!
No, it doesn’t happen on every restart, but seems to have been initiated by the reauth requests.
If i pull power to the machine, it happens! (I am well aware this isn’t the proper way! 
)
This seems to happen whenever the reboot isn’t “clean”, but it’s difficult to say..
Last time it happened, i was trying to connect to a share on the same machine which failed, and trouble shooting disclosed that the interface which is “connected” had been typed as Public (hence-access difficulties) I changed the type to private which allowed Share access, but discovered that Roon-services were not allowed through the firewall on Private networks… I don’t have a clue as to why these Win-settings were changed/set, the machine has been running just fine since around christmas time (when it was reinstalled)
Great information! Thank you! If thats the reason i’ll live with it, as the Diretta Link makes so much sense in the sound fidelity department! I just have to make sure the reboots are clean, as the setting seem to stick that way.
As a side note, i have just changed the power supply on this machine which i am convinced will alleviate the unexpected reboots. The old power supply didn’t really cut it when Roon (or other services) let the CPU cores run free…
Hey @Mikael_Ollars,
Thanks for the heads up! Certainly, let us know how things go. We still have a ticket in and should get some feedback, no matter - we’ll keep you in the loop once that happens. 