And they say turntables can be temperamental 
Like fucking clockwork there’s someone along to make some specious comparison with record players.
It’s nearly 2022, lads.
2 Likes
How is it wrong ?
I don’t know. What are you crying about, exactly?
Is “they” the voices in your head?
3 Likes
The thing about computers is that they do some things without you knowing. It shouldn’t work, but does because of something like UPNP. Then you change something like the router, and that system works slightly differently, breaking stuff that only worked by accident.
The solution is to get it right. Not always easy. Oh and have your own router, so changes in ISP only affect outside that.
Christ, I feel that @sjs has massively trolled me, although actually it’s Microsoft…
After receiving the generous donation of a NAS last week, I’ve been trying to set it up. This has in general been quite easy, there’s a GUI and it mostly just works as you’d expect. It’s not supported by Lenovo any more, so you can’t get new software for it, but I don’t need much.
But getting Windows 10 to see the shares has been a fucking nightmare. Every Linux computer and phone has no problem, but the Win10 machines just aren’t having it. Checking online problem solving sites has had me fucking about with samba settings, the registry, enabling and disabling services, user accounts and permissions, nothing works. There are plenty of people online who have clearly given up trying.
Eventually I gave up on using samba and moved to nfs, another sharing protocol, but even that didn’t work without fucking about with the registry, and mounting the shares using the command line.
Generally I have found Win10 to be fairly decent, but this fuckery is outrageous. Cunts.
Disable SMB v1 on the NAS
1 Like
I got the other NAS from Simon and got it up and running with Windows 10 without too much issue. The breakthrough came when I did the opposite of Chris’ suggestion above and enabled SMB v1 on my win 10 laptop. After that, all the shares on the nas were available under Network in the windows file explorer.
In your search bar type ‘Windows features’
Click on ‘Turn windows features on or off’
In the dialog box that appears check all the SMB boxes.
Reboot pc.
Then you should find all your NAS shares to be readily accessible in file explorer under Network
fuck sake, that was going to be my sarcastic response when he said disabling v1 on the nas didn’t work.
Always a good move 
except when it comes to enabling smb v1
Sorry to spoil your fun 
I have tried these things, where possible, and nothing has worked
Reset the NAS and start again.
this is a reasonable starting position
yup, that will be it.
I cant help much as I didn’t use these boxes with Windows SMB shares, only with Linux NFS shares
I guess you have already seen the manual:
and have the NAS and PC in the same workgroup, and your account name on the pc is the same as the account name on the NAS
he’s probably not using the correct ‘magic roundabout’ themed naming convention.
1 Like
the root of many IT problems
Did you create windows credentials for your nas? These would be the username and password you created to log in to your nas during setup of the NAS.
That won’t work terribly well for the computers where the user is a different account name.
The NAS is fine, it’s Windows. Now I have it working I’m not going to change it, but it’s bloody annoying.
This is a known issue with Windows after they changed something a year or so ago. And, typically, never bothered to fix.
I’m a fucking idiot and I got it going on win 10 so there’s no issue that you can’t resolve. Adding windows credentials for the NAS in win 10 and enabling smb v1 did the trick for me.
1 Like