Mountain Lion Compatibility

It's on a hard-wired connection. Interestingly, I have a couple Lion clients that have started getting the second error mentioned in the linked article while roaming. It's also interesting that this person had problems while you did not. Curiouser and curiouser...

(and thank for all your help on this, btw - very much appreciated)

I've got ML running on my Macbook Air. I just updated both remote software on the Mac and the ReadyNas Ultra2+, latest firmware. Trying to access the NAS via remote, and seeing insanely slow performance. Close to 5 minutes to just show the folder listing. Fast internet in both locations.

It was running well prior to these upgrades, and I made a few at once, so not sure where the problem lies.

thanks

Interesting - I've had no problems at all with performance on shares, just with the Time Machine share not appearing. Are you accessing the NAS via CIFS or AFP?

same problem
all latest firmware on my duo v1 (4.1.8)
upgraded raidar (4.3.4)
have tried different protocols afp,cifs etc. no luck
tried turning of time machine, rebooting, re-enabling. no luck

happens on both my iMac & air (both 2011).
was all fine before ML upgrade

Seems like the very annoying bug that was affecting AFP with OSX Lion for my older model X6 has been fixed! At least the connection isn't dropping constantly anymore.

benjyforrest the AFP in 4.1.8 should be new enough but that was released quite a while ago now (September 2011). If you are willing please try 4.1.10 beta: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222

Compared with 4.1.8, 4.1.10 includes a major samba (SMB/CIFS) update and a decent update to Netatalk (AFP).

All, have upgraded to Mountain Lion and running 4.1.10 t3 on NV+.

Have a really interesting problem, it looks like ML is ignoring permissions when listing shares under CIFS or AFP. Things that were listed under Lion - simply upgrade to Mountain Lion and they are not being listed. Has anyone else got this, the same problem is also occurring on a ReadyNAS Pro so I think it is definitely a ML issue. On another machine running Lion everything is fine.

Just installed ML on my MBP. So far it looks good; shares mounted ok and TM is currently updating the 10GB of changes that happened.
Hard Ethernet connected to a sparc Duo running 4.1.9.

All

Be warned, there is definitely an issue with the way that Mountain Lion reads shares both SMB and AFP versus Lion. I have done further testing today and the situation occurs consistently on a ReadyNAS NV+ ( 4.1.10 T3 ) and ReadyNAS Pro. *Some* existing shares correctly appear within Finder in Lion but don't in Mountain Lion on both machines. I have done a load of testing and I can't see any commonality to this. Even creating shares dont always appear, I thought it was possibly something to do with the use of the underscore character in the share name but I now not sure.

Can the Jedi Council look into this please, there is definitely a problem. It looks like Apple have changed something under the covers that is causing a problem.

I have unusable transfer performance since upgrading to Mountain Lion.
Firmware: RAIDiator 4.1.9 [1.00a043]
Model: ReadyNAS NV+ [X-RAID]