Randall
08-21-2007, 04:50 PM
I have yet another Windows/Mac conundrum I'm wrestling with. But I'll simplify it a bit in hopes that someone will know what's going on.
First we'll try to sidestep the Mac angle by looking at it as a generic Samba thing. It also involves VBScript, but we'll just ignore that. :rasberry:
Distilled question: Why would a subdirectory of a Samba share be inaccessible (under certain conditions) when the root is not, even when the UNIX permissions on both look exactly the same?
Specifically, I have a share named "Randall" and a subdir called "temp." The share is mapped as drive M: on the Windows side. I have a script that needs to copy a file to the subdir.
I can copy it to M:, but not to M:\temp or even \\MacBook-Pro\Randall (with or without the "temp"). The error I get is a generic "Permission denied."
I have workarounds for this -- map the subdir itself to a drive letter, or use a DOS batch script (which handles all of the above variations just fine) instead of VBScript. But I'm hoping to learn something about Samba from all of this ... unless it's just a weird Windows quirk.
Any clues?
Randall
First we'll try to sidestep the Mac angle by looking at it as a generic Samba thing. It also involves VBScript, but we'll just ignore that. :rasberry:
Distilled question: Why would a subdirectory of a Samba share be inaccessible (under certain conditions) when the root is not, even when the UNIX permissions on both look exactly the same?
Specifically, I have a share named "Randall" and a subdir called "temp." The share is mapped as drive M: on the Windows side. I have a script that needs to copy a file to the subdir.
I can copy it to M:, but not to M:\temp or even \\MacBook-Pro\Randall (with or without the "temp"). The error I get is a generic "Permission denied."
I have workarounds for this -- map the subdir itself to a drive letter, or use a DOS batch script (which handles all of the above variations just fine) instead of VBScript. But I'm hoping to learn something about Samba from all of this ... unless it's just a weird Windows quirk.
Any clues?
Randall