plugout.net

Ok Matzi

It would be nice you try tomorrow after re-open your win10 session:
Restore the original value in registry
set a private share on the SD card and keep public the usb share
Try to open the private share => should ask you for login => Do you succeed to open it ?
Then try to open the public share => win10 should reuse quietly the account => Do you succeed to open it ?

:z)

Hi 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

You can use directly nano command to do it

Code: Select all

nano /tmp/usr/lib/smb.conf


reboot smb daemon

Code: Select all

killall smbd
/usr/sbin/smbd -D -l /var/log/samba

That all on the rspb side

Now restore the default environment on your win10 and restart the session.

Then check if you can get share list on your rspb and connect to one

The trick is on smb2_10, guest account would not be blocked so by setting it as min protocol on the server, win10 can no longer use smb2 which is the issue

Restore the original value in registry - done
set a private share on the SD card and keep public the usb share - done
Try to open the private share => should ask you for login => Do you succeed to open it ? - No, all shares are visible. The publics shares are accessible, the private share asks for credentials but does not accept it


Then try to open the public share => win10 should reuse quietly the account => Do you succeed to open it ? - Yes, see line before.

The solution with the modified smb.conf works fine. I can access both share types. Windows Explorer silently kept the credentials from the tril before and used it (this time successfully).

:thumbup
And what about writing speed ?

Hi matzi,

matzi wrote:The publics shares are accessible, the private share asks for credentials but does not accept it

This is still amazing :scratch that would be an host/login account is already using by win10 and the user (login) has no permission on your raspberry share. With win10 home (like older versions) you can use only one user account on remote share

matzi wrote:The solution with the modified smb.conf works fine. I can access both share types. Windows Explorer silently kept the credentials from the tril before and used it (this time successfully).

we still need to deepen something with fvdw as the trick seems do not work on his side

writing is about 18-20 MB/s
Reading at about 12 MB/s

It is through a 300Mbit wlan repeater-

Now I going for family sunday- Let us continue later

More speed test results: Raspi Nas connected directly to PC (Ethernet Cat 7 Cable, both ends fixed IP) results in amazing read/write speeds both about 100MB/s!
So I guess there is a bottleneck in my router (AVM 7580 and Repeater AVM 450E).

and another one: PC WLAN connected to router. NAS with ethernet on router
write/read 12/25MB/s

well there seems to be indeed a restriction in your lan.

question: which windows 10 do you use ?( home, eduction, pro, enterprise) ?

and you mentioned yopu entered the key in registry on two places, Where exactly ?