ZeroConfig should work and for a fallback you can enter the afp url directly, the format is
afp://[[user[:[email protected]]]server[/share[/path[/file]]]] .
Needless to say, there might be issues and that's what this thread is all about. We want GOOD feedback regarding the new AFPClient. If you have issues and do not include xbmc.log and detailed info about your setup... you will get ignored
1) The first connect might fail (spinning wheel is spinning for more then 30 secs). In that case abort the connect by pressing "Menu" on the remote and try again. It works after a couple of trys. If its connected once - everything else should work.
2) On a Mac, you need to enable AFP sharing in System Preferences > File Sharing > Options.
3) AFP paths are case sensitive. If you're editing sources.xml directly (not browsing for the path) make sure to pay attention to case. SMB paths are not case sensitive. E.g. afp://192.168.1.7/MyVideos/ and afp://192.168.1.7/MYVIDEOS/ are two different paths under AFP.
4. AFP is generally stable but may crash in a few situations. Unfortunately the upstream developer of the AFP library is no longer around so it's orphaned for now, i.e. no one to do bug fixes... for now. If it crashes for you, probably best to try WebDAV or FTP.
Just wanted to point to this:
When using MacOSX and trying to share via AFP only HFS+ formatted drives are shared. There is no warning / nor an error message - it simply doesn't show up that shares then. This is the issue some users already have seen when trying to share FAT32 drives on lion via AFP.