Mount Zenith Mk3 disk on windows 11

[hansbondeson]

I have managed my music library stored on my Zenith Mk 3 disk from a Windows 11 machine (mount the Zenith disk as a network disk drive) and everything has worked fine until just recently when windows suddenly demands a password in order to access the Zenith disk. But there is no user id and password as far as I know.
I also tested on a Linux machine, and it did not require any password for doing the same thing, I could manage the files from there.
It might be something caused by a Windows update, I don´t know. It is very convenient to be able to build a logical file structure and to manage meta data tags from the Windows machine.
I also updated the Innous software to the newest version, but still no success.
Does anybody know what might happened and if tere is any solution to the problem?

 

[guardajoias]

You should have also the option to connect as « guest » without username and password…

 

[hansbondeson]

Thanks for the reply!
That might be a possible solution that I did not test.
But, while waiting for answers, I Googled the error message that I got from my mounting tests.
And finally I found the page:
https://learn.microsoft.com/en-us/t...ing/cannot-access-shared-folder-file-explorer
where it actually worked with enabling insecure guest logons with Local Group Policy Editor by starting the program gpedit.msc and in that navigating to
Computer configuration > Administrative templates > Network > Lanmann configuration
Doubleclick "Enable insecure guest logons", click "Enabled" and "Ok"
This changes a post in the registry that allows mounting without username and password.
And after that modification, the mounting procedure of the Innous Zen disk works just as it did earlier, without user name and password.

 

[guardajoias]

Wow! that reminds me why I use a Mac

 

[hansbondeson]

All systems have their own problems, Mac also...

 

[Stephen Healy]

Many thanks for the input @hansbondeson, this would indeed be the workaround for users affected by changes Windows has made in 24H2.
There are changes we can make on our end so that in a future update to Sense we can hopefully bypass this. This is not the first time Windows has done this, so is a bit of a moving target...