NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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
- There shouldn't any issues connecting via afp with SL.
Have you verified that you have afp enabled on the share and the correct access?
Are you seeing that it is connecting as as SMB share instead of a AFP when you do a get info on the share in finder?
So you are not having a issue with the NV+?
Can you try direct connect? - When both CIFS and AFP are enabled on the NAS, yes it is connecting as an smb share when i connect whether I browse or access via opt-k
However, if I disable CIFS on the nas, and do an opt-K and open afp://nas-ipaddy it connects as AFP (there is nothing in the finder view when afp only)
So AFP 'works', but it won't advertise
When you say direct connect - you referring to a crossover cable? I have not yet tried that, will do that shortly if I can find one in my box of spaghetti...
I did try all devices wired into the same switch, same problem.
And correct, I am NOT having an issue with the NV+, however that is on a different network.
On both networks I am in the same broadcast domain as the nas box (both /24's)
A new bit of information - might be helpful, might be unrelated.
I enabled the itunes streaming server on the NAS and cannot see the itunes library anywhere on the network. However I can see my shared windows7 itunes library on my macbook, and i can see my macbook shared library on the win7 itunes machine. But neither can see the nas itunes library.
Thanks! - That is odd with afp disabled on the share you should not be able to connect via command-k afp://nas you should receive a error message and I was able to reproduce that it does that here.
You will not need a cross over cable to direct connect. The nas will get a 192.168.168.168 address unless you have a static address setup.
What happens if you move the Pro to the same network as where the NV+ is do you have the same issue or move the nv+ to this network?
Sounds like something is not routing correctly. - So i just connected a crossover connection and still no joy (i verified i could still cifs to it). I do need to correct you on an item - I disabled CIFS not AFP, so that the mac would be forced to connect via afp. It does but only via command-k. The afp-nas does not show up in the finder.
When both cifs and afp are enabled i only see one device in finder - "nasname" - if i do a get info it says pc server.
As near as I can tell, I think its Bonjour that is hosed (though I'm no expert on mac protocols). I can't see anything off the nas, no itunes library, no shares, nothing. - oh, ps. my nv+ is in the office and pro is at home. Lugging isn't really an option :). Though with the crossover test, I'm pretty confident we can take network out of the equation (that's one area i am pretty good at :) ).
- That is odd on the 4 OS X boxes I have 3 Snow Leopard 10.6.5 and one Leopard Server I see both my Pro (4.2.15) and NV (4.1.7). If I disable "Advertise AFP service over Bonjour" I no longer see it as a shared device but I can connect to it.
Here is and snippet from the output from the mount command on one ov my OS X boxes:afp_2fL3am1QCL8d3GXSKG2m3XVo-1.2e000003 on /Volumes/home (afpfs, nodev, nosuid, mounted by user)
afp_3uNoO71b4qRD1in8Yu44x6nH-1.2e000004 on /Volumes/home-1 (afpfs, nodev, nosuid, mounted by user)
I have mounted my user share via AFP from both my Pro and NV. - yea, it is bizarre. It seems like the "Advertise AFP service over Bonjour" checkbox has no effect and is stuck in the off position.
can you explain how you got those snippets? - The snippet is from the mount command.
I opened a terminal window and at the prompt I typed in the command "mount" and hit enter.
It shows info about the mounted volumes. The afpfs in the parentheses indicates it is mounted as an AFP file system. netracer wrote: yea, it is bizarre. It seems like the "Advertise AFP service over Bonjour" checkbox has no effect and is stuck in the off position.
Could your router be blocking the bonjour broadcasts rather than the NAS be at fault? Do other devices show?
There's a small app called bonjour browser you can download that will show you all the Bonjour activity on your network
http://www.macupdate.com/info.php/id/13 ... ur-browser- What is odd is if you connect via command-k with afp it shouldn't drop you to smb.
Is this the firmware that came installed on this NAS?
Can you send in your logs maybe I can see something that could be causing the issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
