Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
We are running V5R4 and I have a user that disables in NetServer all the time. Even after I reset the user status, profile disables in NetServer. I thought that the mapped drive might be the problem but we've removed the mapping. Is there a password cache somewhere that is causing this and what would I clear on this one user. Others don't seem to have this problem. I do see that NetServer is configured with no guest user and an authentication method of encrypted passwords.
We've now even tried going to another PC and logging there. User still not able to log in.
Don't know anything about NetServer but can't you see on the profile how many times it tried to log in before it was disabled?
Other than mapping, does anything else run at Windows startup, such as the PTF check for iSeries Access? If so, is Windows user id the same as i user profile name, and if so, are the passwords synchronized?
Other thing I've seen is some Windows connections/apps have built-in retries. A single typo can kill it after what appears to be only one attempt, where in reality it's the retries behind the scenes that are the culprit.
You might try authenticating (actually, mapping) from the command line (Start, Run, cmd.exe). Do
net use \\iserver /user:xyz
net use \\iserver password /user:xyz
The first version will prompt you for the password, which is not displayed as you type. You can also use \\ipaddress. It's important that you authenticate to the server first, then drill down into the shares. If you try to authenticate to a share first, as in \\iserver\share1, it will fail (at least, that's been my experience).
btw, are you aware that you can reset a disabled NetServer password by CHGUSRPRF XYZ with no other parameters? You don't actually have to change anything; just CHGUSRPRF by itself. Also works with CHGPRF, which users can run themselves (if they have command line access), again with no parameters.
Looks like a Windows 7 vs. NetServer issue at this point. This is the only machine that is on Windows 7 so far.