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
sphardy wrote: 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
Yes, the domain was there too... I removed that + removed mydomain.com from dns server.
but read output updated in previous post.- Have you rebooted? Might be a good precaution just to be sure the NAS comes up cleanly with the revised settings
- Yes ive rebooted.
I think the problem is my network setup. Im not so familiar with bonjour.
In search domains on the mac i have mydomain.com
In my router i have mydomain.com as domain.
When i ping NAS.local it returns NAS.local.mydomain.com Which goes to an external ip, shouldnt it stay on the internal network? - You normally only have a domain specified if you are running a DNS server on the network - which most home users do not. I would remove all references to the domain name on the router and macs as well as the NAS
- hmmm... My router wont allow me to remove it... It requires domain name. Hostname and domainname... Im running pfSense FreeBSD based firewall/router...
And if i remove it in the mac it still adds it from the router ?!?! annoying...
Just to get it right - when i ping nas.local it should return with the local adress which it gets via the bonjour service? - Correct
- Server startup complete. Host name is nas-02-04-AF.local. Local service cookie is 5686675
Directly from readynas shell if i do: ping nas-02-04-AF.local
It cant resolv host.
However if i skip local its fine... Is that supposed to be? - No - skipping .local means the NAS is just resolving it's name using the local /etc/hosts file
- Taking my thread back :)
Chewie - you sent me a PM which i responded too but haven't heard back. Something about the avahi account missing and whether i had ssh.
SSH is NG, I've got the issue where you get disconnected after providing correct credentials. netracer wrote:
SSH is NG, I've got the issue where you get disconnected after providing correct credentials.
And you are trying to connect as user "root"? (No other user is enabled for SSH access)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
