Client Access - Signon screen

[J.Wells]

I seem to recall that to be able to use case sensitive passwords, you have to change the QPWDLVL system value so that 128 character passwords are allowed......... HTH, Joe

[lls_51@yahoo.com]

Client Access - Signon screen

Checked system value QPWDLVL - set to 2 (User profile passwords with a length of 1-128 characters are supported). lls

[Guest.Visitor]

Client Access - Signon screen

lswain wrote: > System at V5R2. Users access AS/400 via Client Access. > When user profile has expired - user changes password. > Security policies require 1 Upper case, 1 lower case, 1 numeric and 1 > special character. Exit program validates entered password. > Seems that Client Access interprets whatever entered as upper case. What version of Client Access? The help text for Password Values for iSeries Access V5R2 says that it will not translate mixed case with a system value of either 2 or 3. If you are running iSA V5R2 and are at the latest Service Pack level, then you need to contact Software Support and report a bug. Bill

[J.VanHuklon]

Client Access - Signon screen

One other thing to be aware of is that the mixed case 128-character passwords can only be used on Windows NT, 2000, XP or 2003. They cannot be used on Windows 95, 98 or Me. If you are having a problem with this on NT, 2000, XP or 2003, and the QPWDLVL is set to 2 or 3, I agree that contacting Software Support is appropriate.

[lls_51@yahoo.com]

Client Access - Signon screen

System at V5R2. Users access AS/400 via Client Access. When user profile has expired - user changes password. Security policies require 1 Upper case, 1 lower case, 1 numeric and 1 special character. Exit program validates entered password. Seems that Client Access interprets whatever entered as upper case. Is there a way to configure Client Access to accept upper and lower case in password field? Thanks Larry Swain lls_51@yahoo.com

[kkh@nwnatural.com]

Client Access - Signon screen

Here is how to allow mixed case passwords and not move to 128 pass phrases. This is from IBM and it works for us. LANMAN Style Password Hash Info V5R1 - MF30226 V5R2 - MF30229 In V5R1 we changed to prefer the Windows NT style password hash if it is present in requests. If a user on a Windows NT/2000/XP machine tries to connect to NetServer using a mixed case password , the connection is denied. With the PTF applied and the hidden share created Netserver will fall back to using the older LANMAN password has as it did in pre-V4R5 and will not be case sensitive. Once the PTF is applied to the system, the administrator needs to add a share named QZLSPWDANY$. Netserver will then need to be restarted. If the share is present, the NetServer authentication code will try to use any provided password hash to authenticate the client. If a mixed case password is provided from a Windows NT/2000/XP client, the NT style hash will fail, but the LANMAN hash will succeed, and the client will be granted access.