New
#11
So, are you saying that your computer has SMB2 under Parameters? I would hazard an educated guess that it doesn't. I have four win 10 10240 comps here and only one had the SMB2 entry, and, guess what, that was the only one that failed with the path not found error. I have tried entries of SMB1, SMB2, SMB3, SMB4 and only SMB2 gives the failure that can be seen on all my comps, including a win 8.1 one. The effect is totally repeatable.
The 'hack', as you call it, does nothing but make file sharing work as intended and can hardly be controversial considering only one of my comps has it and I suspect the SMB2 entry comes from Vista days.
I also don't think this problem has anything to do with how your shares are set up or, indeed, whether you have any shares set up at all as this gives an Empty Folder' message on a working system. My supposition is that it is a protocol issue and the Lanman Server doesn't acknowledge the request for share info hence the Lanman Client's response that there is no path to the server.
Something was changed in win 10 sometime after 10130 as I reverted one of my comps to 10130 and the path not found error wasn't there.
As for reverting to SMB1, I don't agree that is happening as I quote below:-
Q: How can I quickly check what version of SMB is being used between my machine and the server?
A: There are now several different versions (or dialects) of the SMB protocol that were introduced with different versions of Windows:
- SMB 1 - Windows 2000
- SMB 2 - Windows Server 2008 and WIndows Vista SP1
- SMB 2.1 - Windows Server 2008 R2 and Windows 7
- SMB 3.0 - Windows Server 2012 and Windows 8
The version of SMB used between a client and the server will be the highest dialect supported by both the client and server.
This means if a Windows 8 machine is talking to a Windows 8 or Windows Server 2012 machine, it will use SMB 3.0. If a Windows 8 machine is talking to Windows Server 2008 R2, then the highest common level is SMB 2.1.