Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A collection of tips on accessing Windows file servers' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A collection of tips on accessing Windows file servers
Authored by: tjfarrell on Jul 29, '04 06:05:34PM

Thanks for this. I have two related questions.

First - what does tip 8 do for us? What do we lose by not doing it?

Second. I often get error messages such as

"The Finder cannot complete the operation because some data in
"smb://user@server" could not be read or written (Error code -36). "

Does anybody know if this error code is a mac error code or an error code from the server. If from the SMB server, where do I find the error code definitions.

Thanks.

---
--
T. Farrell



[ Reply to This | # ]
A collection of tips on accessing Windows file servers
Authored by: sapridyne on Jul 29, '04 09:06:27PM

Most likely the share name you are trying to access is longer than 12 characters. The 12 character limit is something that was supposedly fixed in SMB 3.0, but it seems to still be an issue. Check that out.



[ Reply to This | # ]
A collection of tips on accessing Windows file servers
Authored by: mael on Jul 30, '04 11:19:59AM
That usually happens when I try to reconnect to a share that I've been using with no troubles whatsoever before.
It turned out that the .DS_Store-files Mac OS X leaves lying around everywhere seem to cause this. Deleting them causes no harm but makes the share accessible again.

To do so, we are using a command that runs on the windows box, searching and deleting all .DS_Store-files. No need for a script here..

cd driveletter: like: cd f:
del /f /s .ds_store

Maybe it helps.

[ Reply to This | # ]

A collection of tips on accessing Windows file servers
Authored by: Fillman on Aug 05, '04 07:09:33PM

I'm guessing at the cause of this but I think it refers to multiple mount points for the shares. If you type in the ip address of the DNS server that you want to mount as opposed to the domain name you should get the list of shares succesfully each time.



[ Reply to This | # ]
A collection of tips on accessing Windows file servers
Authored by: intensity on Aug 09, '04 06:43:56PM

I ran into this problem today (code -36), and after 5 hours I was able to figure out what the problem was.

My w2k domain password had expired. This was problem #1. Loging into a windows machine I was able to successfully change the password. Trying to login again from my mac produced the same error, even though I could login into a different server in the same domain, which narrowed it down to something linking the two machines. Eventually I went into the Keychain manager and deleted all of the links for this server, and then I was able to successfully login.

Hope this helps!



[ Reply to This | # ]