From 48e547c0734f9f646b7683059552c503c809b8ed Mon Sep 17 00:00:00 2001
From: Andrew Bartlett <abartlet@samba.org>
Date: Fri, 14 Sep 2012 12:04:00 -0700
Subject: [PATCH] docs: Remove confusing reference to smb signing and client
 use spnego

This section is more confusing than helpful, as client support for both is on by default.

Andrew Bartlett
---
 docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml | 19 -------------------
 1 file changed, 19 deletions(-)

diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
index fb81ac0b34d..5cb2a43db63 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-DomainMember.xml
@@ -1286,24 +1286,5 @@ account to which the Samba backend database account can be mapped.
 </para>
 
 </sect2>
-
-<sect2>
-	<title>I Can't Join a Windows 2003 PDC</title>
-
-	<para>
-<indexterm><primary>SMB signing</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>Windows 2003</primary></indexterm>
-<indexterm><primary>SMB/CIFS</primary></indexterm>
-	Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0.
-	Set <smbconfoption name="client use spnego">yes</smbconfoption> when communicating 
-	with a Windows 2003 server. This will not interfere with other Windows clients that do not
-	support the more advanced security features of Windows 2003 because the client will simply
-	negotiate a protocol that both it and the server suppport. This is a well-known fall-back facility
-	that is built into the SMB/CIFS protocols.
-	</para>
-
-</sect2>
-
 </sect1>
 </chapter>
-- 
2.11.4.GIT