afp connection rejected: (bad user/pass) afp log: "too many"

thom wrote:
I just solved my own problem, but not without a lot of frustration and head-banging. ... Maybe this post will help someone else out there who runs into the same problem.

@thom: Thank you very much: your post really helped me! I've been frustrated by the same problem for a while, and now it's solved.

That's really cool of you to take the time and post the solution.

@merlino73: I found that the following worked:

1. Use Frontview to stop AFP

2. ssh into your ReadyNAS

3. confirm that /etc/default/netatalk is empty - if not and you're having this same problem, you should definitely make a backup of the existing file before making any changes.

4. if /etc/default/netatalk is empty;

5. vi /etc/default/netatalk and paste in the text in the "Code" section below:



# Set defaults. Please change these options in /etc/default/netatalk.
AFPD_UAMLIST="-U uams_dhx.so,uams_clrtxt.so,uams_randnum.so"
AFPD_GUEST=nobody
AFPD_MAX_CLIENTS=50
ATALK_ZONE=
ATALK_NAME=`/bin/hostname --short`
ATALK_BGROUND=no



6. Use Frontview to start AFP - you should see your shares appear and they should be accessible.

Now, I doubt this is "officially supported", but it worked for me. Of course, you should know what you're doing if you're ssh'ing into your NAS.

I tested by shutting down AFP, creating an empty /etc/default/netatalk, starting AFP, and was back to the problem state. Following the procedure above restored AFP access to my ReadyNAS.

Thanks again, thom!!