Good morning, with the latest Windows update the devices Networks using SMB1 are no longer supported. Security is fine, but I have several devices around the house that I still use this protocol on which I upload the files. I managed to reload SMB1 on the PC but I still have problems because both with Explorer and with Directory Opus I can't directly view the devices on the network, but I can only see them by entering the IP address. Is there any way to correct this? Thank you
I’ve moved your post from the Support category to Networking, since it is a general question about Windows networking, and not a Roon issue relevant for the support team to answer.
As you can see from the first screenshot the Nucleus+ icon does not appear since
according to screenshot you can see what I have to insert to see the disks on the network.
In the third screenshot you can finally see the connected hard drives. The problem is that having many devices connected to the network, the IP address is almost always different
I am forced every time to first search for the address with an IP scanner and then
insert it as described. Is it possible to make some changes to the registry or Windows services to make the icon reappear on the network?
Thank you
In addition to what @bearFNF suggested, all decent routers provide a name resolution server on the local network, so using „nucleusplus“ instead of the IP address usually works.
I don’t know about the Directory Opus (which seems to be a file manager), but using network device names is such basic functionality that I can’t imagine that it can’t do it. (Plus I find screenshots online that show network device names).
If names don’t work in File Explorer nor Directory Opus, then your router might not provide them. It’s rare but possible. What’s your router model?
In this case, IP reservation on the router as suggested by @bearFNF is the way to go - if the router supports at least this.
I had to apply this fix to be able to access my streamer/core
Even after applying the fix, File Explorer still did not show the streamer without typing in the name or IP address every time. Pinning a link to Quick Access fixes this.
I had the same problem with the latest version of Win11. I had to apply the fix and force connection. It seems Rock or Roon OS is not fully compliant with SMB v2 or v3 as implemented in windows.
Which fix? The one in the post above, „Accessing a third-party NAS with SMB in Windows 11 24H2 may fail“?
If so, the problem is due to Microsoft’s SMB access changes in the recent Windows 11 update, 24H2. The change is that Microsoft does not allow a Windows client anymore to connect to SMB shares with unauthenticated guest access.
However, Roon OS only has unauthenticated guest access at this time (Roon Labs is apparently working on this). Therefore, the fix is to change Windows settings to re-enable it.
This has noting to do with SMB versions. Roon OS supports SMB 2 and 3 as well as it is possible for anyone who isn’t Microsoft (by using Samba, a free and open source enterprise-grade SMB replacement for non-Windows machines)
Thanks for the advice, but unfortunately it won’t let me put it in quick access.
What I can’t understand is that I have a mini-pc with the same OS. Windows 11 pro with
the same updates and changes made to Sercices.msc: in this I can see networked devices such as the Nucleus+ and others with SMB1. I have to try to understand the differences between the two PCs but it’s not easy. One thing I noticed: opening the Windows services on the two PCs I saw that they differ in some items that are in the
old while they do not appear in the mini-pc.
I really don’t know what to think…
thank you and have a good day
Yes, the fix described in the Windows Home Edition section.
Please, note that I mentionned « as implemented in Windows », not saying it is THE correct way. But many Roon users will face this issue in coming weeks and not all of them may be able to apply the fix. It is a good thing that Roon work on an evolution of Roon OS or a workaround.
Authentified connection is a good security point anyway.
