Some client/server combinations have difficulty with mixed-case passwords. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems. These clients upper case clear text passwords even when NT LM 0.12 selected by the protocol negotiation request/response. This parameter defines the maximum number of characters that may be upper case in passwords. For example, say the password given was "FRED". If password level is set to 1, the following combinations would be tried if "FRED" failed: "Fred", "fred", "fRed", "frEd","freD" If password level was set to 2, the following combinations would also be tried: "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", .. And so on. The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection. A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case. Default: password level = 0 Example: password level = 4