added instructions advising people to set up 1.9.18alpha as a Win95 Domain

Logon server, with encrypted passwords *prior* to trying out the NT Domain
Logons.
(This used to be commit f39608ec065503920aafed9655178ce36e67f1f9)

1 files changed, 16 insertions, 0 deletions

diff --git a/docs/textdocs/NTDOMAIN.txt b/docs/textdocs/NTDOMAIN.txt
index c469946a2d..9a254b5c6b 100644
--- a/docs/textdocs/NTDOMAIN.txt
+++ b/docs/textdocs/NTDOMAIN.txt
@@ -14,12 +14,28 @@ without the need, use or intervention of NT Server.  This document describes
 how to set this up.  Over the continued development of the 1.9.18alpha
 series, this process (and therefore this document) should become simpler.
 
+One useful thing to do is to get this version of Samba up and running
+with Win95 profiles, as you would for the current stable version of
+Samba (currently at 1.9.17p4), and is fully documented.  You will need
+to set up encrypted passwords.  Even if you don't have any Win95 machines,
+using your Samba Server to store the profile for one of your NT Workstation
+users is a good test that you have 1.9.18alpha1 correctly configured *prior*
+to attempting NT Domain Logons.
+
 The support is still experimental, so should be used at your own risk.
 
 NT is not as robust as you might have been led to believe: during the
 development of the Domain Logon Support, one person reported having to
 reinstall NT from scratch: their workstation had become totally unuseable.
 
+[further reports on ntsec@iss.net by independent administrators showing
+ similar symptoms lead us to believe that the SAM database file may be
+ corruptible.  this _is_ recoverable (or, at least the machine is accessible),
+ by deleting the SAM file, under which circumstances all user account details
+ are lost, but at least the Administrator can log in with a blank password.
+ this is *not* possible except if the NT system is installed in a FAT
+ partition.]
+
 This *has* been reported to the NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM digest.