Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1013
  • Last Modified:

Mapping OSX to Netware 6.5 - An afp system error has occurred

When I try to connect to my Netware 6.5 server I get the following error. an afp system error has occurred

I Click on Go > connect to server.
Then I type in afp://XXX.XXX.X.XX
It asks me for a username and password
Then I get the error

I had this working fine before but the user account that I had it associated with had its password changed on the netware server. Now I have changed it back to what it was and I can't seem to connect anymore.
0
amerretz
Asked:
amerretz
  • 8
  • 7
1 Solution
 
lesouefCommented:
case problem?
also try to put user:passwd in url like:
afp://user:passwd@server.domain/volume/
0
 
amerretzAuthor Commented:
Same error appears.
0
 
lesouefCommented:
pb on /Volumes rights? can you mount another volume on same server? on another server?
permissions on the remote volume (osX writes hidden files for icons, etc...)?
maybe you should try to mount this volume manually using the mount command in a terminal session, you would get a more accurate error; that required some unix habits you may not have, so, open a terminal session and:
> mkdir /Volumes/localname
> chmod 777 /Volumes/localname
> mount_afp afp://[username:password]@remoteserver/volume /Volumes/localname
that should bring the remote volume on desktop or issue a better error hopefully
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
amerretzAuthor Commented:
OK I typed all that in the terminal. kI get the following message:

mount_afp: the mount flags are 0000 the altflags are 0020
mount_afp: AFPMountURL returned error 1, errno is 2



...I have no clue what this means..
0
 
lesouefCommented:
so do I... man does not document errors numbers...
a few other questions to narrow the pb down:
- does it work with another account?
- does it work with the same account from another mac (if any)?
0
 
amerretzAuthor Commented:
No it does not work with another account.
I had this working before, Like I said above I changed the password for this user account, then I lost the map. Now I have changed the password on the netware server to what is was when it was working. Now I cannot map to any account on my netware box.

0
 
lesouefCommented:
so the passwd change is just a coincidence then, since other accounts do the same.
do you have another client machine? pc or mac?
can you check on netware side if you did not change something else wihout noticing it?
0
 
amerretzAuthor Commented:
yeah I have plenty ok windows boxes which have many mapped drives working currently. Its just always a problem on the mac.

0
 
lesouefCommented:
does that also mean that the same account (the guiltty one on mac) works if it's used to mount the volume from a pc?
if yes, then you are left with a lower/upper case or in anycase a syntax pb.
If the error the same if you put the volume name directly in the URL you want to connect to? ie afp://XXX.XXX.X.XX/volume.
Also, there is something a bit different in between pc and macs, pcs won't use afp but smb, so if something is wonrg with the afp daemon in netware, pcs won't see it. Can you try a smb shared volume from the mac as another test?
0
 
amerretzAuthor Commented:
What is the syntax to map a path using SMB on the mac?
0
 
amerretzAuthor Commented:
smb works fine....is this ok to continue using ?
0
 
lesouefCommented:
so I guess you found the syntax... easy, juyst replace afp by smb.
ok to go on? yes, but don't forget that naming conventions must conform to windows rules, files generated by PC may not be recognized by osX due to unknown extensions, and yr windows will see a few .* files (hidden for osX) generated by osX for folder parameters.
if a given account is ok with smb and not with afp, I am afraid your afp server is going nuts, you should reboot it or at least restart the afp daemon/service (I ignore the proper name as I am netware ignorant).
0
 
lesouefCommented:
so, what was the right fix?
0
 
amerretzAuthor Commented:
using SMB... I will try what you said in the last message later...
0
 
lesouefCommented:
if you just have 1 mac user, restarting only the afp daemon should not do any harm to other users...
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now