Roon Core on streamer not found anymore, although the streamer is accessible

Problem description (started aug 4, 2018):

  • Roon Remote on both smartphone and PC won’t connect to the Roon Core on my streamer anymore; the day before there was no problem
  • The strange thing is that the PC can open, copy, delete, etc. all the files on the streamer’s hard drive using \VORTEXMOD, and that the Vortexbox interface can reached at http://vortexmod/.
  • When I start Roon om my PC, choose the PC to function as Core, select the music directory on the streamer, all the files are there; I can play the music using both Android phone and PC as the Remote

Hardware, network and software:

  • Roon version 1.5 (build 334) on PC and Android phone; the Core on the streamer was updated through the PC somewhere in July to the same version
  • Remotes:
    PC: AMD FX-8370, 16GB RAM; Windows 7 Pro 64 bit PC SP1, with the last updates done July 24th; Norton Security (automatic daily updates)
    PC settings: enabled are network detection, file- and printer sharing, sharing of public maps, media streaming, file sharing with 128-bit encryption, password protected sharing; connections to the home group are managed by Windows
    Phone: Sony Xperia ZX with Android 8.0; Norton Mobile (automatic daily updates)
  • Streamer: 432 Evo with Vortexmod 2.3 (Fedora 20 - Heisenbug) preinstalled; 2TB internal HDD; connected to DAC by USB
  • Network description (starting upstream):
  1. DSL modem/router: Arkadyan Experia Box 8
    Wi-Fi always off; LAN only connected to Ubiquiti; voice options for telephony are off
  2. router: Ubiquiti ER-X-SFP; configured as single LAN; most recent firmware (v1.10.05, 2018-06-28)
    both WAN and LAN are configured as DHCP
    printer, scanner and PC are directly connected
  3. unmanaged switch: Cisco SG110D-08
    connected to router by a 10m long Cat 8 cable
    connects to streamer, DAC, satellite decoder and access point
  4. access point: Asus RT-AC68U router in access point modus (so the firewall is disabled); most recent firmware (3.0.0.4.384.21140, 2018-07-10); connected to switch

Actions taken without success:

  • De- and reinstalled Roon Remote on both PC and phone
  • Switched off everything (complete network and everything connected wired and wireless); switched on the network going from upstream to downstream; then switching on everything attached to the network; I waited for each component to fully boot, until going further downstream
  • Asus access point: switched the Ethernet cable from WAN to LAN1
  • Turned off 432 Evo streamer; closed Roon remote on PC; disconnected Ubiquiti router from modem; disabled firewall on PC and router; switched on streamer; started Roon on PC
  • same as above, but first took out the switch between the router and the streamer
  • Ubiquiti: did a factory reset (that is: with the hardware button)
  • swapped the Ubiquiti for a spare Cisco SG110D-08 unmanaged switch; rebooted the two other switches; disconnected the Experiabox from the Internet and turned off the Norton Security Firewall
  • Android phone: disabled Norton Mobile
  • Windows, Norton Security → Settings → Firewall → Trust device: added the Vortexbox
  • Did an upgrade using http://vortexmod/upgrade.php

Notes:

  • August 1st I swapped the Cisco switch connected to the Xperiabox modem/router for a Ubiquiti router; the Xperiabox remained; the three days after the swap PC and Android phone had been happily connecting to the Core on the streamer; the months before there were some occasional Core connection problems, but they were always resolved after power switching streamer, switches and modem/router
  • Connected streamer to TV: the boot menu chooses the first option (Fedora (3.19.8-100.fc20.x86_64) 20 (Heisenbug)); the boot process is too fast to read the messages; after the boot the Vortexmod shows a DOS like prompt; when I typed ls, it asks for a password that I don’t have; I didn’t try the other boot options, because I don’t know Linux and don’t want to mess-up the installation
  • http://vortexmod/upgrade.php: no option to update or remove Roon core; LMS, Bliss, etc. can be removed or updated
  • http://vortexmod/network.php: changing the SMB workgroup name from “workgroup” to “WORKGROUP” as reported in Windows results in the PC recognizing the streamer as “Logitech multimedia device” instead of as “VORTEXMOD”; also now there is a connection to the Logitech Media Server; after changing the SMB name back to “workgroup” the LMS is gone and “VORTEXMOD” is back; however still no connection to the Roon core; the strange thing is that the DAC now gets a fix at 192kHz soon after the server has booted, while before it would only get a fix at 44.1kHz and only if a track was streamed (I disabled the 432Hz plugin and oversampling a long time ago; for some reason it didn’t sound well on my system)
  • In a DOS box on the PC, when typing “arp -a > arpoutput.txt”, this is the output from the text file:
    Interface: 192.168.1.39 — 0xd
    Internetadres Fysiek adres Type
    192.168.1.1 78-8a-20-bc-82-66 dynamisch
    192.168.1.40 d0-50-99-ac-d9-a1 dynamisch
    192.168.1.42 38-d5-47-62-eb-d0 dynamisch
    192.168.1.44 00-1d-ec-0a-b7-e5 dynamisch
    192.168.1.51 00-11-f6-a8-58-90 dynamisch
    192.168.1.255 ff-ff-ff-ff-ff-ff statisch
    224.0.0.22 01-00-5e-00-00-16 statisch
    224.0.0.252 01-00-5e-00-00-fc statisch
    239.255.255.250 01-00-5e-7f-ff-fa statisch
    255.255.255.255 ff-ff-ff-ff-ff-ff statisch
  • When logging in to the Ubiquiti router it reports that:
  • 192.168.1.40 (d0:50:99:ac:d9:a1) is “vortexmod”
  • 192.168.1.39 (40:8d:5c:1f:76:27) is the Windows PC
  • No subnet masks are given
  • Windows: Configuration screen → Network centre → Network → Menu, View, Details:
    PC 127.0.0.1 no MAC address WSD
    VORTEXMOD no IP address no MAC address WSD
    VUDUO 192.168.1.44 00:1d:ec:0a:b7:e5 NetBIOS (satellite decoder)
    BRN_8EEB3C no IP address no MAC address NetBIOS (printer)
    This was done at the same time being logged in to the Ubiquiti router the step before

Thank you for the detailed report, @Peter_van_Schendel!

I’d like to propose a test — Are you able to connect to the Core machine if you use a fresh database? Please see the steps below:

  • Locate your Roon database according to these instructions
  • Rename the entire RoonServer folder to roon_old
  • Relaunch Roon, sign in, and configure a new install

Let me know if you’re able to connect after this.

-Dylan

Thanks for the swift response @dylan,

I think the instructions in https://kb.roonlabs.com/Database_Location may be for Windows 10 (mine is Windows 7).
I renamed the directory Database in C:\Users\:slight_smile::slight_smile::slight_smile::slight_smile:\AppData\Local\Roon to “Database (renamed)”.
Rebooted the Roon Core machine using the Vortexbox.
Then launched Roon on my PC and selected “Find my Roon Core”. The core isn’t found, but a new Database directory was made.
For the time I’ll leave it at this: the developer offered assistance. Let’s hope it will do.
If you or the community would like it, I can summarise in this what the solution is.
Kind regards,

Peter van Schendel

@dylan

The developer of the streamer managed to log in to it and resolve the problem.
He told me there was a small mixup in how the streamer took care of the Roon Core updates. There was a left-over from Roon 1.3 and the updates weren’t handled in the right way.
So apparently there was no fault in Roon itself.
Now the hdd’s platter in the streamer is spinning happily again and my set is making music :slight_smile:
Kind regards,

Peter van Schendel

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.