Mapping an I-Series drive via windows logon script

45 pts.
Tags:
AS/400
Client Access Express
Logon script
Network Drive Mapping
Windows XP
We are having a weird issue here regarding mapping a drive when the user logs on. Without client access express loaded, the drive maps correctly. WITH Client Access Express we get an invalid user profile. This ONLY happens when the PC is initially powered on. If the user logs off then logs back on the problem goes away. Has anyone seen this before? We are on OS/400 6.1 and running on Windows XP. This is driving us nuts! Any help would be appreciated.

Paul



Software/Hardware used:
ISeries OS/400 6.1, Windows XP, Client access Express
ASKED: August 1, 2011  3:03 PM
UPDATED: March 31, 2012  7:26 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Go into Operations Navigatpr or whatever it is called and look at the properties of the connection to see what profile it is using, Client access usually defaults to use credentials same as Ops nav..
If it using Windows credentials and your Userid and Passwords match you should have no problem.

Remember when mapping to a Iseries unless you change the mapping to use a different user it always uses the Windows credentials.

Discuss This Question: 13  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Just to clarify, are you really using the Client Access Express product? That's pretty old. I'm kind of surprised that it would work on XP with i 6.1. If it's really Client Access Express, is there a reason you haven't kept up with the product line? And if it's not, then what is the actual product version and release? Tom
    125,585 pointsBadges:
    report
  • tatespa
    We are running that product because its required to use with our Medical Sysytem Software (Siemens). The current version is 6.1 and has been working fine. This issue is during the logon script. I don't know if CS is actually involved, ut it must be because without it, the mapping works just fine. It appears that somehow the registry is getting corrupted somewhere but we cannot find it. When we uninstalled and re-installed CS the problem still exists. Paul
    45 pointsBadges:
    report
  • TomLiotta
    I can no longer recall how CA Express handled mapped drives. Back early on in that product line, drive mapping to AS/400s was handled by that product itself. I don't know if CA Express was a version just before or just after the drive mapping function was taken out of that product and handled totally by Windows. Nowadays (and for a number of years before this), drive mapping has no connection to the "Client Access" product -- it's all just plain Windows Network Neighborhood drive mapping. If CA Express performs any internal drive mapping, it could conceivably interfere with what Windows is doing. That is, CA might do something like loading a .DLL (or modifying a registry entry) that conflicts with current Windows networking. At i5/OS V5R4, IBM was also changing how the *FILE server interacted with requests from remote clients. I don't have useful details related to your situation, but an example change involved a new multi-threaded server that would handle Windows networking that was changing starting with Windows XP. As Windows changes its technology, systems that interact with Windows must also change. We are running that product because its required to use with our Medical Sysytem Software (Siemens). There is some sense in that. That is, I can see how it would have been needed back when "shared folders" (for example) were served via Client Access. But there should no longer be any pieces from "Client Access" that are used. The medical software might call the older CA APIs and hasn't been updated for new API names, etc., even for parts that don't relate to mapped drives, e.g., the data queue server or the database server. It's quite possible that the software vendor would be the only one who could fix it. I don't expect that any of this helps. It might get someone else here thinking about it, though, and other ideas might come up. Tom
    125,585 pointsBadges:
    report
  • Yorkshireman
    Have you checked alternatives? such as using a current version of client access, and as Tom syas - just let Windoze do its thing. Take a spare PC, install a recent CA, and do some testing. Unless Siemens use some explicit function, I'd expect it to work. If not, I'd be making their support lines hot. If their product is no longer maintained./ marketed, then perhaps you need to stay on 5r4 until you find a current product
    5,520 pointsBadges:
    report
  • tatespa
    We have tried everything to fix this. It does appear that CA is not involved with the mapping at all. It seems somehow that there is an invalid userid being used for the drive mapping. We did take another machine and load up CA 5.4 and tried it without any issues, we upgraded to 6.1 with no problems either, we also tried the same thing with NO CA loaded and that worked as well... somewhere there is something screwing this up and we can't find it. EVEN when we uninstall the CA software from the offending machine, it still errors out. I was hoping that someone out here had run into this issue and had a resolution for it. I guess that this is isolated to these machines and the best remedy would be to clean them, rebuild them and/or give these users a new machine.. Such a pain to go through all that for just this issue. We do need the CA primarily because of the Siemens product.. can't use any other 5250 emulation.
    45 pointsBadges:
    report
  • Splat
    Tatespa, we're running Siemens MS4 on a V6R1 machine & I've not run into any particular requirements for Client Access Express. Our default 5250 emulator is iSeries Access for Windows, but we've successfully used Tn5250 for stripped down access.
    6,255 pointsBadges:
    report
  • tatespa
    So, I think I am back to some sort of corruption going on. I think somewhere a userid has been put in or changed that does not have corresponding access to the I-Series. Seems the only solution that we have found is to put a new PC out there...
    45 pointsBadges:
    report
  • TomLiotta
    Given responses from others who apparently use the same (or very similar) product, I agree that some configuration item is incorrect. (Maybe corrupted, but that can be considered "incorrect".) A reasonably sharp PC/Windows person should be able to track it down and set it right. Otherwise, save stuff off of the PC that needs to be saved. Then set it up fresh again. Or, of course, replace it. Tom
    125,585 pointsBadges:
    report
  • Rickmcd
    Also you can go into Windows Explorer tools map network drive wizard and pick drive letter put in the share click on different user put Iseries credentials no domain Also click on map at restart Thren when password for Iseries changes do over
    1,560 pointsBadges:
    report
  • tatespa
    @Rickmcd, that would have been a great idea, but the mapping fails so it never really happens. I need to see what user it's trying to use when it attempts to map. All I get is the password is invalid, then the prompt is for userid...
    45 pointsBadges:
    report
  • WoodEngineer
    We run a similar configuration at our company. About 50 users have drives mapped to the IFS. We typically install a subset of iSeries Navigator to handle the mapping task. In a few cases we use a PC script to map the drive. Could it be that some of your users are employing both methods to map a drive? If so, they might conflict.
    6,045 pointsBadges:
    report
  • Rickmcd
    Tatespa - When you get that window for User ID it is saying your windows credentials and Iseries Credentials are not matching. I don't know what script is running but for a quick fix, disregard the script go into Map network drive and Use the different user and use a User Profile that you know has the necessary authority,if you also use the reconnect at Logon the script would not be necessary. Also before you map use the disconnect option under tools to disconnect that drive letter.
    1,560 pointsBadges:
    report
  • graybeard52
    If you upgraded to v6.1, you are using System i Access for Windows, not "Client Access". Nevertheless, you should be able to map. Check the NetServer service in Navigator and see if you have any "disabled ID's". An ID can be disabled for Netserver and not the normal profile logon. Also, as suggested, check Navigator to see what the logon default is. (Use windows passord, prompt, etc). The most common reason is that the Winodws password does not match the System i password.
    3,115 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following