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
- For both ToggleSSH & EnableRootSSH, when I try 'root' and the admin password, it tells me bad password. If I use 'admin' and the admin password, it just closes the connection.
- ToggleSSH is for enabling tech support access to your NAS only. Try installing EnableRootSSH once more
- Done it, still no joy. Even tried editing/replacing the shadow file to get the root pwd and admin pwd the same.
netracer wrote: Done it, still no joy. Even tried editing/replacing the shadow file to get the root pwd and admin pwd the same.
And you did that how given the issue you report is not having SSH access?
Sorry, but I'm no longer sure what the problem is- backed up the nas config via the web interface, ripped the shadow file out of the zip, edited, replaced and then restored via web interface.
In any event, it's all good. Chewie is sending me a special addon that i guess phone galactic hq :) - Did this ever get resolved?
I have the exact same problem with a ReadyNAS pro running RAIDiator 4.2.21 and I have also seen this on my NV+ as well.
I only have AFP enabled (no CIFS),
Randomly the share name disappears from the sidebar, but I can still connect via AFP or NFS if I use CMD-K and an IP address. afp://ip.address/share_name or nfs://ip.Address/share_name
Stopping and starting Avahi via ssh, or via fontview doesn't help.
It appears to be a Bonjour issue but not sure how to get it going again. Usually a client reboot fixes this, but I don't want to reboot all the time.
This happens across two different NAS's (and also multiple MACs), and they are all on the same network (Via Wireless APs), only router is he ADSL gateway to the outside world.
Would love to be abel to track this down and fix it for good.
Any suggestions? - Everything is working now, but to be honest its been so long ago I don't remember the final fix. I think also sometime since this issue, I've done a complete factory reset
- Same here. I have tried 4.2.19, 4.2.21 and most recently 4.2.22 and file permissions do NOT work with Mac OS X Lion. Files and folders disappear randomly while access rights are incorrect for most of the files that do show up in Finder. File ownership and Group ownership is wrong. However, when I downgrade to 4.2.17, everything comes back to normal (except with TimeMachine): files that had disappeared, reappear, etc.
I thought it could be due to inconsistent file permissions to start with, but even when I re-apply the correct file permissions, I still have the same behavior.
I have looked through this Forum, on Wiki's, etc. and I see there are several people experiencing similar issues and there does not seem to be a good solution. I keep on hoping that a new firmware will resolve these problems, but... I keep waiting.
To be honest, I am VERY DISAPPOINTED with NetGear and the ReadyNAS team. I bought two ReadyNAS devices (ReadyNAS Pro Business Edition and a ReadyNAS Ultra 6 Plus) in order to use them with my Macs, but it is pretty clear that the support for MAC is VERY LIMITED.
For a $1000 base, diskless system (and I have TWO that last year I paid around $1500 last year!) I would expect it to work flawlessly with Mac OS X.
If I am wrong, I BEG you to point it out and provide some guidance on how to resolve these issues.
My setup:
ReadyNAS Pro Business Edition (3x1TB and 2x2TB) FW 4.2.17
ReadyNAS Ultra 6 Plus (3x2TB) FW 4.2.17
iMAc with Mac OS X 10.7.5
Macbook Pro with Mac OS X 10.7.5
Macbook Air with Mac OS X 10.7.5
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
