NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Starlionblue's avatar
Starlionblue
Aspirant
Sep 14, 2010

AFP "connection failed"

Hiya,

Did a customer install a few months ago with:
- ReadyNAS Duo.
- Seagate FreeAgent backup drive.
- Buffalo WZR-HP-G300N routers.
- iMac
- Thinkpad

Duo has both CIFS and AFP on. The iMac was just fine connecting via AFP. I also used the Time Machine function to backup the iMac.

Customer called a few days ago saying Time Machine was throwing errors so I went to check it out. I saw that AFP in Finder displayed "connection failed". Attempts to connect with finder or command-k got me "incorrect username and password". I changed the password to "1234" just in case I was mistyping but no joy. CIFS access worked fine. As a workaround I switched customer to CIFS.

Since Time Machine uses AFP, that functionality was broken.

Updated Duo to latest firmware and ran system update on iMac. No difference. Tried deactivating TM and AFP on ReadyNAS, rebooting it, reactivating. Did the same in various combinations. No joy.

I have read of other users having similar issues at various times.

Any help is appreciated. Have sent logs to the specified address attn. Captain Solo.


Sidebar: Made aliases for the "CIFS shares" on the iMac desktop. At startup I get a garbled terminal-like window, one titled with the name of each alias. Does not affect functionality. Why is that?

18 Replies

Replies have been turned off for this discussion
  • Starlionblue wrote:
    it would seem unlikely this link just disappeared. Or?

    I would tend to agree. But given the symptoms are very much the same.

    I leave to you , but here's the issue if you do take a look:

    In a standard configuration, all of the shares are mounted as "/c/<share>", so the physical location of a share called "public" would be "/c/public". For reasons I don't know and unlike CIFS, the AFP service is configured to access shares at the root as "/<share>". To make this all work, Frontview creates symbolic links in the root to the actual share in /c

    Again by way of example, for a share called "public", if you were to list the root directory on the NAS ("ls -al /") you would see something like:

    lrwxrwxrwx   1 root  root      9 2010-07-24 13:39 public -> /c/public

    If that link is not there, AFP cannot find the physical share and fails with a "connection failed" error. But everything regarding the setup of the share will otherwise seem correct. The fix is to recreate the link with a command such as :
    ln -s /c/public /public
  • Thx for info. I'll try if and when I get out there.

    One thing though. I get the "connection failed" message even before trying to access the share. Finder has a "Vault (AFP)" listing (NAS is named "Vault") on the left. If I click on that I get "connection failed" and no listed shares. So it's like it sees the NAS but can't connect to even list the shares.

    In Time Machine setup, when I try to select a drive, it lists the ReadyNAS but when I try to connect it throws the username and password error.


    Thx for the help btw. Much appreciated. :D
  • OK - My mistake as I was under the impression the shares showed, but you only got the error when trying to connect to a share. In which case, my previous "guess" will be completely wrong as the symptoms are different.

    The sidebar entry is a result of the AFP servcie being advertised over bonjour - but bonjour and AFP are actually completely separate. So there are numerous reports of sidebar showing the AFP service, but not working. Bonjour uses network broadcasts, and because of that sidebasr items will appear even if mac and Duo have incompatible IP addresses, or if the AFP service is blocked. So the usual cause is IP addressing being "wrong" (eg an address name resolution problem), or the AFP service being blocked (it runs on port 548). This is also much more consistent with the TM issue - the AFP service is "seen" by TM due to bonjour, but you can't connect to it.

    Have you tried to connect over AFP with the IP address rather than name? (eg cmd-k -> afp://192.168.0.xxx) Any way the customer could have installed some kind of firewall or other such program? How do you connect the iMac over cifs?
  • sphardy wrote:
    The sidebar entry is a result of the AFP servcie being advertised over bonjour - but bonjour and AFP are actually completely separate. So there are numerous reports of sidebar showing the AFP service, but not working. Bonjour uses network broadcasts, and because of that sidebasr items will appear even if mac and Duo have incompatible IP addresses, or if the AFP service is blocked. So the usual cause is IP addressing being "wrong" (eg an address name resolution problem), or the AFP service being blocked (it runs on port 548). This is also much more consistent with the TM issue - the AFP service is "seen" by TM due to bonjour, but you can't connect to it.


    Also, there's Bonjour Browser with which you can investigate the Zeroconf registrations easily using a GUI.
  • Same issue here can't connect to any AFP share but CIFS works

    Use raidiator 4.1.8 and OS X lion
    I have SSH access to it.

    Anyone ?
  • I reinstall the readyNAS firmware(via reset switch) and now AFP works agian :D
  • sphardy's last suggestion to use the IP address worked for me...I'm not familiar enough to figure out where the problem is but at least it works, thanks!
    I might also reinstall the firmware. Useful threads thanks!
  • Tip on Entering correct information to ensure TM can find your NAS

    Just been trying to reconfigure my set up.

    I have had a Duo V1 working quite happily backing up via TM however I decided to carry out a bit of housekeeping following the failure of an Ext HDD I was using with my Macbook.

    Although you can change your user name and password to anything you like. To login and successfully select your NAS drive, the name used for TM to find your NAS is fixed and you should always enter 'ReadyNAS' and then you should enter the password you used when setting up TM via Raidiator. Otherwise TM will not find your NAS and will give you the OSStatus 2.0 error message.

    This seems illogical when you can change your username and password but there it is.

    Seems so obvious when the username on the TM setup screen in Raidiator is greyed out so it is always 'ReadyNAS' but this can easily trip you up as it did me for hours.