From 4b347a1b17549a3807d9448866fa37dcb293c4e7 Mon Sep 17 00:00:00 2001
From: Volker Lendecke <Volker.Lendecke@SerNet.DE>
Date: Fri, 18 Mar 2011 12:07:43 -0700
Subject: s3: Add "print notify backchannel" parameter to prevent us doing the
 reverse print notify connection.

Autobuild-User: Jeremy Allison <jra@samba.org>
Autobuild-Date: Fri Mar 18 21:34:30 CET 2011 on sn-devel-104
---
 .../smbdotconf/printing/printnotifybackchannel.xml     | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 docs-xml/smbdotconf/printing/printnotifybackchannel.xml

(limited to 'docs-xml')

diff --git a/docs-xml/smbdotconf/printing/printnotifybackchannel.xml b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml
new file mode 100644
index 0000000000..f895f9c70c
--- /dev/null
+++ b/docs-xml/smbdotconf/printing/printnotifybackchannel.xml
@@ -0,0 +1,18 @@
+<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 setting this parameter to <constant>no</constant>
+	the Samba print server will not try to connect back to clients
+	and treat corresponding requests as if the connection back to
+	the client failed. The default setting of <constant>yes</constant>
+	causes smbd to attempt this connection.
+</description>
+<value type="default">yes</value>
+</samba:parameter>
-- 
cgit