Hello. On st?eda 14. ?ervence 2021 14:37:24 CEST Rowland Penny via samba wrote:> On Wed, 2021-07-14 at 14:23 +0200, Oleksandr Natalenko via samba wrote: > > On st?eda 14. ?ervence 2021 14:04:28 CEST L.P.H. van Belle via samba > > > > wrote: > > > Have you followed this : > > > https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server > > > > > > Basicly its, guest access is denied on SMB2 > > > Adjust the smb.conf as shown in the link. > > > And test again. > > > > OK, thanks for the pointer. I understand what's going on now after > > seeing the > > "guest access is denied on SMB2" phrase. > > No, guest access isn't denied on SMB2, but Windows 10 now refuses to > allow guest access by default.Windows 10 is not really involved in this scheme.> From the log fragment posted it looks like the android client isn't > sending the proper data: 'Bad SMB2 signature for message'Yes, probably. But as the x-plore devs didn't respond to this concern, I started to look for other options.> > I've adjusted the config, and now X-plore connects just fine. The > > config looks > > like this now: > > > > ``` > > [global] > > > > disable spoolss = Yes > > domain master = No > > load printers = No > > name resolve order = host > > printcap name = /dev/null > > server string = Samba Server %v > > show add printer wizard = No > > socket options = TCP_NODELAY SO_KEEPALIVE > > idmap config * : backend = tdb > > printing = bsd > > valid users = __guest > > Where did the '__guest' user come from ?From useradd+smbpasswd. -- Oleksandr Natalenko (post-factum)
On Wed, 2021-07-14 at 14:51 +0200, Oleksandr Natalenko via samba wrote:> Windows 10 is not really involved in this scheme.Never said it was, just pointing out that Win10 no longer allows the use of a guest share unless you modify the registry, but Samba still allows guest access, just not from an unmodified win10 machine.> > > From the log fragment posted it looks like the android client isn't > > sending the proper data: 'Bad SMB2 signature for message' > > Yes, probably. But as the x-plore devs didn't respond to this > concern, I > started to look for other options.I suggest that if the people that wrote your app cannot (or will not) help, then you should find an app that works.> > > > I've adjusted the config, and now X-plore connects just fine. The > > > config looks > > > like this now: > > > > > > ``` > > > [global] > > > > > > disable spoolss = Yes > > > domain master = No > > > load printers = No > > > name resolve order = host > > > printcap name = /dev/null > > > server string = Samba Server %v > > > show add printer wizard = No > > > socket options = TCP_NODELAY SO_KEEPALIVE > > > idmap config * : backend = tdb > > > printing = bsd > > > valid users = __guest > > > > Where did the '__guest' user come from ? > > From useradd+smbpasswd. >Thought so. Even though your user has 'guest' as part of its name, it isn't a guest user, it is just a Samba user and you are now using password authentication. Rowland