Readynas mac os x lion

Did you recently change your router or change the settings?

If so, ensure that you have multicast DNS enabled or that your router has this capability at all. Then delete all those items in the original folder. Then restart your computer. For good measure, reset your ReadyNAS user password.

Not sure if this does anything, but I happened to change mine when I was fixing my problems with TM. In fact, I was just about to write a post about it. Try connecting manually.

Yes, I changed from 4. I had hoped it would solve the problem. I recently swapped one wireless router with another. Both are, and was, set up to only act as a WAP, as I kept them configured on the same subnet as my router, and to not act as a router. Suggest other similar software suggested. Current Version 6. Downloads 7, Version Downloads 1, License Free. Date 10 Apr Price Free.

To leave a comment, you need to be logged in. Log in.

Helpful answers

Sign up. Sort by: Be the first to review this app and get the discussion started! Create a sparse disk image on the backup disk, mount it, then use "tmutil" to set the mounted sparse image as the destination for Time Machine. I've changed the detail a bit to take out the unnecessary steps.

• Mac OS X 10.7, Time Machine & ReadyNAS NV+?
• Enable Time Machine on unsupported network drives - Mac OS X Hints.
• vlc media player mac 10.5.8;
• mac and cheese pizza buzzfeed recipe.
• the last place on the net.
• athan for mac os x.

I don't have a Mac here at work, and I don't have a network drive to test it with, but here you go anyway: Mount the remote volume. In Finder, "Connect to server" and enter "smb: Open a Terminal and type the following commands: Yep, that's it. The only thing I would change from your summary is step 2a.

You are creating the sparse bundle directly on the external drive. For my NAS I couldn't. I was getting errors. I had to create the sparse bundle on the local drive and then copy it to the remote drive. Everything else looks good. I can also confirm that the copy is needed at least for my Linksys router's SMB share.

In fact I suspect that's part of the reason you can't set up TM directly on these shares anymore. I hadn't really paid much attention to these posts and just tried following the steps outlined here without the copy and kept getting an error saying the sparsebundle couldn't be created. Finally I realized on my own that maybe I could create the file locally and copy it over I think this should be listed as either it's own hint, or at least highlighted as a recommended alternative to this hint.

3 posts in this topic

I did not want to go replacing any System files like Craig mentioned you had to do I didn't even bother looking at the link after I read that and this is a very easy to understand solution that seems a lot less likely to break in a System Update. Edited on Sep 27, '11 Another option that doesn't involve lowering your security is to check if there is updated software for your unsupported drives. Hacking time machine to back up to unsupported devices is possibly very foolish. The last thing you want to do is risk the integrity of your backup.

After all, the point of time machine is to keep your data safe. If SMB servers are not supported because they don't have the required flushing protocol the ability to verify that data has been written to the disk image to avoid corruption then hacking things to make it "work" will run the very real risk of corrupting your whole backup if there is a network interruption. Given how difficult it has been for Apple to get their own network backup system Time Capsule working reliably, I would be very, very wary of trusting a hack for a third party device.

Lost your password? Powered by the Parse.