On Thu, 2021-10-28 at 09:13 +0100, Nick Howitt via samba
wrote:>
> On 27/10/2021 22:56, Gilles via samba wrote:
> > Hello,
> >
> > I'm finally upgrading from Windows7 (I know) and notice that my
> > new
> > computer running Windows10 can't see a Samba 4.5.16 share running
> > on
> > Debian. It's fine when working from the Windows7 host.
> >
> > I tried the following tips, but the Samba share still doesn't show
> > up in
> > Windows10's Network*:
> >
https://serverfault.com/questions/720332/cannot-connect-to-linux-samba-share-from-windows-10
> >
> >
https://community.spiceworks.com/topic/2148301-samba-4-and-windows-10-file-sharing
> >
> >
> > Here's my smb.conf:
> > ======= START
> > [global]
> > ;MADE NO DIFFERENCE, SO COMMENTED OUT
> > ;so Win10 sees Samba shares
> > ;client min protocol = SMB2
> > ;client max protocol = SMB3
> > ;MADE NO DIFFERENCE, SO COMMENTED OUT
> > ;smb ports = 139
> > ;LAST TRY BUT STILL NO CIGAR
> > ntlm auth = yes
> >
> > ;BELOW IS THE STUFF THAT WORKS FINE WITH WINDOWS7
> > workgroup = WORKGROUP
> > netbios name = DEBIAN
> > security = user
> > map to guest = Bad User
> > ;map to guest = Bad Password
> >
> > ;www-data used by Nginx
> > guest account = www-data
> >
> > hosts allow = 127.0.0.1 192.168.0.0/24
> > hosts deny = 0.0.0.0/0
> >
> > ;to solve the "WINS server 127.0.0.1 timed out registering
IP"
> > message
> > bind interfaces only = yes
> > interfaces = 192.168.0.15/255.255.255.0 127.0.0.1/255.255.255.255
> > ;BAD? interfaces = lo eth0
> >
> > log level = 2
> >
> > wins support = yes
> > local master = yes
> > preferred master = yes
> > domain master = yes
> > os level = 255
> >
> > ;this avoids needless errors in the logs if you have no printer
> > printcap name = /dev/null
> > load printers = no
> > printing = bsd
> >
> > [nginx]
> > path = /usr/share/nginx
> > ;comment = No need for Unix/Samba passwords
> > guest ok = yes
> > writeable=yes
> > ;valid users=www-data
> >
> > browseable=yes
> >
> > force create mode = 0644
> > create mask = 0664
> > security mask = 0664
> > force security mode = 0664
> > ========== END
> >
> > Does someone have a working smb.conf I could use?
> >
> > Thank you.
> >
> > * and "net view" fails with error 1231, but it's
apparently
> > expected
> > since it was based on SMB1, which Microsoft has disabled for
> > security
> > reason
> >
> >
> Have a look at installing wsdd. Micro$oft killed of being able to
> view
> Networks in Win10 with the old SMB1 method.
>
What he said, plus upgrade from Samba 4.5.16, it is dead, the funeral
was held quite sometime ago :-)
Rowland