Previous 1 8 9 10 11 12 Next 199 Replies Latest reply: Apr 8, 2010 8:35 PM by Robert Bosch Go to original post
  • gswd Level 1 Level 1 (0 points)
    I don't think it is dead. And many have not found fixes or work arounds. For myself, I have started using FTP to move files to and from my NAS device, but that is not the same as being able to access them as a regular drive like I was with 10.4.
  • Luke Carbis Level 1 Level 1 (0 points)
    Yeah, I am still having the same problems. One guy one page 9 said that Apple said they would address the issue in 10.6.3, so at the moment I'm just hanging out for that.
  • Steve1812 Level 1 Level 1 (0 points)
    Imac 2008 version 2.6Ghz etc.

    Same error code - retrieved a FOLDER full of wav files and tried to drag/drop in to a USB stick on the desktop. Code 36 comes up.

    Solution was to drag and drop the individual files within the folder - no problem. But why...

    Steve1812
  • needsomeihelp Level 1 Level 1 (95 points)
    Oh wow...I thought I was the only one with this problem..when is 10.6.3 coming out?
  • dstark Level 1 Level 1 (0 points)
    The problem is still there and I wish Apple would fix it. I have a 100gb iPhoto library that I back up to my OS X 10.5.8 server and never had a problem until I upgraded to 10.6.

    I have always copied the file off an external hard to my server using AFP and have never had a problem. I have checked all permissions, verified hard drives on both the client and the server and everything checks fine. I even did a clean install of 10.6 and all the patches and upgrades and still had the same problem. I then go to another machine still running 10.5.8 and copy that same file with no problems.

    What gives Apple?!
  • CarCode Level 1 Level 1 (0 points)
    Yes, the problem is since I switched to Snow Leopard.
    Copying in both directions to the NAS works however.
    But when opening a file with Finder - say with PreView - the file does not open.
    Doing the same with muCommander then the file opens, e.g. a picture file shows up with PreView. Finder however does not launch the associated app (err -36).
    Looking in the logs I see:
    "smb_maperr32: no direct map for 32 bit server error (0x0000161)"

    This happens only with the NAS but not with any other Windows computer in my smb network. I have searched over and over the Xcode docs but nothing found about smb_maperr32.
  • satcomer Level 4 Level 4 (1,110 points)
    I have seen a possible fix (for some situations) to delete all the .DSStore hidden files that Leopard had put on the NAS device. Then prevent any of those .DSStore files from writing to the NAS drive by using the freeware TinkerTool to stop those files ever being written by OS X. Some users have said this drastically speeds up SMB sharing.
  • CarCode Level 1 Level 1 (0 points)
    The NAS without any .DSStore file was already tested, but shows same behavior:
    Launching a NAS file with Finder fires up error -36 also.
  • gordon28 Level 1 Level 1 (0 points)
    Same problem here...I bought a Time Capsule, completed a full backup of my mbp (Leopard) and then completed an erase and install of Snow Leopard. Now I can't restore any files from my backup. What a kick in the stomach.

    For example:

    The Finder can’t complete the operation because some data in “03 What's Up.mp3” can’t be read or written.
    (Error code -36)

    Thanks, Apple.
  • man overboard Level 1 Level 1 (0 points)
    Same problem here - Cannot write to NAS drive, reads are very slow.

    Some sign that there is an Apple support team would be nice...
  • PierreJJA Level 1 Level 1 (0 points)
    Hi Gordon,

    This sounds familiar:My iMac had a memory problem and I was advised not to use the backup to restore executables. So, I erased and installed a clean Snow Leopard and next I wanted to restore data files. Not possible since I had no rights.

    What I did was use the same user name and password and everything but in Unix a new user is generated with a new ID and that makes that you can't read your old backed up files.

    The solution is simple: make a root account and login as root and now you can read all your old stuff back. You have to do this with Finder though: go to your TC, double click on your TC disk and right-click on your sparsebundle and use "show package contents". A bit cumbersome but it worked for me. And in a way I understand what happens, it is a Unix security issue that in the end we don't want to miss.

    I hope it works for you.

    Pierre
  • William Kucharski Level 6 Level 6 (14,890 points)
    man overboard wrote:
    Same problem here - Cannot write to NAS drive, reads are very slow.

    Some sign that there is an Apple support team would be nice...


    This is a user to user forum; Apple support does not officially read and does not reply on these boards.

    If you want direct technical support or to report a bug, call AppleCare.
  • plq Level 1 Level 1 (5 points)
    Yes, definitely.

    In early December a downloaded DMG file was copied on my system (iMac 27 inch) to a network RAID drive (Netgear) over SMB. Bad idea. The SMB file protocol was knocked out, or had its capacity reduced to between 10 and 1% percent of previous values.

    The workaround was to use NFS instead, although the character issues are troublesome (NFS differentiates between upper and lower case).

    The late in December another problem appeared as I started backup and file sync procedures again. They started to hang because completely unrelated files were absent.

    I have subsequently found one such file in the /Volumes directory, where it is impossible to delete. The file is designated as a directory (zero length), permissions are such that the file can not be discarded, not even as a sudo user.

    For more on the subject, see the posting at:
    http://discussions.apple.com/thread.jspa?threadID=2284881&tstart=210
    here on this forum.

    It is my belief that something creates this directory entry when the machine is booted.

    Applecare has the problem, but have yet to come up with a solution.

    Any ideas on how to remove cause?

    BR,

    peter
  • gswd Level 1 Level 1 (0 points)
    If Apple does not "officially" read and respond on these boards, then why is it on the Apple website under the Support category? And even so, this problem was opened up on this "discussion board" more than 3 months ago. Various people have said that they have taken it to the Apple support team, and have discussed the issue with them. It was reported that it was supposed to be fixed in 10.6.2, but wasn't. And I have heard that it is supposed to be addressed in 10.6.3, but who knows when that is coming out.

    In today's world of social networking, every community forum, especially those on your own site, should be monitored and issues addressed appropriately. It could be from someone in the PR department letting us know that the issue has been entered into the bug system and even providing us with some tracking number or something.

    Apple has the reputation of being elitist, and this is one of the reasons why.

    Message was edited by: gswd
  • William Kucharski Level 6 Level 6 (14,890 points)
    gswd wrote:
    If Apple does not "officially" read and respond on these boards, then why is it on the Apple website under the Support category?


    Because Apple provides these forums as a way for fellow users to help other users troubleshoot Apple issues, as for 99% of issues there's usually someone here who knows how to solve a particular problem or how to work around it.

    If you want help directly from Apple, call AppleCare or visit the Genius Bar at your local Apple Store.

    In today's world of social networking, every community forum, especially those on your own site, should be monitored and issues addressed appropriately. It could be from someone in the PR department letting us know that the issue has been entered into the bug system and even providing us with some tracking number or something.


    Apple does not do that here, and these forums have never been meant for that purpose, no matter what you think Apple should be doing.

    Have you called AppleCare on this issue? Have others who have been experiencing it?

    If Apple doesn't have detailed technical knowledge of what the circumstances are under which the problem occurs, they can't fix it, and that's the interaction contacting AppleCare provides. You can be the person that provides Apple with the information they need to solve the problem and may, in fact, be asked to interact with Apple's engineers to do so.

    If you want to enter things into Apple's bug system, feel free - anyone can after setting up a free ADC online account:

    http://developer.apple.com/products/membership.html
    http://bugreport.apple.com
Previous 1 8 9 10 11 12 Next