I have a samba file server that I created about 20 years ago and in the
time I have done the little updates needes to new server (when I move to a
new server I copy config and adapt if needed).
It only do public file sharing.
Some week ago a client stopped to connect to the share.
Only this client (Win 10 updated to 1703 or 1709).
It can connect to other windows shares or linux samba shares, but not to
this server..
Any attempt end in a messagge like "can't connect to \\GWLAN check
ortography ..." (translation from Italian original message)
After many attempt, I reformatted and reinstalled the client from scratch.
Now the problem is still present: this client can't connect to the shares.
It connect to every other box in the LAN, but not to this box.
I can't find any useful info in the server's logs, but I noticied a
strange report from the smbstatus command:
Samba version 4.5.12-Debian
PID Username Group Machine
Protocol Version Encryption Signing
--------------------------------------------------------------------------------------------------------------------------------
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
. . . (65534 identical rows!!!)
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
12620 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:51969)
SMB3_11 - -
Service pid Machine Connected at Encryption
Signing
---------------------------------------------------------------------------------------------
share 12620 192.168.67.5 Mon Jan 8 06:24:46 PM 2018 CET -
-
hidden$ 32049 web2ka0 Tue Jan 9 03:44:49 AM 2018 CET -
-
share 14629 xp0804-xp Mon Jan 8 06:33:16 PM 2018 CET -
-
share 12635 contgwlan Mon Jan 8 06:24:56 PM 2018 CET -
-
share 32049 web2ka0 Tue Jan 9 12:58:17 AM 2018 CET -
-
IPC$ 12635 contgwlan Mon Jan 8 06:24:56 PM 2018 CET -
-
share 29712 192.168.67.243 Mon Jan 8 07:44:37 PM 2018 CET -
-
share 3619 192.168.67.242 Mon Jan 8 08:13:32 PM 2018 CET -
-
share 12613 192.168.67.95 Mon Jan 8 06:24:44 PM 2018 CET -
-
share 12603 192.168.67.243 Mon Jan 8 06:24:43 PM 2018 CET -
-
The 192.168.67.5 client is another box (a windows server 2016 that I use
as my general porpouse box from many months before the problem appear).
It works fine and don't show any symptoms of problem. Like all other
clients.
The not working client is the 192.168.67.204 (not listed)
That can connet to other samba servers or windows shares.
No DC in this LAN. only workgroup.
If I restart samba the 65534 rows disappear but after few hours I can
noticied them again in smbstatus report.
65534 is so close to the 65536 magic number that I can't think it is a
coincidence :-)
My smb.conf:
============================================================================[global]
workgroup = APF
server string = APF Server Version %v
netbios name = GWLAN
interfaces = lo eth0 192.168.67.254/24
hosts allow = 127. 192.168.67.
log file = /var/log/samba/log.%m
max log size = 5000
guest account = mondo
security = user
map to guest = bad user
passdb backend = tdbsam
load printers = no
cups options = raw
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
writable = no
printable = yes
[share]
writeable = yes
public = yes
path = /DATA/HOME/share/public
guest ok = yes
comment = Area Condivisa
read only = no
writable = yes
printable = no
inherit permissions = yes
create mode = 0664
veto files = /.flexshare*/
recycle:repository = .trash/%U
recycle:maxsize = 0
recycle:versions = Yes
recycle:keeptree = Yes
recycle:touch = No
recycle:directory_mode = 0775
vfs object = recycle:recycle
[hidden$]
comment = Area Condivisa
path = /DATA/HOME/public/hidden
read only = no
writable = yes
printable = no
inherit permissions = yes
create mode = 0664
guest ok = yes
public = yes
only guest = yes
[condiv]
guest ok = yes
public = yes
only guest = yes
comment = Area Condivisa Spool
path = /home/mondo
read only = no
writable = yes
============================================================================
Are these things related?
Thanks for any help/advice :-)
B.
On Sat, 13 Jan 2018 20:10:08 +0100 (CET) "Barbara M. via samba" <samba at lists.samba.org> wrote:> > I have a samba file server that I created about 20 years ago and in > the time I have done the little updates needes to new server (when I > move to a new server I copy config and adapt if needed). > It only do public file sharing. > > Some week ago a client stopped to connect to the share. > Only this client (Win 10 updated to 1703 or 1709). > It can connect to other windows shares or linux samba shares, but not > to this server.. > Any attempt end in a messagge like "can't connect to \\GWLAN check > ortography ..." (translation from Italian original message) >Microsoft has turned off SMBv1 in windows 10, so this is likely to be your reason (note that I don't say problem), try adding this to smb.conf: server min protocol = smb2 Then restart Samba. Rowland
On Sat, 13 Jan 2018, Rowland Penny wrote:>> I have a samba file server that I created about 20 years ago and in >> the time I have done the little updates needed to new server (when I >> move to a new server I copy config and adapt if needed). >> It only do public file sharing. >> >> Some weeks ago a client stopped to connect to the share. >> Only this client (Win 10 updated to 1703 or 1709). >> It can connect to other windows shares or linux samba shares, but not >> to this server.. >> Any attempt end in a messagge like "can't connect to \\GWLAN check >> ortography ..." (translation from Italian original message) > > Microsoft has turned off SMBv1 in windows 10, so this is likely to be > your reason (note that I don't say problem), try adding this to > smb.conf: > > server min protocol = smb2 > > Then restart Samba.It worked fine until some weeks ago. I reinstalled the box and worked fine for a couple of weeks (this box is only used about twice for week). I have about 10 other boxes with windows 10 that works without problems (some always on other sporadic guests). Like the 2016 boxe (that seems to generate the other "problem" of the 65534 rows in the smbstatus report). And some Win 7, Win XP, ... Anyway, tried your hint. No difference for the specific win 10 client. Still can't connect. All other Win 10 and the 2016 tested still works as usual. smbstatus still reports the "strange" rows: Samba version 4.5.12-Debian PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 6358 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:58761) SMB3_11 - - 6358 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:58761) SMB3_11 - - 6358 mondo mondo 192.168.67.5 (ipv4:192.168.67.5:58761) SMB3_11 - - . . . but only 16650 (until now). The only real difference is that a couple of old VMs with win 98 (yes there is the need to keep them alive), now can't connect to the server :-) Thanks, B.