× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.


On 7/27/2011 8:25 AM, Jeff Crosby wrote:
All,

Can someone confirm or tell me if you've run into this. A user changed her
System i and Windows passwords. They match, but start with a digit. She
can sign on to both Windows and the System i with this password.

*BUT* there is a job she runs once a day that copies 3 PDFs from the IFS to
a windows share via the QNTC route. It's worked fine for many months until
2 days ago when she changed her password to START with a digit. The W2008
Security event viewer says it's the wrong password. Could it be that
Netserver (or whatever it is on the System i that supplies the password)
cannot handle a password starting with a digit?

Thanks.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.