Using Samba Drive 4.9.4 under with windows 10

[matzi]

Last one: PC and NAS cable hooked up to router: write/read 85/100MB/s

Do I have low speed wlan adapter? is there a speed test tool for that?

[matzi]

first occurrence:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LanmanWorkstation\Parameters
second:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

I run Win 10 Pro

[fvdw]

if you use win 10 pro you can also use group policy editor to allow unsecure guest login
In gpedit : computer configuration->administrative templates->network->Lanman-workstation->enable unsecure guest logins
Also setting it to not configured will allow unsecure guest login. Of course the registry you have added can be removed if you go the way via gpedit.msc

[wd9895]

Hi fvdw,

the function that the NAS (or network) share are shown in a W10 explorer is only worlking under SMB1.
That's what I've been told in a Windows administrator forum. If you disable your SMB1 settings all will be gone or let's say: invisible.

Of course the share remain availablw writing \\NAS-name\share_name or \\NAS-IP\share_name

If I enable my SMB1 settings like in your picture all my shares are visible as in your example.
As I want to avoid SMB1 I disabled all these option getting this little disadvantage.

[fvdw]

H wd9895, yes that is correct, if you disable those settings you will not see the nas in network overview, even not windows computers that have shared folders.
You can still list shared folders on the nas in explorer by using \\name-nas or \\ip-nas in explorer adress bar, so no need to add sharename, think I do not know from head all names of the shared folder on my nas :whistle so would be anoying to find a specific shared folder.

Furthermore disabling smb1 on windows pc makes little sense to me as long as you are with your pc in a private local network at home,for sure if your nas works with smb2/3 protocols only, but of course you may have a different opinion.

Tip:
you can also use the fvdw-sl-assistant to find the nas and explore the shared folders on it by clicking the explore button in fvdw-sl assistant. The assistant uses an other way to detect the nas in the network.

[matzi]

Hi fvdw,
Of course the share remain availablw writing \\NAS-name\share_name or \\NAS-IP\share_name

This is exactly the problem where I came from. If the guest authentification in windows is not activated or Jockos smb.conf trick is not done, I cannot access the shares with windows explorer. With WinSCP it works.

The speed issue for me is solved. We found that is very much depending on the kind of network configuration (LAN,WLAN, Repeater, Switch...)

[matzi]

Maybe with some new options in smb.conf, we can fix your issue without editing your win10 environment.

First edit smb.conf file by replacing the lines :

Code: Select all

server min protocol = SMB2
client min protocol = SMB2

(if you have disabled smb1) by

Code: Select all

server min protocol = SMB2_10
client min protocol = SMB2

Jocko, I tried your proposal also on 5big2 but here it fails because smb.conf is oviously rewritten at boot. So my change is not persistent!?

Another thought:
asking windows power shell for smb connections the result is still empty:

PS C:\WINDOWS\system32> Get-SmbConnection
PS C:\WINDOWS\system32>

is there a chance that my router does not forward smb3? I have AVM ios 7.12 but their description is not quite clear about this.

[Jocko]

Hi matzi

Indeed a reboot rewrite smb.conf file. I go to send you a pm to install a new file which set the new smb.conf version.
So store it in fvdw share and do

Code: Select all

mv /etc/finc/smbfunc_conf_commit.finc /etc/finc/smbfunc_conf_commit.finc.org
tar -xf /direct-usb/fvdw/new-smb-conf.tgz -C /

Then edit a share to force smb.conf rewriting

About smb3, you can try to force it by replacing SMB2_10 by SMB3 in smb.conf and see if you still have access on the share after killing and restarting smbd

is there a chance that my router does not forward smb3? I have AVM ios 7.12 but their description is not quite clear about this.

I do not think a router may locked a smb3 exchange between two host on the LAN, only it may or not support smb2 or smb3 for its sharing on the LAN
That was a point I did not understand on your win10 as it should try to use by default smb3 and its sub-version and not use directly smb2 protocol.

I need to search on WEB if you can disable smb3 on win10 (which would be amazing :whistle but you can disable smb1 and also smb2)


----edit----
It seems with the new php version on the board we have an issue with the pm feature.
So attached the tarball

[fvdw]

Another thought:
asking windows power shell for smb connections the result is still empty:
Quote:
PS C:\WINDOWS\system32> Get-SmbConnection
PS C:\WINDOWS\system32>


is there a chance that my router does not forward smb3? I have AVM ios 7.12 but their description is not quite clear about this.

You will only get output there when you have opened a shared folder on the nas

here output on my system, nas online but no shared folder openend in explorer

Code: Select all

PS C:\WINDOWS\system32> Get-SmbConnection
PS C:\WINDOWS\system32>

now after opening network in explorer on

Code: Select all

PS C:\WINDOWS\system32> Get-SmbConnection

ServerName    ShareName UserName       Credential     Dialect NumOpens
----------    --------- --------       ----------     ------- --------
192.168.1.190 IPC$      Frans-W7\Frans Frans-W7\Frans 3.1.1   0


PS C:\WINDOWS\system32>

now when opening a shared folder

Code: Select all

PS C:\WINDOWS\system32> Get-SmbConnection

ServerName    ShareName UserName       Credential     Dialect NumOpens
----------    --------- --------       ----------     ------- --------
192.168.1.190 fvdw      Frans-W7\Frans Frans-W7\frans 3.1.1   1
192.168.1.190 IPC$      Frans-W7\Frans Frans-W7\frans 3.1.1   0
192.168.1.190 public    Frans-W7\Frans Frans-W7\frans 3.1.1   0


PS C:\WINDOWS\system32>

Note that some lines are only visible shortly after opening the shared folder

[matzi]

That looks better:

PS C:\WINDOWS\system32> Get-SmbConnection

ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
FVDWSL-BASE-PI IPC$ PAPA\Papa PAPA\Papa 3.1.1 0
FVDWSL-BASE-PI Volume_1 PAPA\Papa PAPA\Papa 3.1.1 0