NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
netracer
Nov 12, 2010Apprentice
AFP Not Working
So I've been beating my head against the wall trying to solve a problem with both a Macbook and Macbook Pro not being able to see the AFP share on my ReadyNAS Pro on my home network. I'm a Mac newbie, so please forgive me if I don't know some obvious things.
Here's the breakdown of my diagnostics
Macbook Pro is running 10.6.5 as of 11/10/2010 and the Macbook is running 10.6.3
BOTH Macbooks CAN see an AFP share for a ReadyNAS NV+ that I have in my office.
ReadyNAS Pro is running 4.2.15
ReadyNAS NV+ is running the latest version (the number escapes me)
On my home network the Macbooks CAN see each others AFP shares when i turn on sharing
There is no WINS server on the network
Now pay attention....
If I do an Option-K and explicitly type afp://nas-ipaddress it connects but it shows up as connected as a PC Server (so its dropping to smb anyway)
If I turn off CIFS on the readynas and explicity type afp://ip-address it connects via afp and shows up as a Mac Server (so now it can connect using AFP).
Under no circumstances does typing afp://nas-name work. It fails immediately.
However from windows boxes (when cifs is on of course), doing a start run //nas-name works fine.
All equipment is connected to a single linksys E3000 running DD-WRT firmware. The ReadyNAS is wired to the E3000, and the macbooks have been connected both wired and wireless with the same results. The E3000 is a pure WAP only; no filtering or firewall is active, there is a FIOS router on the external and it only supports G speeds which was unacceptable :)
So it really looks like the ReadyNAS isn't broadcasting AFP properly. I've tried unchecking every afp option and rebooting and turning on afp/bonjour options one by one with a reboot between each change to no avail.
Before you suggest CIFS (which works fine), the whole point of this is to get Time Machine working and TM is not seeing the CIFS share as a configurable remote device even if i connect to the ReadyNAS before running TM. It doesn't even see the afp share when i disabled cifs on the ReadyNAS and did an option-K to connect to the nas ip address.
A question I do have concerns name resolution for mac's. In the windows world if you are in the same workgroup, machines names are advertised via netbios (in the old days netbeui), is that what bonjour does in the mac world?
I've been searching the forums and reading some very long threads about problems with afp and SL, but it looks like the later firmwares were supposed to fix the afp problems.
Is this still an issue for people?
EDIT: Saw some threads about jumbo frames so I've tried both on and off, same results.
Any thoughs on this?
Here's the breakdown of my diagnostics
Macbook Pro is running 10.6.5 as of 11/10/2010 and the Macbook is running 10.6.3
BOTH Macbooks CAN see an AFP share for a ReadyNAS NV+ that I have in my office.
ReadyNAS Pro is running 4.2.15
ReadyNAS NV+ is running the latest version (the number escapes me)
On my home network the Macbooks CAN see each others AFP shares when i turn on sharing
There is no WINS server on the network
Now pay attention....
If I do an Option-K and explicitly type afp://nas-ipaddress it connects but it shows up as connected as a PC Server (so its dropping to smb anyway)
If I turn off CIFS on the readynas and explicity type afp://ip-address it connects via afp and shows up as a Mac Server (so now it can connect using AFP).
Under no circumstances does typing afp://nas-name work. It fails immediately.
However from windows boxes (when cifs is on of course), doing a start run //nas-name works fine.
All equipment is connected to a single linksys E3000 running DD-WRT firmware. The ReadyNAS is wired to the E3000, and the macbooks have been connected both wired and wireless with the same results. The E3000 is a pure WAP only; no filtering or firewall is active, there is a FIOS router on the external and it only supports G speeds which was unacceptable :)
So it really looks like the ReadyNAS isn't broadcasting AFP properly. I've tried unchecking every afp option and rebooting and turning on afp/bonjour options one by one with a reboot between each change to no avail.
Before you suggest CIFS (which works fine), the whole point of this is to get Time Machine working and TM is not seeing the CIFS share as a configurable remote device even if i connect to the ReadyNAS before running TM. It doesn't even see the afp share when i disabled cifs on the ReadyNAS and did an option-K to connect to the nas ip address.
A question I do have concerns name resolution for mac's. In the windows world if you are in the same workgroup, machines names are advertised via netbios (in the old days netbeui), is that what bonjour does in the mac world?
I've been searching the forums and reading some very long threads about problems with afp and SL, but it looks like the later firmwares were supposed to fix the afp problems.
Is this still an issue for people?
EDIT: Saw some threads about jumbo frames so I've tried both on and off, same results.
Any thoughs on this?
38 Replies
Replies have been turned off for this discussion
- sphardy1Apprentice
Chewbacca wrote: What is odd is if you connect via command-k with afp it shouldn't drop you to smb.
I would very much doubt that it is doing that. To be sure, the OP could test via the mount command as Charles suggested - netracerApprenticesphardy - thanks for the bonjour link, i will use that at some point. Took the router out of the picture earlier with a crossover cable (nas directly wired to laptop), but i still wouldn't mind an easier bonjour filter.
Chewie -
The firmware was upgraded. I don't know what the original was.
Would an OS reinstall be helpful or useless?
in the interim, I'll pull the logs... - netracerApprenticeLOGS SENT....good luck filtering through all the on/off i've been doing the past 48 hours.. :)
- ChewbaccaAspirantnetracer: you can do a OS reinstall just to make sure. I would also disable jumbo frames that Linksys E3000 doesnt support Jumbo from the quick google search.
Was this working before the upgrade to 4.2.15?
Ill keep looking through your logs. - netracerApprenticeActually already tried disabling jumbo. Turned it back on after 2 days of having no effect. I'll turn it off again to be sure.
I don't know if it was working before 4.2.15. I've ignored my kids macbook for a while and just decided it was time to back up all his pics (IT guys are the worst at doing backups of their OWN stuff...lol) - AddeBCAspirantExact same problem. AFP isnt broadcasting via bonjour. i have a mac book pro and a nv+ latest radiator and latest osx updates.
everything was working great before but one of all updates have broken bonjour, or actually it worked until i updated nv+.
i got exactly the same problem as previous poster. ive tried stopping bonjour service and starting it again...no luck
ctrl-k connects to afp no problem... i need bonjour to work for firefly n itunes... - AddeBCAspirantUpdate. logged on with ssh just to check status of avahi-daemon. Killed process and restarted just to get the output:
as-02-04-AF:/etc/avahi# avahi-daemon
Found user 'admin' (UID 98) and group 'admin' (GID 98).
Successfully dropped root privileges.
avahi-daemon 0.6.15 starting up.
Loading service file /etc/avahi/services/afp.service.
Loading service file /etc/avahi/services/cifs.service.
Loading service file /etc/avahi/services/frontview.service.
Loading service file /etc/avahi/services/readynas.service.
New relevant interface LeafNets.IPv4 for mDNS.
Joining mDNS multicast group on interface LeafNets.IPv4 with address 5.168.46.242.
New relevant interface eth0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 10.10.10.12.
Network interface enumeration completed.
Registering new address record for 5.168.46.242 on LeafNets.
Registering new address record for 10.10.10.12 on eth0.
Registering HINFO record with values 'PADRE'/'LINUX'.
Server startup complete. Host name is nas-02-04-AF.local. Local service cookie is 816897388.
Service "ReadyNAS Discovery [nas-02-04-AF]" (/etc/avahi/services/readynas.service) successfully established.
Service "FrontView on nas-02-04-AF" (/etc/avahi/services/frontview.service) successfully established.
Service "nas-02-04-AF (CIFS)" (/etc/avahi/services/cifs.service) successfully established.
Service "nas-02-04-AF (AFP)" (/etc/avahi/services/afp.service) successfully established.
As far as i can see everything should be working. But macbook wont see the afp services. - sphardy1ApprenticeWhat do you see if you try pinging the nas using the bonjour name?
ping nas-02-04-AF.local
- AddeBCAspirant
sphardy wrote: What do you see if you try pinging the nas using the bonjour name? ping nas-02-04-AF.local
Ahhh... it responds with nas-02-04-AF.local.mydomain.com <-- my external ip
I removed "mydomain.com from dns domain but then i get:
ping: cannot resolve nas-02-04-AF.local: Unknown host
Addes-MacBook-Pro:/ adde$ - sphardy1Apprentice
AddeBC wrote: Ahhh... it responds with nas-02-04-AF.local.mydomain.com <-- my external ip
Have you entered your domain name in Frontview -> Network -> Interfaces -> Global Settings ??
If so, try removing it
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!