Lion Time Machine still not working for me (NV+ 4.1.8)

[sphardy]

I don't think the issue is bonjour related specifically but with connecting via device name. Bonjour sees it, then when you try connecting it will disappear when it is not able to connect. Bonjour uses the device name such as "afp://NAS" or "afp://AFP%20on%20NAS._afpovertcp._tcp.local" is the actual connection mine used. If you try to manually connect via device name it will not connect either.

FYI that again further confirms the issue is bonjour related

For Mac connectivity - be it for share access or TimeMachine - there are 2 services involved: the AFP file server which is implemented using an application called Netatalk, and the Bonjour service implemented by the application Avahi

The AFP server (netatalk) has no involvement in the name to IP address resolution - that is totally the function of the bonjour server (avahi) which provides different advertisements for normal shares vs the TM service (your example is the name used to advertised normal share access only and not TM, and the fact that it "disappears" suggests the ip address is not being resolved correctly)

The only way I can think of to fix this (if Netgear cannot reproduce and given @awperk has shown resetting the TM service does not fix the issue) is to check the actual avahi configuration files of one of the failing units, and to get that to happen you would be best advised to log an official support case with Netgear as @mdgm suggests

Good Luck

[joudbren]

I'm also having the same issue with Lion and NV+ 4.1.8. I was successfully able to delete the old TM backup on the ReadyNAS and successfully able to setup and do a Lion TM backup to the ReadyNAS. After that however, no go. I couldn't access TM or do a subsequent backup. If I go into the ReadyNAS and disable and re-enable TM then I have access again but only for one instance. The I have to repeat the cycle.

I've also tried "connect to server" via OSX using my TM user i.d. and password and that makes the TM available again as well and it appears to stay connected for subsequent sessions. However I then cannot access the other shares on the ReadyNAS unless I log back into the box via "connect to server" with my normal user I.D. and password. Once I connect back with my regular I.D., yep, TM drive disappears again. Frustrating to say the least and hopefully someone a lot smarter than I am with this stuff can come up with a solution. Cheers!

James

[Arafel]

I would suggest opening tech support cases (http://www.readynas.com/support). If NetGear can reproduce the issue and confirm that it's an issue with the firmware then it'll be addressed in a firmware update.

The scary thing is I attempted to open a case and the link provided on the readynas support url you gave us goes to a site with an expired security certificate.

[Chewbacca]

Arafel: Can you send in your logs so we can take a look at this? I am unable to reproduce the issue.. I am having no issues with OSX Lion and RAIDiator 4.1.8 with time machine.

[Arafel]

Arafel: Can you send in your logs so we can take a look at this? I am unable to reproduce the issue.. I am having no issues with OSX Lion and RAIDiator 4.1.8 with time machine.

I am at work currently but tonight I can send you all the info I have. What logs do you want and how shall I send them to you? Thanks for the response and hopefully can identify the issue.

[atlgator]

FYI, this sounds EXACTLY like what I have experienced with the 4.1.8 Beta on my Duo. I finally solved my Bonjour issues by blowing away the Time Machine backup on the Duo and starting from scratch on my backups. This seemed to have stabilized Bonjour on the NAS so it no longer stops working. I haven't really seen any comments from the Readynas team that they're chasing this even though there are multiple other people that have reported the same issue. My problems started with the upgrade to Lion and the beta did not solve them (though it did solve the ability to connect to the NAS at all over AFP using IP) until I wiped the TM backup file.

See below:
viewtopic.php?f=28&t=55683

[Chewbacca]

Arafel: Directions are in my signature.

[Chewbacca]

Arafel: Do you get a error message when you try to connect to time machine?

Can you also install Bonjour browser and let me know what port your nas is on for afp and also adisk?

[Arafel]

If i restart the "Advertise AFP service over Bonjour" in frontview or do a full readynas duo restart I get this in Bonjour browser:
Local
Apple File Sharing (_afpovertcp._tcp.)
NAS (AFP)
192.168.1.2:548

That is the correct address for my readynas duo. After I try connecting via finder, the readynas duo no longer is listed in bonjour browser and disappears from finder's share listing. It almost seems like the bonjour service is crashing though nothing was in the log files about that as you probably saw.

I no longer get an error in time machine since I have it connecting via IP address manually and it no longer will detect the readynas drive in the select disk option.

From another post I had made in the osx forum: viewtopic.php?f=28&t=56813 I copied the old error I was getting:

When Time Machine tries to connect I get the same error proceeded by:
"There was a problem connecting to the server “NAS.local”."

[sphardy]

Definitely appears that the Bonjour service is crashing which would explain all the symptoms

[bab5139]

This is the exact same issue I have with the PRO 6 and NV on my network. If any shares have "guest" access enabled I can access them and the share stays in the finder window. The instant I try to "connect as" the share disappears!. How come no one has solved this?

[mdgm]

Under Services > Standard File Protocols > AFP do you have "Advertise AFP over AppleTalk" enabled? If so could you try disabling this option? AppleTalk is only really needed for very old Mac clients (Mac OS 9 or possibly an even older machine, I think).