[Samba] 4.1.5, spoolss_connect_to_client and negotiated protocol
Thomas Bork
tombork at web.de
Tue Mar 4 05:45:55 MST 2014
Hi @all,
experimenting with 4.1.5 and printing I have messages like this in the log:
spoolss_connect_to_client: machine X didn't negotiate NT protocol.
machine X is a windows 7 machine.
I have following definitions in smb.conf:
lanman auth = yes
client lanman auth = yes
client plaintext auth = yes
client ntlmv2 auth = no
max protocol = SMB3 # <---------------
min receivefile size = 16384
aio read size = 16384
aio write size = 16384
client max protocol = SMB3 # <---------------
acl allow execute always = yes
Is it possible that a higher protocol will be negotiated with modern
clients with these options?
Can I quiet these messages with
print notify backchannel = no
(no connection attemps from server to client)?
Shouldn't the "print notify backchannel" default be "no" in 4.1.5 regarding
https://lists.samba.org/archive/samba-technical/2013-October/095492.html
and
https://blogs.technet.com/b/askperf/archive/2009/01/16/understanding-print-notifications-in-windows-vista.aspx?Redirected=true
?
--
der tom
More information about the samba
mailing list