I have found that windows is semi-stupid in drive mappings to non-windows systems. I do not know this for sure but it appears that windows will try and try and try the password the user used to logon to the PC when attempting to doing the drive mapping which a lot of times disables the iSeries account. I don't know it does not just try once and then ask for a different password if it does not work. The only way I have found to not have problems is to be sure the Windows password and iSeries password are identical. The username does not appear to be as much of an issue as windows will remember the username used to setup the mapping. My windows username and iSeries username are not the same but the passwords are and I never have an issue with drive mappings. Others in my office who keep their passwords different (they don't trust active directory to keep password secure) have problems all the time. We do have our iSeries setup to accept long passwords
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Friday, June 01, 2012 11:45 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: Drive Mapping Headache
One problem we have here is MixEd case passwords. Our iSeries have not been updated to handle mixed case passwords. Yes the use types the password on the "Green Screen" as mixed case, but we all know that it is an upper case only field. ;)
But the Network does support MixEd case so the passwords really do not match. Second problem is "1password". Which on the iSeries becomes Q1PASSWORD. Type from a green screen and the Q is automatically inserted. From other methods, no Q. Make sure the password does not start with a number.
But then again, depending on how you have your system value set for password level, this may all be mute.
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of daparnin@xxxxxxxxxxxxxx
Sent: Friday, June 01, 2012 8:20 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Drive Mapping Headache
I've got a user who took over a job and is having issues with mapping a drive to the IFS. It worked fine for the person who used to do the job.
The mapping is done in a batch file (see below). It looks like it doesn't recognize her user name or password, although it works fine on a green screen. I've given her access to the folder via WRKLNK (see below). I checked the permissions with System/i Navigator. Public has read, write, execute, management, existence, alter, and reference authority. I gave the same to her user-id. I copied her user-id to a test name and it works fine with it. I'm running out of ideas.
R:\acct\acctng\ACH>net use w: \\AS30\Root\ACH The password is invalid for \\AS30\ROOT\ACH.
Enter the user name for 'AS30': slballar Enter the password for AS30:
Enter the user name for 'AS30': slballar Enter the password for AS30:
System error 1326 has occurred.
Logon failure: unknown user name or bad password.
R:\acct\acctng\ACH>pause
Press any key to continue . . .
Data --Object Authorities--
Opt User Authority Exist Mgt Alter Ref
SLBALLAR *RWX X X X X
--
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.
midrange.com
