summaryrefslogtreecommitdiffstats
path: root/docs/textdocs/WinNT.txt
diff options
context:
space:
mode:
authorJohn Terpstra <jht@samba.org>1997-06-28 23:29:05 +0000
committerJohn Terpstra <jht@samba.org>1997-06-28 23:29:05 +0000
commite61846a9c10420132ac3dbcb9c7663bcface9559 (patch)
tree904936f548a247666a8837b7a95ebe92def7c33a /docs/textdocs/WinNT.txt
parent4f6ad2654f40b1170640876bb15f88a40568fb2e (diff)
downloadsamba-e61846a9c10420132ac3dbcb9c7663bcface9559.tar.gz
samba-e61846a9c10420132ac3dbcb9c7663bcface9559.tar.xz
samba-e61846a9c10420132ac3dbcb9c7663bcface9559.zip
JHT ==> Been playing again! Whooooooo!
(This used to be commit 707172b4fb8ee39f5e0f30dab844eca27bc5362c)
Diffstat (limited to 'docs/textdocs/WinNT.txt')
-rw-r--r--docs/textdocs/WinNT.txt41
1 files changed, 27 insertions, 14 deletions
diff --git a/docs/textdocs/WinNT.txt b/docs/textdocs/WinNT.txt
index b57abb7742e..772ef74a4c0 100644
--- a/docs/textdocs/WinNT.txt
+++ b/docs/textdocs/WinNT.txt
@@ -1,6 +1,14 @@
-There are some particular issues with Samba and Windows NT
+Contributor: Various
+Updated: June 27, 1997
+Status: Current
-=====================================================================
+Subject: Samba and Windows NT Password Handling
+=============================================================================
+
+There are some particular issues with Samba and Windows NT.
+
+Passwords:
+==========
One of the most annoying problems with WinNT is that NT refuses to
connect to a server that is in user level security mode and that
doesn't support password encryption unless it first prompts the user
@@ -8,21 +16,31 @@ for a password.
This means even if you have the same password on the NT box and the
Samba server you will get prompted for a password. Entering the
-correct password will get you connected.
+correct password will get you connected only if Windows NT can
+communicate with Samba using a compatible mode of password security.
+
+All versions of Windows NT prior to 4.0 Service Pack 3 could negotiate
+plain text (clear text) passwords. Windows NT 4.0 Service Pack 3 changed
+this default behaviour so it now will only handle encrypted passwords.
+The following registry entry change will re-enable clear text password
+handling:
+
+Run regedt32.exe and locate the hive key entry:
+HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\rdr\parameters\
+
+Add the following value:
+ EnablePlainTextPassword:REG_DWORD=1
+
The other major ramification of this feature of NT is that it can't
browse a user level non-encrypted server unless it already has a
connection open. This is because there is no spot for a password
prompt in the browser window. It works fine if you already have a
drive mounted (for example, one auto mounted on startup).
-
-Samba should support encrypted passwords soon, which will solve this
-problem.
=====================================================================
-
-
-=====================================================================
+Printing:
+=========
When you mount a printer using the print manager in NT you may find
the following info from Matthew Harrell <harrell@leech.nrl.navy.mil>
useful:
@@ -49,8 +67,3 @@ time for the NT machine to get verification that the printer queue
actually exists.
I hope this helped in some way...
------------
-=====================================================================
-
-
-