Error 36 OSX10.4.11

[vudewjoe]

Hi, Currently have a mixed mac / PC environment and one of our users is trying to connect to server via smb://xxxxx/xxxx and getting - The Finder cannot complete the operation because some of the data in smb://........ could not be read or written. (Error code -36).
in console it shows the following error
mount_smbfs: tree connect failed (extended security lookup2): syserr = No such file or directory
When I go into terminal and use
smbclient //xxxx/xxx -W domain -U username
it connects fine
If I sign into my account I can get to it just fine, but he cannot.

I tried unbinding and then rebinding the machine and it changed to error 43 instead of error 36. I then went to Finder > go > recent folders and selected the folder we were trying to get to and it opened fine, He is currently using this as a workaround but this is contingent on it being in the recent folders pane. Can anyone help me find a fix for this before i have to simply reinstall the OS? Thanks.

Joe

 

[Satcomer]

Is this affected Mac on a Windows Domain of some kind? If so the open System Preferences->Network, Advanced button and make sure the WINS has the domain WINS server listed in there. Plus make sure the Mac is using the same Time Server Domain the Domain is using.

Also look threw the older thread [HOW TO] Bind Leopard to Active Directory to see if anything there helps.

Lastly try to Reset Your PRAM on the affected machine and bookmark the site Macwindows.com and the subset of Integrating Macs and Active Directory: Tiger and Earlier.

 

[Giaguara]

Error -36 is an I/O error, and you've found the same 'feature' of Finder that I was fighting with and getting frustrated with for years.

Yep, for dealing with smb Finder sucks, and it sucks even more for the error -36 when Terminal works for the same task and the same environment.

Here's the history of my fight (and a bunch of things to try)
http://macosx.com/forums/mac-os-x-s...mb-error-36-always-finder-terminal-works.html
https://discussions.apple.com/message/5368147?messageID=5368147#5368147?messageID=5368147
(and a few other links, but I can't find most of my old bookmarks since they ruined Delicious with the last 'upgrade').

Essentially... you could
- try the nsmb (may not make any difference)
- trust the users with Terminal for making the smb connection
- in case of not trusting the users with Terminal for that (and for most users I would not trust them with Terminal), perhaps... well, use Fusion or Parallels and give the users e.g. an Ubuntu virtual machine. An unnecessarily complicated setup to do the task, but at least the equivalent fo connecting via Finder/Explorer type interface works, and so does drag and drop.
- upgrade the OS to 10.7 and hope it fixes the issue (or finds a fresher workaround)

Reinstalling Mac OS X won't resolve the problem. I had the same issue with every single Mac where I worked, so it was from 10.4 to 10.6 and with any type of user or installation. (Un?)fortunately I don't have the same environment to test whether the same hiccup happens still with 10.7.

One of the additional problems my setup had was that one of the share points had a hyphen - another vintage Finder issue that one would hope to have been resolved by now (the original KB it was from has since been set to invisible, or the URL has changed and they forgot to change the URL or something else).

Macwindows is another site that lists a lot of variations to try. Hopefully one of those could solve it for you, otherwise it'll need to be one of the workarounds.