NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jonsenge
Jul 23, 2012Aspirant
Mountain Lion Compatibility
Is there any early word on Mountain Lion compatibility for the ReadyNAS models?
112 Replies
Replies have been turned off for this discussion
- Josc73AspirantHi there!
Upgraded my Mac's to ML and guess what? No luck with Time Machine anymore... I've been reading on this forum and tried the following:
1. Restarted the ReadyNAS
2. Restarted my Mac with Time Machine off and then re-initiated it after restart
3. Upgraded the Duo to 4.1.10-T3
4. Double checked that AFP advertises over Bonjour.
The strange thing here is that I can get it to backup once if I disable AFP and the reenable it. Then it will backup, although very slow. Takes about 2 minutes in the state "Looking for backup disk" and then it gets going. If I try to make a new backup directly it will not work. Also my shares (AFP) has disappeared. It is almost as Time Machine disables the share in the clean-up phase?
Anyone else experienced the same?
/Joakim - edantoAspirant@redpola Thanks! I came here looking for a fix to the dropped connection problem and fingers crossed your suggestion has helped. Appreciate you posting it.
- step_andy1AspirantUpgraded to ML and Time Machine no longer works for Ready NAS NV v2.
Also, ReadyNas Raidiator widget will not launch - getting an error message that developer isn't authorised.
Cheers
Edit: went through the set up from scratch and TM is working again. - bluewammerAspirantI haven't upgraded to ML yet, but I understand that if you right click on an app icon and use the 'open with' command, there is an option to authorise an 'unauthorised' app to run - you only need to do this once.
- mdgm-ntgrNETGEAR Employee Retired
step_andy wrote: Upgraded to ML and Time Machine no longer works for Ready NAS NV v2.
Please open a support case.bluewammer wrote: I haven't upgraded to ML yet, but I understand that if you right click on an app icon and use the 'open with' command, there is an option to authorise an 'unauthorised' app to run - you only need to do this once.
Yes. This trick works well. - dgerson76Aspirant
kolz wrote: READYNAS REMOTE NO LONGER WORKS
you connect.. it sees the shares, asks you to select which shares you want to mount, then the connecting to 5.x.x.x. dialog continues forever. The NAS shows up in Finder but non of the shares do and the connecting dialog still shows :( :oops: :oops:
SAME ISSUE. Can someone please help?
Macbook air/ML.
Ultra2+ with latest firmware and latest Remote software.
Shares eventually mount but can't see anything past the 1st level of folders.
This was working perfect prior to last firmware and readynas remote software.
HELP! - I'm having an issue accessing the WebDAV service on my ReadyNAS Pro, which is running the latest production firmware, from a Mountain Lion machine. Accessing the ReadyNAS WebDAV share on Lion and Snow Leopard works great, but the machine running ML fails to connect. I can ping the webdav server from the ML machine, but not connect via WebDAV. I can also access the ReadyNAS shares from AFP without an issue (in my limited testing). I've been scouring console for the error, but can't seem to find the failure.
Reading up on the issue on the Apple Support forums, it appears Apple made a change that requires a server (e.g. ReadyNAS) change? https://discussions.apple.com/thread/41 ... 0&tstart=0
Anyone else having this problem? - sphardy1Apprenticesircoolio - this is not necessarily a Server change that needs to be implemented, but a client change.
The ReadyNAS issues a self-signed certificate to enable SSL support (i.e. the "S" in "HTTPS", and self-signed as those do not cost you anything)
Web browsers always warn you before accessing services over HTTPS where the certificate is self-signed and allow you to set the certificate as trusted to avoid future warnings. Finder doesn't have such a feature and has previously always defaulted to trusting the certificate. It appears that security hole has been closed in ML by now defaulting to not trusting self-signed certificates. But as there is no mechanism to ask to trust the certificate built into Finder you must therefore you must use the KeyChain app on your client to first trust the certificate - once done Finder should connect as before
The alternative is to make a server change and buy & install a certificate from a trusted authority (eg Comodo, verisign etc) - you can read how here: http://url.sphardy.com/Romarm
I've just tested connecting to my NAS with trusted certificate installed over HTTPS from Finder on my ML MacBook - works just fine as shown below:
- I ran into an issue with mine, and the initial steps (Enabling AFP) didn't seem to work for me. Then again, my NAS hung in the middle of a backup, which may have corrupted something... in either case, here's the steps I took to fix the issue, and it seems to be backing up now.
1) Follow the steps here, to delete any old backups: viewtopic.php?f=71&t=60831
2) While there, also delete the .AppleDB and .AppleDouble folders (from SSH, do a "rm -rf .AppleDB" and "rm -rf .AppleDouble" command)
When you are done, the only files in the /c/.timemachine directory (or the home folder you've designated as your backup) should be:
.AppleVolumes
.com.apple.timemachine.supported
Once I did this, my TimeMachine backup ran without issues. - Josc73AspirantStrange, when I check my /c/.timemachine directory I haven't got .AppleVolumes or .com.apple.timemachine.supported? What will happen if it is empty?
/Joakim
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!