similar to: Samba 3.0.5 and Winbind

G'day, We are having problems when connecting to our Solaris 8 server Zeus from our Windows 2000 Terminal Servers. We are running Samba 2.2.8a on the unix box and are finding that from time to time people are having difficulty opening files from shares on this server. They also have difficulty mapping network drives. It reports errors such are "file doesn't exist". However, we

I have just struggled to implement a Samba Domain Server, and have some remaining issues. I have a Samba PDC using tdbsam, managing a domain called RHEA. I have (finally) configured a new Samba Domain Server (AUREUS) using winbind and idmap_rid. When I am logged in to RHEA as user GMCH I can access a TMP share on AUREUS (at last). Running 'getent passwd' I get (inter alia):

Hello, > > I'm having a bizarre problem doing authentication via > winbind against a > > Windows 2003 server. > [...etc...] I got almost the same problem authenticating to a Samba 3.0.20 server in a Windows 2003 Domain in mixed mode (updated from a Windows 2000 Domain). Following actions succeed: > ALL of the wbinfo > functions seem > to work correctly: wbinfo

Hi all, I have a small issue with my current Samba install. I have installed 3.2.7, and joined it to my AD domain with security=ADS, I have also built up a Idmap backend using LDAP. It all appeared at first to work flawlessly. I was doing some bits the other day and wanted to check the group listings, so I ran "getent group" - This sat at the point after the local users for 5

hi all ! I have compiled Samba 2.2.2 for Solaris 7 ( Solaris 8 also ) but found out that the "nss_winbind" support is available in source-code, but not after compilation. The neccessary entries in the Makefile after "configre" are missing !! Why ? I have got it to run and it works fine with a small amout of groups. But deploying this samba/winbind version to a Windows

Hi David, I experienced this issue as well, it's currently a limitation of Samba 4.2.2. Samba 4.2.2 DCs do not support pulling home directories and login shells from AD via rfc2307. I solved this issue with the "template homedir" and "template shell" directives. You lose some flexibility but at least it works. Excerpt from my DC smb.conf: winbind nss info =

hi, today i experience a very crazy behaviour: 1) yesterday my winbindd crashed (s. log.crash) (status: "dead") 2) restarted winbind and saw that some files have no owner (just the uidNumber) 3) getent passwd, wbinfo -u shows me all users (authenticating agains Windows PDC) 4) i'm using nsswitch (passwd: files winbind, group: files winbind) e.g. (getent passwd) .... (snip)

Hey all I'm currently trying to use squid and samba/winbind to filter internet access based on groups in a windows 2000 active directory domain. Im running Mandrake 10.1 Community and samba 3.0.10 installed from rpm. Following the directions in the samba manual for setting up winbind I have: - configured nsswitch.conf - checked to see if the libnss_winbind.so library is there - checked

Hey all I'm currently trying to use squid and winbind to filter internet access based on groups in a windows 2000 active directory domain. Im running Mandrake 10.1 Community and samba 3.0.10 installed from rpm. Following the directions in the samba manual for setting up winbind I have: - configured nsswitch.conf - checked to see if the libnss_winbind.so library is there - checked to see if

Hi! I have a setup with several Linux machines running samba-3.0.22-10.1.17 (from SuSE 10 OSS), authenticating against an AD. Since one of the machines is exporting an NFS share mounted by the rest of the machines, I need SID <-> uid/gid mapping to be shared between all Linux machines, which led me into using an OpenLDAP server as idmap backend. My smb.conf is found at the end of this mail.

This is my first post to this list. The domain names etc have been changed slightly in the examples below, but you should get the idea. For a long time now (since 3.0.2a?), I have been using the samba 3.0.x series at one of our client sites. The Linux server is joined to a Win2k3 Active Directory. All users are created in the ADS, and the Linux server is able to authenticate them, etc. I

About a month ago, I setup a Windows 2000 native-mode domain, and had a couple of Linux machines join the active directory. I followed the steps outlined in the Samba 3.0 docs regarding winbind/PAM/NSS. The machines joined the domain fine, and 'wbinfo -t', as well as 'wbinfo -u/-g' and 'getent passwd/group' return expected results. Connecting from other Windows clients

I have a problem with the Winbind setup authenticating Active Directory Users. I have setup Fedora Core2 with the minimal setup option These are the Fedora RPM's that I have installed manually. openldap-2.1.29-1 openldap-devel-2.1.29-1 krb5-libs-1.3.3-1 krb5-devel-1.3.3-1 krb5-workstation-1.3.3-1 pam_smb-1.1.7-3.1 pam-devel-0.77-40 pam-0.77-40 pam_krb5-2.0.10-1

G'day All, I'm running Centos 7, Samba4.2.2. (SSSD is NOT running (not even installed on the Member Server)) /etc/nsswitch on both: passwd: files winbind group: files winbind the winbind libs have been sym-linked as described in the tiki. All seems to be working well on both the DC and Member Server. Both smb.fonfs have: idmap config *:backend = tdb idmap

On Sun, 30 Sep 2018 23:25:48 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > > AD server CentOS 7-1804, Samba 4.9.1 compiled from source, only used > as AD server, with netlogon and sysvol, just like any Windows AD > server > > AD member server CentOS 7-1804, Samba 4.7.1 installed from CentOS > repositories, intended for use as a

Hi David, > Just to clarify, is it only the DC that doesn't return desired values of HomeDirectory and Shell? Yes, it is only the DC that doesn't pull HomeDirectory and Shell via rfc2307. (when using winbindd) Member servers with winbindd do pull the desired values without problems, I have it setup like this and it works without problems. I have only two ideas to solve your problem:

I'm having a bizarre problem doing authentication via winbind against a Windows 2003 server. Aside from changing the hostname information, etc. as appropriate for krb5.conf and smb.conf, the configuration I'm using is one that I copied from another server that is successfully authenticating against ads. The two systems I'm having trouble with are running Suse Linux Enterprise

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, currently I'm testing samba authenticating against ADS. Samba is joined to that domain, getent passwd and wbinfo -u works as expected, but when I try to ssh to the samba server with an account in AD it failes. I've turned debug on for pam_winbind.so in /etc/pam.d/system-auth. When I try to connect I get the following in /var/log/secure

Hello folks, I'm getting a problem where winbind incorrectly lists groups for a certain user. I'm using 3.0.27a. >From what I'm seeing, winbind lists another group the user is not in. Doing getent and grepping for the group lists the members correctly though. The commands id and groups return correct listings as well. Any ideas? Thanks in advance, Franz

I have winbind authenticating against a W2K Domain Controller. It works just fine with 2.2.3. After upgrading to 2.2.4 I can no longer authenticate agains a W2K domain account. Everything compiles, installs, and starts successfully Under 2.2.4. wbinfo -u gives a correct list of users, wbinfo -t verifies that the secret is good. Howerver, running 'getent passwd' and 'getent