SMB/Samba server version

YuppieScum

New Member
After the recent SMB unpleasantness, I - like many others here, I suspect - have been following Microsoft's advice on disabling SMBv1 on my Windows machines.

However, on disabling the SMBv1 client, I can no longer connect to the shares on my Humax.

Are there plans for updating SAMBA support on the T2 to version 2 (or later)? I'd rather not keep the v1 client active on Windows just for this...

Cheers,
YS
 
After the recent SMB unpleasantness, I - like many others here, I suspect - have been following Microsoft's advice on disabling SMBv1 on my Windows machines.

However, on disabling the SMBv1 client, I can no longer connect to the shares on my Humax.
Yes, I tried it last week and lost access to mostly everything on various machines (Windows, Linux, Humax).
Are there plans for updating SAMBA support on the T2 to version 2 (or later)? I'd rather not keep the v1 client active on Windows just for this...
It doesn't seem like it's going to happen. From what I can deduce, one person built it (Samba and Cifs) originally and it was a bit of a lash up to get going. No-one else has managed a build since. It's becoming a nuisance for at least two (in)compatibility reasons.
 
I had to disable smb3 on my W10 machines for then to see my two NASs, leaving smb1&2 alone.
 
I've just hit this problem (no longer able to access the shares on my Humax from Windows 10). Has anyone found a way of re-enabling SMB1 on Windows 10? I've tried 2 methods (one from the command line, one in the registry editor), but I still can't access the Humax shares.
 
I can access my Hummy with W10 without any mucking about with Samba versions.
The only probs I had are remarked on a couple of posts ago.
Read the post above that implies that if you disable SMB1, you can't connect to Hummy. So it must be 'something else', but no ideas as to what.
 
I think I may have found the answer (for me at least). I've just re-installed the SMB1 client in Programs and Features, and can now see the Humax shares again. I'm sure that it's less secure than SMB2/3, but I think I can live with it. I've also disabled future Windows 10 updates, as this is third thing in the last month that I've noticed being broken by an O/S update.
 
Irrelevant if the server you are trying to access doesn't support SMB2/3. Other servers should negotiate the best protocol.
That's my way of thinking. Although a security specialist would probably point out that preventing access to any potentially compromised server using a vulnerable protocol is a good idea.
 
Back
Top