I just connected My Book LIve to my network, and am not able to see the drive in Time Machine using a wireless connection. When I connect the computer directly to the router using an ethernet cable, I can see it in Time Machine and do a backup successfully. As soon as I disconnect the ethernet cable, Time Machine can’t find the MyBookLive disk.
When connecting wirelessly, I can see My Book Live under Shared in the Finder. I used ‘Go → Connect to Server’ to add the My Book Live IP address, which it did and mounted both Public and TM folders under ‘MyBookLive-tm’ in the Shared section. I can go to that IP address in my browser and setup and change Users. I am connected to MyBookLive under a User I created this way. I have the network mode for MyBookLive set to DHCP.
What do I need to do so that Time Machine can see the MyBookLive disk? I have three different Macs wirelessly connected to the network that I would like to backup via Time Machine to the WD MyBookLife, and am having the same issue with all three. Any help you can provide would be appreciated.
Dang, I’ve spent several hours on this and can’t seem to get any headway. The My Book LIve Discovery (nore time machine) cannot see the network while connected to my PK5000 modem, it only sees it while directly connected to the Mac.
I was able to ping it and Time Machine can see my router, I read on the apple forum that the WPA settings on the router may have been too high so I did away with WPA and WEP security as a test and it worked! Link: https://discussions.apple.com/message/12420839#12420839
Well, I think it worked, I am now getting error after only a few minutes of starting Time Machine. ‘MacBook Pro.sparsebundle" could not be created (error 45).’ I’ll be searching around for the cause this error…
It works fine at work and home with my My Book Live. What type of Network setup are you running. Usually this is the culprit. Have you connected your MBL directly to your Mac and tried running TIme Machine?
As an FYI, the newest Netatalk client (when released) will have much more robust handling of connectivity issues. Once it is released we will update the MBL with this version as OS X Lion requires all third party implementations of AFP to be running at version 3.3.
