search for: mdavidson

Hello all, I have a functional samba/windind file server (SLES 10) thats a member server of an Active Directory domain. I'm able to successfully resolve user and group accounts from AD. The problem I'm having is samba isn't creating home directories automatically when I try to map to a AD user share from Win XP. What I am able to do is, when I ssh into the machine with an AD user,

...uot;Graphics" access to the share and to force group ownership on files that are created through the share to be "Graphics". Here is some command output (The domain name is MWO): wbinfo -g | grep Graphics MWO+Graphics getent group | grep Graphics MWO+Graphics:x:10029:MWO+mdavidson wbinfo -G 10029 S-1-5-21-1830939736-2914305965-1243072980-1232 The first command tells me that Winbind know the group is there. The second tells me that I'm a member of the group. The third tells me that the Unix GID translates to an NT ID properly. The problem happens when I att...

I have read many opinions on what character to use for the winbind separator. Many people urge changing the default to '+'. According to testparm: 'winbind separator = +' might cause problems with group membership. The man page for smb.conf says this on the subject: "Please note that setting [winbind separator] to + causes problems with group membership at least

I recently had a problem with Winbind where new Active Directory user accounts could not access the list of shares on a particular Samba server. "wbinfo -u" showed that the users did exist, but they were not appearing in "getent passwd" results. "/var/log/samba/winbind.log" showed the following error (with Winbind error logging set to either 2 or 3): idmap Fatal

Happy Holidays for those of you celebrating holidays this time of year :-) I am having difficulty with a newly joined Samba server, version 3.0.28-1 on CENT OS 5.1. Winbind doesn't seem to be picking up changes to group membership. For instance, the example commands below show a discrepancy between wbinfo and getent group (dom\user1 does, in fact, belong to dom\group, aka 10016) #

Here is the solution to a problem that I recently had. (I almost emailed this list asking for help, but then a co-worker clued me into the solution.) Server: a new Cent OS 5.1 install with Samba 3.0.28 that is joined to a Win 2003 domain. Client: Win XP Pro SP3, member of same domain A user was attempting to save an Excel file which had 644 perms and was owned by her. As soon as she