Web lists-archives.com

Re: [Samba] User mapping/login issue




Ps. Smb1 in Win10 ! I mean ofcourse.. 

Step 1: Go to Start button and type Control Panel. You will get Control Panel; Desktop app. Click on it.
Step 2: You will get a window with a list of software on it, go to the left side of the panel and click Turn Windows Features On or Off.
Step 3:  You need to remove the checkmark beside SMB 1.0/CFs File Sharing Support to disable SMB1 for good. If you want to enable it, put a checkmark beside the same.

And after seeing this, 
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/fac3655a-7eb5-4337-b0ab-244bbcd014e8 
@Rowland, can you do a read in this one. 

Your english is better then mine, but i do think this is related. 
Could bug#13698 (marked fixed today) also have influence here. 

And might be related: 
https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser
Cant think of much more. 


Greetz, 

Louis


> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces@xxxxxxxxxxxxxxx] Namens 
> L.P.H. van Belle via samba
> Verzonden: donderdag 25 april 2019 10:00
> Aan: samba@xxxxxxxxxxxxxxx
> Onderwerp: Re: [Samba] User mapping/login issue
> 
> Hai, 
> 
> > -----Oorspronkelijk bericht-----
> > Van: samba [mailto:samba-bounces@xxxxxxxxxxxxxxx] Namens 
> > Stephen Davies via samba
> > Verzonden: donderdag 25 april 2019 8:34
> > Aan: samba@xxxxxxxxxxxxxxx
> > Onderwerp: Re: [Samba] User mapping/login issue
> > 
> > > 
> > It would appear that there may be more than one issue with 
> my smb.conf.
> > The scenario is a Centos 7 Linux server with a bunch of LAN 
> connected windows 
> > 10 clients and several remote windows 10 clients which 
> connect via VPN.
> > The server firewall accepts everything from the VPN.
> > The server and local clients are all in workgroup BENPARTS 
> while the remote 
> > clients are either stand-alone or in different workgroups/domains.
> > Local SMB access works as expected but remote access does 
> not due to password 
> > failures (as described in earlier log excerpts).
> > What should the domain-related entries in smb.conf be to 
> support this scenario?
> >
> > Cheers and thanks,
> > Stephen
> > 
> 
> I can only think of these last 3 things. 
> First try enable smb1 again in windows 10 again. I noticed ms 
> changed things again. 
> Thinking here that the "older samba" your using, with a 
> latest windows is the problem. 
> Enable smb1 again, think that will fix a lot. 
> 
> And your sure you vpn line is ok and you dont have packetloss? 
> Think in test with mtr or smokeping, something like that. 
> 
> Are the MTU sizes are handled by the firewall? 
> This is to prevent IP packet fragmentation, so IPTables is 
> set to reduce the size of packets by adjusting the packets' 
> maximum segment size.
> Something like this: iptables -A PREROUTING -i ethX -p tcp -m 
> tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1361:1536 -j 
> TCPMSS --set-mss 1360
> 
> Greetz, 
> 
> Louis
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
> 


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba