Cannot longer find my NUC/Rock PC on my network [Solved]

Today I should copy some music from my windows PC to my Rock NUC. Could not find my NUC on my network, it has always worked before, but not after the new Rock update.

I can ping my NUC from my windows PC.

What has happened here?
Regards Peter

Hello @Peter_Leinslie,

Have you tried reboot NUC and your windows machine ?

I have powered off both Pc’s, shut down my network but it doesent work. Have not tried just to reeboot the nuc.
It plays my music as it always have. Roon desktop from my windows pc works.
Strange.

Peter

You should try to reboot ROCK machine and see if it helps. Can you also launch any Roon Remote, in the app open the About page (in Settings) and tell us the build number of Roon OS you are using ( look for ‘Roon OS Version’ field) ?

Regards,
Vova

Roon OS Version1.0 (build 155) stable

Hi @Peter_Leinslie ----- Thank you for the follow up and providing the request information asked in @vova’s previous post. The insight is appreciated!

Moving forward, I wanted to touch base with you and see if rebooting the NUC yielded any changes in behavior here.

-Eric

No changes after reboot.
Peter

This happened to me yesterday. I put in an HDMI and found the machine was sitting at a bootloader menu. I attached a USB keyboard and hit ESC for normal boot. Nothing happened. I restarted it and it then booted normally.

Peter, are you by chance running the Fall Creators Update of Windows 10?

My windows version:
Windows 10 Enterprise
Version 1709
Build 16299.192

I seem to have normal boot. Tried with hdmi and usb keyboard. All looks normal.
peter

It’s possible that Windows 10 Enterprise is doing the same as the Fall Creators Update - disabling SMBv1. See:

i have tried to diable and enable SMBv1- same result.
Does this make any sense:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-P9URMA3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® Ethernet Connection (5) I219-V
Physical Address. . . . . . . . . : 2C-4D-54-F0-00-98
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a1e6:5196:7cea:d97f%5(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.17(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 28. januar 2018 11:10:27
Lease Expires . . . . . . . . . . : 29. januar 2018 11:10:28
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 36457812
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-EB-20-E7-2C-4D-54-F0-00-98
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:78cf:83b:3bab:a8ce:ba5(Preferred)
Link-local IPv6 Address . . . . . : fe80::83b:3bab:a8ce:ba5%2(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 117440512
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-EB-20-E7-2C-4D-54-F0-00-98
NetBIOS over Tcpip. . . . . . . . : Disabled

Peter

Have also noticed a decrease in the stability of ROCK since the 155 update.
There are many moments where ‘Lost Connection, Trying to Reconnect’ is seen on the Roon Remotes.
The ROCK is still present on the network, and the Core is running, but there are seems to be some networking presentation issues.
Can we go back to Build 150 please.

Also, what was covered in the 155 update, as there was no Release Notes with it.

Thanks,
Simon.

Hmm - not seeing that here. Everything’s Rock-solid… However, my Remotes are all Windows devices - no iOS, Android or OSX stuff allowed in my home, thank you…

Hi @Peter_Leinslie ----- Thank you for your continued feedback and more importantly, thank you for your patience here.

Before continuing forward, I want to make sure I have this behavior clear in my head. From my understanding of your report, and please due correct me if I am wrong, you are running ROCK on a NUC that can be pinged from your Windows PC computer (Roon remote) but you are not seeing ROCK listed as a network share on the same computer, yes? Furthermore, you have no issues controlling ROCK via the PC, its just that the ROCK can’t be accessed via the PC on the OS level, yes?

During your troubleshooting have you tried re-mounting ROCK via “Network and Sharing Center”?

-Eric

I can see rock listed as a network:

But i cannot access it:

I can control rock with this pc.
I cannot re-mount rock via “Network and Sharing Center”

Peter

I can switch to english language if you cannot understand the danish.

Er, Peter, you have the ROCK NUC mounted as a drive ( D: ). This may be the issue. I don’t do that, I just access ROCK over the network…
Roon 460

Nono. Thats just a bacup of music and restore of the roonserver. It’s just called d:/ roon

Peter

Here’s the english version.
This is my network:

This happends when i try to open ROCK:

Here is my Roon desktop:

Here is when i ping my Roon/NUC

image

Here is my Roonserver:

Hope this is clear enough
Peter