Trouble logging on to ROCK from Windows 10

[Geoffrey_Binder]

Roon Core Machine

Lenovo ThinkCentre 720s i5 8GB RAM

Networking Gear & Setup Details

Netgear Prosafe MS510TXPP switch and ASUS TM1900 router

Connected Audio Devices

Ethernet

Number of Tracks in Library

60,000

Description of Issue

This is a fresh install of ROCK on this machine.
The installation went smoothly. Roon remote has connected and I have pointed it at my NAS with my music files. They have uploaded no problem.

Because I cannot connect to ROCK I cannot install the codecs.

I cannot connect to ROCK via Windows. I type in \ROCK\data and then get prompted with a login. I have tried guest and guest/guest but cannot connect.
I can see ROCK as a computer on my network but get the error message, attached.

I have enabled SMBv1 and enabled Insecure Guest Logons in Lanman Workstation.

Any help would be much appreciated!

Cheers, Geoff

[BlackJack]

@Geoffrey_Binder

I have enabled SMBv1 and enabled Insecure Guest Logons in Lanman Workstation.

Have you rebooted the Windows PC after those changes?

[Geoffrey_Binder]

Hi BlackJack, Yes.

[BlackJack]

You can also see if the solutions other users found might help you too:

Unable to access the ROCK/Data/Codecs folder to install the ffmpeg Codecs file

Hi Greg & BlackJack, I eventually figured out what the issue was. Yes, I’m using File Explorer to find the share. However, you also need to turn ON the SMB file sharing feature in Windows under Control Panel, Programs. After I did that and rebooted the various Rock folders were visible and accessible via File Explorer. I’ve copied the ffmpeg codecs file to /Data/Codecs folder and everything looks good in the Rock web UI now. Internet Explorer no longer renders the Rock Web UI properly. Usi…

Going insane trying to install ROCK codec

@Rugby Yes, SMB 1.0 is enabled on the Windows machine. But I had to go into Control Panel/Programs/Turn Windows Features On or Off/SMB 1.0 to check the check box necessary for it to work. Then reboot. It worked! Thanks for the great tip @BlackJack. But I did not need to dip into the Registry. But your last question helped. Previously I tried to supply blanks for the SMB UID/pwd, and it didn’t’ work. Also “anonymous”. But due to your question, I gave “Anonymous” a shot, and it took me straight …

[Geoffrey_Binder]

Hi BlackJack,

Seems ok…

[Suedkiez (Just a fellow user like you)]

“Security policies block unauthenticated guest access”

This should be unrelated to SMB1 (Roon supports SMB2, this was confirmed in older threads about this topic), the issue is most likely, well, certain Windows versions now blocking unauthenticated guest access by default.

In know you said you did the Lanman thing, but also check your registry to confirm if that worked, as described here:

Your organization’s security policies block unauthenticated guest access

[Geoffrey_Binder]

Yeah! Thanks Suedkiez! That worked.

Much appreciated.

Cheers, Geoff