Windows 7 mapped drives with Client Access

50 pts.
Tags:
AS/400
Client Access
Client Access 5.4
Client Access 5.x
IBM iSeries
Microsoft Windows 7
Network connectivity
Using client access 5.4 with iseries os 5.1. Most parts of client access is working ok but cannot create a mapped drive. Is this there some setting tha i have missed?

Answer Wiki

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

In iNav expand the system whose files you wish to share, click on File Systems, Integrated File System then click on File Shares folder. This will expose the folders that can be mapped to network drives.

Discuss This Question: 4  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
    If this is indeed iseries os 5.1 and Windows 7, be aware that Microsoft began using some changed protocols for Windows networking in Windows XP. IBM began changing the *FILE server (and therefore NetServer) in i5/OS V5R4 to allow the newer MS protocols to work effectively. Discussion is generally seen in the NetServer What's new for V5R4 topic, as well as Troubleshooting iSeries NetServer (V5R4) topic under Troubleshooting user profile connections and Troubleshooting file share problems, as well as related troubleshooting topics for V5R4. I don't have specific info for Windows 7. It might be necessary to determine what the connection protocols are and to see if it's possible to use older behavior in Windows 7. That's all just secondary info and may have nothing to do with whatever the actual problem is. Still, I would try the same connection with a Windows 2000 PC (or possibly basic Linux and Samba) to ensure that general configuration is still proper for V5R1 before digging into what Windows 7 might be doing. Tom
    125,585 pointsBadges:
    report
  • Pjb0222
    If your backend requires NTLM authentication, you will need to enable it on WIndows 7. You can go into GPO Edit and enable NTLM. By default Windows 7 (and Vista) only enable NTLM v2. MS Technet on NTLM in Windows 7 and Server 2008 detailing how to enable NTLM. Another item to check is when and how the drives are mapped. If the user ID has local administrative access and you are using a login script, then there is a Registry modification you need to make on the Windows 7 (and Vista) systems. Setting to allow drive mappings between admin and non-admin sessions
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem
    EnableLinkedConnections =(dword)1
    3,310 pointsBadges:
    report
  • WoodEngineer
    According to IBM, Client Access 6.1 is required for Windows 7. We are experimenting with that environmant now. So far, so good.
    6,875 pointsBadges:
    report
  • Stark99
    I have the 64bit version of Windows 7 home premium. The install cd I have for client access 6.1 would not run because of compatibility problems. I can map a drive to any PC on our network just not the Iseries. Thanks
    50 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