2 !== WinNT.txt for Samba release TNG-alpha 01 May 2000
5 Password Section - Copyright (C) 1997 - John H Terpstra
6 Printing Section - Copyright (C) 1997 - Matthew Harrell
7 Priting Info - Copyright (C) 1997 - Frank Varnavas
8 Updated: October 16, 1997
11 Subject: Samba and Windows NT Password Handling
12 =============================================================================
14 There are some particular issues with Samba and Windows NT.
18 One of the most annoying problems with WinNT is that NT refuses to
19 connect to a server that is in user level security mode and that
20 doesn't support password encryption unless it first prompts the user
23 This means even if you have the same password on the NT box and the
24 Samba server you will get prompted for a password. Entering the
25 correct password will get you connected only if Windows NT can
26 communicate with Samba using a compatible mode of password security.
28 All versions of Windows NT prior to 4.0 Service Pack 3 could negotiate
29 plain text (clear text) passwords. Windows NT 4.0 Service Pack 3 changed
30 this default behaviour so it now will only handle encrypted passwords.
31 The following registry entry change will re-enable clear text password
34 Run regedt32.exe and locate the hive key entry:
35 HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Rdr\Parameters\
37 Add the following value:
38 EnablePlainTextPassword:REG_DWORD=1
40 Alternatively, use the NT4_PlainPassword.reg file in this directory (either
41 by double clicking on it, or run regedt32.exe and select "Import Registry
42 File" from the "Registry" Menu).
44 The other major ramification of this feature of NT is that it can't
45 browse a user level non-encrypted server unless it already has a
46 connection open. This is because there is no spot for a password
47 prompt in the browser window. It works fine if you already have a
48 drive mounted (for example, one auto mounted on startup).
49 =====================================================================
53 When you mount a printer using the print manager in NT you may find
54 the following info from Matthew Harrell <harrell@leech.nrl.navy.mil>
58 I noticed in your change-log you noted that some people were
59 still unable to use print manager under NT. If this is the same problem
60 that I encountered, it's caused by the length of time it takes NT to
61 determine if the printer is ready.
63 The problem occurs when you double-click on a printer to connect it to
64 the NT machine. Because it's unable to determine if the printer is ready
65 in the short span of time it has, it assumes it isn't and gives some
66 strange error about not having enough resources (I forget what the error
67 is). A solution to this that seems to work fine for us is to click
68 once on the printer, look at the bottom of the window and wait until
69 it says it's ready, then clilck on "OK".
71 By the way, this problem probably occurs in our group because the
72 Samba server doesn't actually have the printers - it queues them to
73 remote printers either on other machines or using their own network
74 cards. Because of this "middle layer", it takes an extra amount of
75 time for the NT machine to get verification that the printer queue
78 I hope this helped in some way...
80 =====================================================================
84 From: Frank Varnavas <varnavas@ny.ubs.com>
85 Subject: RE: Samba as a print server
87 When an NT client attempts to connect to a printer on a non-NT print
88 server the attempt is failed with an error, something like:
90 "You have insufficient access to your computer to perform the
91 operation because a driver needs to be installed"
93 This is because domain users must have 'Power User' status on the
94 desktop to connect to printers on a non-NT print server.
96 This error occurs regardless of whether the driver in question is
97 already installed or not. What it really means is that the server is
98 a non-NT server and the client does not have permission to create
99 printers locally. Apparently when a connection to a non-NT print
100 server is made the printer is defined locally. Such an action can be
101 performed by either a local administrator or a Power User.
102 Unfortunately there is no way to limit the powers of a Power User, nor
103 is there any way to grant the Printer Creation right to another group.
105 This permission policy is documented in PSS database WINNT, ID Q101874
107 Frank Varnavas (varnavas@ny.ubs.com)