Hot answers tagged

2

Place the .bash_profile file in /etc/skel/. It's basically a template directory for new user profiles. Anything in there gets copied into $HOME when a new user is created and they have a $HOME dir. It's similar to a default profile in Windows. To use the same file for remote and local users, look for a variable that only remote users have set and include ...


2

You can set defaults for the home directory and login shell in the [global] section of the smb.conf configuration file: template shell = /bin/sh template homedir = /home/%ACCOUNTNAME% Note that it is %ACCOUNTNAME% and not %U as was the case with Samba 3. Similarly, it is %WORKGROUP% instead of %D. I also discovered that changes to these values are not ...


2

Winbind/Samba stores the Windows SID ids in a tdb (simple LDAP database) and creates a key pair that matches the translated sid-2-uid. If a user on the Linux side doesn't already exist, it makes up a unique UID and stores it in the tdb. If a user exists and 'file' (or ldap) comes before Winbind in nsswitch.conf then it will use that matched users local UID ...


1

Only Samba 4.8.x+ supports such trust. Only thing I am aware that you need to do is to configure idmap for the trusted domain in the [global] section of your smb.conf : idmap config <trusted_domain> : backend = rid idmap config <trusted_domain> : range = ?????- ????? make sure the range doesn't overlap with the range you currently defined for ...


1

Undo all of your changes and delete the computer account from AD. Remove the winbind package. Install a suitable selection of packages. On Debian-based systems you can use apt-get install samba smbclient sssd realmd dnsutils policykit-1 packagekit sssd-tools sssd libnss-sss libpam-sss adcli. Don't worry at this point if sssd fails to start. It needs to be ...


1

You haven't made it clear what version of RHEL you're using. I will assume you are using a supported version (6.8 or 7.3). First thing's first, winbind does not support password changes, at least not natively. You can maybe make a pam configuration change to assist in this, but you may run into the dreaded The change of the authentication token failed error....


1

In my case I've found that I can add an entry to /etc/group that masks the Active Directory entry. (This might not be the correct solution but in my situation it works). Here is what I would add for your example, where getent group 67uts-mq-admins returns 67uts-mq-admins:x:57376: mqm:x:57376: You may be able to run the command addgroup --gid 57376 mqm or ...


1

So, as it turns out, winbind's cache was stale. I'm not sure how to set that to refresh more often, which is what I would prefer for a solution, but I found that the following was effective in fixing the issue: Note: This is a CentOS 5.x system. Adjust as necessary for your OS. /sbin/service winbind stop /sbin/service smb stop /usr/bin/net cache flush /bin/...


Only top voted, non community-wiki answers of a minimum length are eligible