mirror of
https://github.com/samba-team/samba.git
synced 2024-12-25 23:21:54 +03:00
477e53a8cb
In handling RemoteFindFirstPrinterChangeNotifyEx requests, the spoolss server can establish a "backchannel" connection to the print client, as a mechanism for sending print notifications. This behaviour is governed by the "print notify backchannel" smb.conf parameter. This change sets "print notify backchannel" to "no" by default, which sees Samba respond to RemoteFindFirstPrinterChangeNotifyEx requests with WERR_SERVER_UNAVAILABLE. In recieving such a response, print clients can fall back to polling for print queue changes. Signed-off-by: David Disseldorp <ddiss@samba.org> Reviewed-by: Günther Deschner <gd@samba.org> Autobuild-User(master): Günther Deschner <gd@samba.org> Autobuild-Date(master): Mon Oct 14 18:49:41 CEST 2013 on sn-devel-104
18 lines
696 B
XML
18 lines
696 B
XML
<samba:parameter name="print notify backchannel"
|
|
context="S"
|
|
print="1"
|
|
type="boolean"
|
|
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
|
|
<description>
|
|
<para>Windows print clients can update print queue status by expecting
|
|
the server to open a backchannel SMB connection to them. Due to
|
|
client firewall settings this can cause considerable timeouts
|
|
and will often fail, as there is no guarantee the client is even
|
|
running an SMB server. By default, the Samba print server will
|
|
not try to connect back to clients, and will treat corresponding
|
|
requests as if the connection back to the client failed.
|
|
</para>
|
|
</description>
|
|
<value type="default">no</value>
|
|
</samba:parameter>
|