I've been trying to follow the other thread about CIFS and permissions mapping. But not really understanding it.
I'm from linux backgroud and have never really worked with windows permissions beyond making sure any windows machines had a username matching a user on the linux server. And setting windows share dialog so that username has full control of the share. I've tried to keep it as simple as possible, never resorting to ACL's, at least not knowingly. Now inserting an opensol zfs server (build 110) into my lan as Backup host, and run into problems I don't expect. I took someones advice on osol lists and have set the zfs shares to be offered to windows clients with: chmod A=everyone@:full_set:fd:allow pool/filesystem And hoped it would just work from there... but still find in some cases (where I'm not really able to identify all the variables) where from a windows client, I'm unable to delete files or create directories. I attempted to setup the windows application EMC Retrospect (a backup application) to write to certain osol server shares. It worked fine... but then I find after a reboot of osol server the attempts from Retrospect fail. I find even manual connection from windows host to fail too. So at this point I'm finding a reliable connection of windows backup application with Osol server to be unattainable. I'm hoping someone can tell me if I SHOULD be fine with this setup. Then I can attempt to debug it, but it would be nice to know that it SHOULD work ok. Osol server: Osol share set chmod A=everyone@:full_set:fd:allow pool/filesystem Share is owned by user reader chown -R reader:wheel /path/share Of course sharesmb is turned on and smb/server is running. Windows host: Windows based Retrospect backup app is given the UNC address of Osol share and is able to connect and write to it. Creating a few directories and backup files. The windows user running Retrospect has an admin account and that username matches the username who owns the share on OSOL server. All appears to be working. Then a reboot of Osol server and eventually a reboot of windows client occur... after the Osol reboot the windows client in unable to connect to the previously working share. A reboot of the windows client doesn't change that fact. A final note is that through out my experimenting with osol as zfs server on lan...( a few wks now) the Osol host or the shares offered by it have never appeared in the windows applet `Network Places'. All other windows hosts and linux hosts do appear there. This means manually entering UNC addresses to connect... not all windows based applications expect to use UNC addressing... at least not in the UI dialog boxes, although they are probably using UNC internally. So apparently something about the way the ZFS server behaves in the network makes it invisible in `Network Places'. I wonder if that fact is pointing out some underlying problem which may be related to the unreliable connections I experience. _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
