• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Snow Leopard - Big Problems With Windows Fileshares

Seeruk

Senior member
I am posting this on a few forums as I am at my wits end trying to resolve this issue. It seems to effect a lot of people and there are posts on the apple forums, but no solution anywhere. So I am posting this on a few forums where I know the knowledge level is higher 🙂

The basic problem is this - I am able to write to Windows SMB mounted shares but not READ. I can create directories on the share, I can copy files from my mac to the share, and I can happily browse the share .... but not read/execute files!

For example, I want to use a firefox.dmg file on my home server (running WHS). The server is called bigbox and the path to the file is Software/OSX/firefox3.07.dmg

See the screenshot here which shows all the permissions at every level and I have read and write everywhere (As I should because I am connecting as bigbox\administrator)

http://erzz.com/downloads/errorcode36.jpg

If I try to execute the file directly of the share I get the input/output error (also included in the screenshot), if I try to copy the file from the share to my mac I get the error code 36 (also included in the screenshot) and if I try and copy via terminal I get "cp: Firefox 3.0.7.dmg: Input/output error"

Now to add some further mystery I WAS able to use these shares just fine with a fresh install of 10a432. I know this because I installed most of the software on the system from this same share. Thus one of the two(?) updates since could be the culprit?

Seriously, this is about the 15th issue I have spent many hours on already with Snow Leopard..... whatever happened to 'Just Works' ???
 
Actually I am back here to say (rather embarrassingly 🙂 ) that it was in fact that the external disk I have attached to the WHS was not seated quite correctly. I only worked this out because I wanted to test the files locally on the WHS. So I remote desktop'd in and found I couldnt access them there either *blush*

Strange as the whole setup has been sat there in the workroom for 18 months untouched ...there must have been an earth tremor or something to shake it loose!

Still doesnt explain the dozens of people complaining of the exact same symptoms in the apple networking forum.... but my issue is resolved at least
 
Back
Top