Home Forums OS X Server and Client Discussion Misc. 10.5.x AD bound clients unable to copy files to windows smb shares

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #377494
    kennyj
    Participant

    Hello,

    I have come across an issue in which my 10.5.x machines that are bound to AD cannot successfully upload files to a windows file server using smb. It seems to be a server-related issue because there are certain servers where the problem is reproducible from any AD bound mac.

    Problem description:
    An AD user logs into a mac that is bound to Active Directory. They mount a smb share on thier local windows server for which they have access. The user drags a file to the share and receives a message “You may need to enter the name and password for an administrator on this computer to change the item named ‘file.whatever’.” The file then shows up on the share, however it is zero kb in size.

    Glancing at the system.log, I find the error “kernel[0] smbfs_composeacl:smbfs_setattr+1 13, ignored”. If I try to copy using cp or ditto at the command line I recieve this message: “cp Desktop/Picture\ 1.png /Volumes/sdgpublic/
    cp: Desktop/Picture 1.png: could not copy extended attributes to /Volumes/sdgpublic/Picture 1.png: Operation not permitted”

    I can reproduce this from any Active Directory bound mac. I’m wondering if this may have anything to do with the UUID that is created by Mac OS X. I have seen posts regarding this problem occuring on local volumes and the suggestion was to change the UUID. This did not help in this situation.

    If the user logs in as a local user and mounts the same share using thier AD account… files transfer just fine. So I have a work-around, however it is not a solution. As I said, this seems to happen with two windows file servers.

    Thank you,
    Ken

    #377676
    kennyj
    Participant

    I’m still seeing this issue happen…

    I’ve tested different smb packet signing and encryption settings using dsconfigad… no dice. I also thought… hmmm, is the kerberos ticket bad or not being genereated… nope, everything looks fine there.

    Any suggestions or others having similar issues? I have been unable to have the windows server team here find any difference between working shares and non-working shares.

    Thank you,
    Ken

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Comments are closed