NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
The specified extended attribute name was invalid
I have created folders in a share on my ReadyNAS and configured access via AFP (for access from Mac OSX) and via SMB (for access from Windows).
When I create folders and files using my Mac (running Snow Leopard) and then try to copy these files from the NAS using a Windows system, I often get an error near end of the copy which tells me there is a problem with an extended attribute. The Windows error code is 0x800700FE
After some research I came across a useful article at http://www.stanford.edu/group/macosxsig/blog/2008/04/ive_been_doing_some_mucking.html
This describes the same problem. It seems that when the extended attribute includes a character like colon (:) the Windows O/S complains and the copy is unsuccessful.
When I use ls -l@ to list files I can see extended attributes on the files do indeed contain : character. See example below:
$ ls -l@ *.TAR
-rw-r--r--@ 1 talsop staff 6723173 20 Apr 08:04 20004566.TAR
com.apple.quarantine 85
com.apple.metadata:kMDItemWhereFroms 339
$
Since I am sure many people use AFP and SMB together for accessing files from Windows and Mac, I wondered how this issue has been solved by others ?
I am using a ReadyNAS 4200 running latest 4.2.19 Radiator.
I am using Active Directory for authentication, but I doubt this is the reason for the issue.
Thanks,
Tim
When I create folders and files using my Mac (running Snow Leopard) and then try to copy these files from the NAS using a Windows system, I often get an error near end of the copy which tells me there is a problem with an extended attribute. The Windows error code is 0x800700FE
After some research I came across a useful article at http://www.stanford.edu/group/macosxsig/blog/2008/04/ive_been_doing_some_mucking.html
This describes the same problem. It seems that when the extended attribute includes a character like colon (:) the Windows O/S complains and the copy is unsuccessful.
When I use ls -l@ to list files I can see extended attributes on the files do indeed contain : character. See example below:
$ ls -l@ *.TAR
-rw-r--r--@ 1 talsop staff 6723173 20 Apr 08:04 20004566.TAR
com.apple.quarantine 85
com.apple.metadata:kMDItemWhereFroms 339
$
Since I am sure many people use AFP and SMB together for accessing files from Windows and Mac, I wondered how this issue has been solved by others ?
I am using a ReadyNAS 4200 running latest 4.2.19 Radiator.
I am using Active Directory for authentication, but I doubt this is the reason for the issue.
Thanks,
Tim
8 Replies
- Can anybody help me with this?
- Can anybody help us please
- I've got the same issue. The mentioned article had some tips on understanding (but not fixing) the issue: http://www.stanford.edu/group/macosxsig ... cking.html
Some things I may test:- Re-adding the problem file via CIFS instead of AFP from the Mac computer.
- Using SFTP to grab the file instead of using Explorer, like I do currently.
- SFTP worked for sure.
- So, are you suggesting that it is acceptable to be able to save files from a Mac onto ReadyNas and then use ftp to access these files from Windows computers ? Surely it would be better if you could use explorer to access the files on ReadyNas from Windows ?
- I'm not suggesting anything... I only had this problem with one file so far (an ISO). Of course you should expect some issues when trying to integrate things between two different operating systems. That being said, I am not convinced that there's no solution to making it work. For me using FTP is a low-hassle work around but it would be better if we could use explorer & finder with more confidence. Perhaps someone more veteran on the subject will be nice enough to give their two cents and confirm our findings so far..
- Leoj3n, thanks for explaining your earlier comment.
I think the only solution is to update the ReadyNAS with a feature so that it can be configured to remove or ignore extended attributes from files which include special characters like : (colon). The issue occurs on any file (not just .iso or .tar) which has extended attributes that Windows does not like.
Maybe somebody knows of a way to stop Windows complaining when it finds an extended attribute in a file which it is not recognising. It would be much better if Windows ignored this attribute when found instead of stopping the file being accessed. I did some research on this potential solution myself, but was unable to find any information on such a feature, so I assume it isn't available. - You can use "xattr -rc *" in Mac Terminal to clear all extended attributes on shared files.
-r fo recursively, -c to clear all extended attributes.
See more by "man xattr"
another link for your reference
http://stackoverflow.com/questions/4833052/how-do-i-remove-the-extended-attributes-on-a-file-in-mac-osx
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
