Mountain Lion Compatibility

ReadyNAS Remote is now compatible with Mountain Lion: http://www.readynas.com/forum/viewtopic.php?f=75&t=66468

Reposted this in the ReadyNAS Remote subthread as well.

Hey guys, anyone else having the problem where after I add my User in the Add-Ons section in Dashboard, I can't connect to my NAS on the Mac itself? I see 6 options on my top taskbar when I click the remote icon.

Properties -> (Grey'd out)
Shares > Does nothing
Manage -> Does nothing
ReadyDrop -> Does nothing
Log Out -> Works
Exit Works

There is no "Connect to ReadyNas option.

Cheers

I have problems with Mountain Lion and Ready NAS Duo v1. When my Macbook Pro goes to sleep and wakes up time machine stops working and cannot find NAS. Raidar stops working too and AFP service works very randomly. Hope Netgear will release fixed firmware to these issues, I dont wanna buy new NAS device becouse of it works fine on my Win7 pc and I have used this Duo many years succesfully.

ak72: have you tried the latest firmware?

More troubling behavior I've encountered. I don't know if this is Mountain Lion related or not. When connected via wired ethernet, I see the the Duo in the Finder Sidebar (three entries: hostname, hostname (AFP), and hostname (CIFS)). If I turn on WiFi and disconnect the wired ethernet, these three entries remain and are accessible. Turn WiFi off, and they go away (expected behavior), turn WiFi back on and they don't come back--even after several minutes. Plug in the wired ethernet and they immediately appear. Unplug the wire (WiFi still on, NAS entries in Sidebar) and try to run a Time Machine backup, it fails (error 19) and the hostname (AFP) entry disappears while the other two remain. If I try to mount the CIFS entry, it too disappears.

I probably would not have happened upon this except for tinkering with location services, Find My Mac, and FileVault. I normally use a wired connection with WiFi off. I thought it might be useful to have the WiFi on during vacations as it could help were Find My Mac needed in the event of a theft.

What router do you have? There are known instances of wireless routers that do not properly support broadcast traffic over wifi - Thomson routers are a major culprit (I have one) and are often supplied by ISPs

I used to document here: http://sphardy.com/web/readynas/apple-s ... over-wifi/

I'm having an interesting problem where if the iMac goes to sleep (ethernet) for a long time (like last night), when I wake it up it is no longer connected via AFP. Looking through the logs:

9/18/12 10:34:59.323 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fdb68c41880> Tue Sep 18 22:53:18 2012 MDT (approx)
9/18/12 10:34:59.000 PM kernel[0]: AppleBCM5701Ethernet: 3 4 compare_link_settings - failed linespeed check
9/18/12 10:34:59.000 PM kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0 (wol enabled, BJP 1926)
9/18/12 10:35:01.022 PM KernelEventAgent[41]: tid 00000000 received event(s) VQ_NOTRESP (1)
9/18/12 10:35:01.023 PM KernelEventAgent[41]: tid 00000000 type 'afpfs', mounted on '/Volumes/Media', from '//eriddler@Leaman-NAS%20%28AFP%29._afpovertcp._tcp.local/Media', not responding
9/18/12 10:35:01.000 PM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 1 on so 0xffffff801e87b370
9/18/12 10:35:01.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Media prevTrigger 1 currTrigger 2
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Media
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Media
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 60 secs, Connect timeout: 30 secs for /Volumes/Media
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Media
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Media failed 49.
9/18/12 10:35:01.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/18/12 10:35:01.023 PM KernelEventAgent[41]: tid 00000000 found 1 filesystem(s) with problem(s)
9/18/12 10:35:02.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Media
9/18/12 10:35:02.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Media failed 49.
9/18/12 10:35:02.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/18/12 10:35:03.000 PM kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [796d,0301,0181,0000,cde1,0800]
9/18/12 10:35:03.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Media
9/18/12 10:35:03.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Media failed 49.
9/18/12 10:35:03.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/18/12 10:35:04.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Media
9/18/12 10:35:04.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Media failed 49.
9/18/12 10:35:04.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/18/12 10:35:04.071 PM configd[17]: network changed: v4(en0-:192.168.1.3) DNS- Proxy- SMB
9/18/12 10:35:04.073 PM configd[17]: arp_client_transmit(en0) failed, Network is down (50)
9/18/12 10:35:04.074 PM configd[17]: bootp_session_transmit: bpf_write(en0) failed: Network is down (50)
9/18/12 10:35:04.074 PM configd[17]: DHCP en0: INIT-REBOOT transmit failed
9/18/12 10:35:04.075 PM configd[17]: DHCP en0: ARP detect ROUTER failed, arp_client_transmit(en0) failed, Network is down (50)
9/18/12 10:35:04.000 PM kernel[0]: Wake reason: RTC (Alarm)
9/19/12 12:34:59.000 AM kernel[0]: RTC: Maintenance 2012/9/19 06:34:59, sleep 2012/9/19 04:35:04
9/19/12 12:34:59.907 AM KernelEventAgent[41]: tid 00000000 received event(s) VQ_DEAD (32)
9/19/12 12:34:59.907 AM KernelEventAgent[41]: tid 00000000 type 'afpfs', mounted on '/Volumes/Media', from '//eriddler@Leaman-NAS%20%28AFP%29._afpovertcp._tcp.local/Media', dead
9/19/12 12:34:59.908 AM KernelEventAgent[41]: tid 00000000 force unmount //eriddler@Leaman-NAS%20%28AFP%29._afpovertcp._tcp.local/Media from /Volumes/Media
9/19/12 12:34:59.908 AM KernelEventAgent[41]: tid 00000000 found 1 filesystem(s) with problem(s)
9/19/12 12:35:00.000 AM kernel[0]: Previous Sleep Cause: 5
9/19/12 12:35:00.000 AM kernel[0]: 13303.796976: setDISASSOC from ATH_INTERFACE_CLASS disconnectVap
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Media
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Media failed 65.
9/19/12 12:35:00.000 AM kernel[0]: ]
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA to unmount /Volumes/Media
9/19/12 12:35:00.000 AM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 2 on so 0xffffff801e87b370
9/19/12 12:35:00.000 AM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Media prevTrigger 2 currTrigger 3
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_DoReconnect: already in unmount /Volumes/Media
9/19/12 12:35:00.000 AM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Media, flags 524288, pid 41


It seems there is an issue with the system trying to reconnect. Anyone have any thoughts? Working ReadyNAS Duo 4.1.8, just upgraded this machine to ML...waiting to upgrade the MBP until I can figure this out.

4.1.8 included Netatalk 2.2.1dev. That's an old version of Netatalk.

You may wish to try 4.1.10-T3 which includes Netatalk 2.2.3-p1 and see if it's any different.

I have 4.1.10-T3, problems started after upgrading OS X to Mountain Lion. If I boot my MacBook Pro all works fine, afp,time machine etc but if computer goes to sleep and wakes up again later afp works randomly and time machine cannot be find. Raidar also don't find NAS after wake up.

Sounds like a router compatibility issue as sphardy mentioned.

mdgm wrote:
Sounds like a router compatibility issue as sphardy mentioned.

I had D-link DIR-655 earlier, now Asus DSL-N55U. Same problem on both routers.