NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kentex
Jul 05, 2012Aspirant
CIFS won't mount after update to 4.1.9
System is ReadyNAS NV+
Running Mac OS X ver. 10.7.4
Just updated Radiator from 4.1.8 to 4.1.9.
When trying to access any CIFS share, I get the error message "The operation can’t be completed because the original item for “<sharename>” can’t be found."
Everything was working fine on Radiator 4.1.8
Thanks for any help.
Running Mac OS X ver. 10.7.4
Just updated Radiator from 4.1.8 to 4.1.9.
When trying to access any CIFS share, I get the error message "The operation can’t be completed because the original item for “<sharename>” can’t be found."
Everything was working fine on Radiator 4.1.8
Thanks for any help.
16 Replies
Replies have been turned off for this discussion
- jebrAspirantI have a similar issue. Just upgraded ReadyNAS NV+ to 4.1.9. Client - Mac OS X 10.7.4.
I have 5 shares and but one of them is not able to be mounted via AFP or CIFS from the mac. I have even tried mounting it from a Windows XP VM (that previously had access via CIFS).
The share name is "shared_files" - I tried renaming it without the _, I tried relaxing the security to default access Read-Only but nothing works.
I have spent hours fiddling with this now and rebooting the NAS etc. so am very upset.
The only workaround I have found was to mount the "c" share as the admin user and copy the data off into a working share. Also creating new shares is ok and they are able to be mounted.
Any help or suggestions would be very welcome.
JEBR - pugilaresAspirant4.1.9 is problematic. It's better to go back to 4.1.8. Please, just browse through this forum. So many posts about problems with 4.1.9. Please, take look at viewtopic.php?f=17&t=64230 I don't know why Netgear did not withdraw this release as an official yet.
- jebrAspirantHmm a further update.
CIFS via the finder shared area I can see all the shares (my 5 original and a new one I was hoping to move my broken ones data to) after authenticating.
However, like kenex I get the "The operation can’t be completed because the original item for “house” can’t be found.". So I can mount none of them.
AFP via the finder only shows 4 of my 5 original shares (not the new one or broken one) and all 4 mount ok.
What a nightmare!
I'm going to try reverting back to 4.1.8 - jebrAspirantNetgear please can I have a download link to 4.1.8 - I don't have a copy and want to downgrade.
- pugilaresAspirantI don't see the 4.1.8 on the readynas.com anymore. Yesterday it was still there http://kb.netgear.com/app/answers/detail/a_id/20684/
- jebrAspirantFound it - fingers crossed the downgrade works!
http://www.readynas.com/?cat=8 - pugilaresAspirantDowngrade to 4.1.8 after 4.1.9 works. I have done it and I have read posts of other people did that with success.
- kentexAspirantMoved back to 4.1.8 and all is well. Thank you pugilares and jebr for the link back to 4.1.8
- lucs12AspirantThe same problem here after "upgrading" to 4.1.9:
ReadyNAS DUO
MacOS 10.6.8: "The operation can’t be completed because the original item for “share” can’t be found."
:cry:
WORKAROUND: After I changed, over SSH, the user and group of the share folders in /c from "nobody:nogroup" to myuser:mygroup, I could mount the shares in both MacOS and Linux. However, as soon as I open the "Advanced Options" tab for a share, the owner and group of the share are automatically changed to "nobody:nogroup" and I cannot access the share anymore. Rebooting the ReadyNAS also reverts the owner and group of a share to "nobody:nogroup". - despawsAspirantAfter upgrading to 4.1.9 I had no problem with any shares that were both CIFS and AFP previous to the upgrade, but the one share I had that was AFP only was not visible. Adding CIFS to it made it visible in SMB sharing, but unmountable due to a permissions error on either Windows or Mac, any recent version. I tried many things to fix it with no success, until finally I did the following: default CIFS: read/write, guest access on and read/write. AFP same. Also, on advanced tab choose a primary user and give ownership/read/write, choose a group with all users in it, and give read/write, and most importantly, give read/write to "everyone". After that it showed up and I slowly clawed share permissions back to what they were originally, and the share was now visible under original permissions. I tried various combinations of the above, but the only thing that made it visible was doing ALL of it. As I said, after that I could restrict permissions to what they were before, but until I opened it up completely, no go.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!