Not able to access AS/400 share from the Windows PC

665 pts.
Tags:
AS/400
AS/400 administration
IBM i 7.1
Microsoft Windows
Hi Team,
We are not able to access the AS/400 share using the window's PC. While we try to connect, we are getting an error" Extended error occurred". The user ID is not disabled and the password is correct. We tried with "Connect using different credentials", yet we are getting the same error. Kindly advise.


Software/Hardware used:
V7R1

Answer Wiki

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

Have you tried accessing the link through iSeries Navigator? 

It might be issue with incorrect credentials as per IBM (Click Here). But, could be problem with Authority. Try accessing any other Share and see if it gives same error.

Discuss This Question: 27  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.
  • Subhendu Sen
    Is there one or more Windows PC? If other windows systems can access this share, through windows explorer and the same actions do not work on this particular PC, then it might be cause of route/something like permission of user. Check all of these possibilities.
    93,600 pointsBadges:
    report
  • ToddN2000
    Another possibility is to check the max signons for that user. If they are logged in elsewhere it may not allow a second login under the same profile.
    89,455 pointsBadges:
    report
  • Splat
    Do you see the CPIB682 message (User profile [user profile name] disabled for IBM i Support for Windows Network Neighborhood access.) showing up in your QSYSOPR message queue?
    11,455 pointsBadges:
    report
  • ToddN2000
    Please post any errors you may see on the AS/400 side for that user. It may help us resolve the issue faster.
    89,455 pointsBadges:
    report
  • Gayathri123
    Hi Team,

    We checked the maximum sign-on and tried accessing using different user profile from different PC, yet we are getting the same error. Port 445 is in listening state and we are not getting any error in AS/400 message queue. We are able to ping the AS/400 IP from the windows PC and the shared directory has RWX authority for *public. 
    665 pointsBadges:
    report
  • Gayathri123
    Also we have created a shared directory and tried to access the new share, but we are getting the same " Extended error". We were able to map it before. We have this issue since 20 days. Please advise.
    665 pointsBadges:
    report
  • Splat
    Would you happen to have the error message ID? That may help track down the issue.
    11,455 pointsBadges:
    report
  • ToddN2000
    Can the profile make any valid connection to the AS/400, if do then I would check the security on the share. The flip side is can anyone connect to the share or are all profiles giving the error? This will help narrow down if it's a profile of the shared object that has the issue.
    89,455 pointsBadges:
    report
  • bhannah
    I read through the comments and suggestions, and I did not see anything that the people had checked to make sure that the permissions were granted correctly on the AS/400 side. Not the windows side. There can be more than one place that controls permissions to a shared folder on the AS/400. This is especially critical if you are running Websphere too.
    3,745 pointsBadges:
    report
  • Gayathri123
    @ToddN2000: All the profiles have challenge in connecting to the shared drive.
    665 pointsBadges:
    report
  • Gayathri123
    @Splat: We are not getting the CPIB682 message and we checked for the disabled user IDS for IBM i netserver in system i navigator. We do not have any disabled user ID for IBM i netserver. We checked the qsysopr message queue and there are no errors related to IBM i netserver.
    665 pointsBadges:
    report
  • pdraebel
    Have you ran CWBPING from PC? It lists all Client Access Services. Is QDLS still in use? And shared? Did you manage to use any share?
    7,545 pointsBadges:
    report
  • ToddN2000
    Are you sure the server is up and running? When we first started we would have an issue where operations would forget to start the QHTTPSVR subsystem. Nobody could connect.
    89,455 pointsBadges:
    report
  • kitvb1
    You do not say which version of Windows you are using.
    Microsoft is switching over to SMB2 (I believe it's called) and I thought this is/was scheduled for 01 Jan 2018. This could/might disable your shares and I say could because our network guys could not understand from the document if it did or did not include PC shares.
    SMB2 is not compatible with IBM i v7.1. Compatible with v7.2 with PTFs and fully with v7.3.
    Our Network guys seem quite relaxed about it as they say they can bypass it easily via the registry anyway to use SMB1.
    Kit
    50 pointsBadges:
    report
  • Gayathri123
    @ToddN2000: IBM i netserver is up and running and QSERVER subsystem is up.
    @kitvb1: We are using windows 7 Enterprise.
    665 pointsBadges:
    report
  • pdraebel
    Gayathri123, so no Drive can be mapped to the iSeries at all? This since 20 days. Where any system changes made on iSeries prior to this? System change or User setup Change.
    7,545 pointsBadges:
    report
  • Gayathri123
    @pdraebel, yes. We are not able to map any of the drives and we have four iSeries LPAR and we are not able to connect anyone of them. Is there a possibility that it could be an issue from window's side?
    665 pointsBadges:
    report
  • pdraebel
    I've never come across such an error. Check your versions of Client Access and check your PTF level of the iSeries. Another thing to check is with your network colleagues: Is the NETSERVER traffic being blocked?
    7,545 pointsBadges:
    report
  • ToddN2000
    Have any windows updates or PTF's been applied recently? IF so which ones. I have seen updates do more harm than good and the have to be rolled back to get things working again.
    89,455 pointsBadges:
    report
  • Splat
    If you've not made any changes to any of the iSeries in the past 20 odd days you might want to check with your network folk to see if there's been a change in your network configuration and/or firewalls.
    11,455 pointsBadges:
    report
  • WoodEngineer
    Could it be an authority issue on the iSeries folder being mapped? Check the permissions on the folder.
    7,650 pointsBadges:
    report
  • Gayathri123
    @ToddN2000 & @Splat: We did not do any PTF update on the AS/400 side. We are checking with windows team.

    @WoodEngineer: We checked the permissions and we don't have authority issues in our iSeries folder.
    665 pointsBadges:
    report
  • ToddN2000
    How are you trying to connect to the share? Directly, command, network drive,  via an app or program? If you are using an app or program post the code so we can get a better understanding.
    89,455 pointsBadges:
    report
  • Gayathri123
    @ToddN2000: We connect to the share directly through network drive.
    665 pointsBadges:
    report
  • hbpraveen

    Hi There,

    There are basically 2 reasons for this.

    Reason 1: The password used by the user should be same on windows machine and the iseries.

    Reason 2: The password in windows can be case sensitive. However, in iseries, the user needs to use the same password used in windows without case sensitive.

    Reason 3: Both the Windows password and iseries password should be same.

    Reason 4: please check on what windows OS platform the user is accessing the iseries shared folder. If the user is using Windows 10, it will not work. the windows machines has to be updated with the windows patch. Please check in IBM website for the same.

    Regards,

    Praveen.

    10 pointsBadges:
    report
  • Gayathri123
    @hbpraveen: We are using windows 7.
    665 pointsBadges:
    report
  • Splat
    I found this. It's a bit dated but might be of some use.
    11,455 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.

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

Following

Share this item with your network: