[Samba] 4.1.5, spoolss_connect_to_client and negotiated protocol
David Disseldorp
ddiss at suse.de
Fri Mar 7 05:53:40 MST 2014
Hi Thomas,
On Fri, 07 Mar 2014 13:07:02 +0100, Thomas Bork wrote:
> The message was printed anyway with Windows 7, which should reject null
> session pipes, according to the lanman parameters:
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
> "ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
>
> 00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
> 73,00,72,00,76,00,73,00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,00
> "ServiceDllUnloadOnStop"=dword:00000001
> "EnableAuthenticateUserSharing"=dword:00000001
> "NullSessionPipes"=hex(7):00,00
> "autodisconnect"=dword:0000000f
> "enableforcedlogoff"=dword:00000001
> "enablesecuritysignature"=dword:00000000
> "requiresecuritysignature"=dword:00000000
> "restrictnullsessaccess"=dword:00000001
> "Lmannounce"=dword:00000000
> "Size"=dword:00000001
> "AdjustedNullSessionPipes"=dword:00000003
> "Guid"=hex:5e,b5,dd,a3,b4,6c,59,4e,bb,2a,2a,c8,70,0a,ff,cf
Yes, you'll need to modify your registry to accept the backchannel
connection. Looks like you're already aware of that :-)
https://blogs.technet.com/b/askperf/archive/2009/01/16/understanding-print-notifications-in-windows-vista.aspx?Redirected=true
>
> > @Thomas, if you're willing to test backchannel notifications against
> > an SMB2+ print client, I can send you a 4.1 based patch or rpm.
>
> As patch please :-)
Patch against v4-1-test branch attached. Thanks!
Cheers, David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-spoolss-permit-SMB2-notification-backchannels.patch
Type: text/x-patch
Size: 1439 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140307/24e2744d/attachment.bin>
More information about the samba-technical
mailing list