No longer can access my Samba shares

Operating Systems & Open Source Windows
1

I upgraded to Windows 10 today and with the exception of my Focusrite 2i2 not working, the only other issue I have is that I cannot access my Samba shares from my fileserver. I have tried ALOT of solutions, including adding a reg entry to windows that allows the unsecure authentication (apparently MS updated the way the security works and it's the cause)
I also tried removing any security requirements on the linux side, but still no luck.

Anyone have any ideas? And please dont tell me to install a different os on the fileserver. Ubuntu server edition with MATE desktop is working just fine for me. (well other than this new problem)

I've also tried while being in a workgroup and not. I've tried with Windows controlling passwords and shares, and with "Use user names and passwords to connect" but nothing works. The only change I have manged to get is certain network and workgroup settings make the server not visable at all, while being in a homegroup and using "use usernames and passwords to connect to other pc's" i can see my server and see the shares, but when i try to access them i get an error saying i do not have permission.

I am stuck. Any help would be great.

2

It could be that the file server is using an older version of samba that is disabled in Windows 10. I don't know enough about samba to know how to check that or fix it but I would look into that to make sure it isn't the problem.

3

Actually not a bad answer at all. That was something I discovered in my journey of trying to fix this. I was able to determine that I am running a 4.0+ version of Samba and i'm using SMB 2.0/3.0 instead of 1.0 (1.0 does not work in Windows anymore apparently)
This still does not resolve my issue.
I though maybe it was because I am on Windows 10 home, but that doesn't seem to be a factor in this according to the interenets.

4

it depends if the smb/cifs protocols changed in the new version and microsoft is pretty good at updating them with a full version upgrade. look on the smb/samba message boards.

you could try an alternative protocol like ssh until these issues are resolved or understood.