|
We've noticed a different problem in our shop that maybe someone can shed some light on. Sometimes we'll have users who create passwords that are a mix of upper- and lower-case letters. These passwords work fine to log on to both the i and our windows
network, but if someone tries to map a drive to the IFS (or tries to access a drive that is mapped to to the IFS), they get a password mismatch error.
Our solution so far has been to tell people to use only upper- or lower-case for passwords, but sometimes it's a little embarrassing when the user has just read an article on password security and is following the common recommendation to used mixed
case. They give us funny looks when we tell them our systems can't handle it. ;-)
I've checked the passworld level settings, but they don't seem to apply. Is there something I'm missing, or is there a way around this? If not, any guesses as to whether it might be fixed in the future?
TIA,
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:
I know you've already received a bunch of messages about this, and that
I'm late to the game, but...
When you create a password that starts with a digit, the IBM i operating
system automatically inserts a Q in front of it. So if your password is
1234, the system stores it as Q1234. (I don't know why.)
When the password is Q1234, the system would accept a signon where the
user typed 1234 _or_ Q1234.
The problem in your case is you're going the other direction. You want
the system to _send_ the password out to a Windows share. When you do
that, should it send 1234? or Q1234? How would it know which one to
send? The answer is: it doesn't. So it probably sends Q1234, and
that's the bad password.
Solution: Use a password that starts with a letter.
Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
