similar to: getent group fails on member server after upgrade to 3.5.5

Hello all. I'm relatively new to Samba, and haven't been able to track down a solution to this particular problem. I use Samba/Winbind to authenticate FreeBSD machines against a Windows 2003 Active Directory. That all works fine. The problem is that groups in the AD of type "Security Group - Domain Local" are causing winbindd a lot of grief. Every time the winbindd daemon is

I've been messing around with running samba 3.4.14 inside a freebsd jail over the last couple of days, and am running into an odd problem where wbinfo -u and wbinfo -g succeed, but getent passwd fails (insofar that it shows only local users, but none of the domain users). Here's my smb.conf: [global] interfaces =192.168.0.16/32 bind interfaces only =yes security

I have configured winbind on a Linux file server, connecting to a Samba PDC. When I run wbinfo -g, I can see the group "domain users". On the other hand, when I run getent group, I do not see this group. Apart from a few other groups, all groups are visibile in both wbinfo -g and getent group. When running for the first time wbinfo -u, getent passwd and wbinfo -g, I got the results

Hi Igor, I got stuck now. I did my best. I got stuck at the winbind which I suspected is the reason why the domainA_computer cannot map the domain_B user's home directory. 1. What are the settings of your winbind? 2. Do you use only "winbind" in your libnss_ldap or use "ldap" as well? 3. My winbind works with :- (For both sides) wbinfo -t wbinfo -p wbinfo -u wbinfo

Quick question about Samba and Domain Local groups. Ive got a Samba 3.0.7 server (redhat 8) as a domain member of a 2K Domain in native mode. (security = domain). Std Windows group mgmt says: Users are members of Global Groups. Global Groups are members of local groups Local Groups control access to resources. So ive got a Domain Local group I want to use to restrict access to a samba share:

I started my AD-member server with the DC not being present. Afterwards, I executed the "good practice" sequence from the howtos for testing a installation: "testparm ..." "nmblookup -d ..." "nmblookup -M ..." "nmblookup __SAMBA__ ..." "smbclient -L ..." And some domain tests: "net ads testjoin" "net ads lookup"

Hi I am having a lot of trouble getting users from a trusted domain to access shares and files. getent passwd / get group doesn't retrieve domain users or groups, so I can't set permissions for the users or groups from the trusted domain The domain having problems is: Ubuntu 6.06 Server Samba Version 3.0.22 The trusted domain is: Ubuntu 8.04 Server Samba Version 3.0.28a wbinfo -u and

I have a centos 5.6 server that has xen domUs installed on their on logical volumes. These logical volumes contain their own volume groups and again their own logical volumes. I want to access the domU logical volumes and tried this: [root at kr ~]# fdisk -l /dev/VolGroup00/LogVol02 Disk /dev/VolGroup00/LogVol02: 274.8 GB, 274877906944 bytes 255 heads, 63 sectors/track, 33418 cylinders Units =

doublecheck that a pointer is not NULL before dereferencing it. (Coverity CID 121). CVS tag: libXpm-3_5_5 http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.5.tar.gz ae164be364086615dcc12c1f59035b55 libXpm-3.5.5.tar.gz 4c1674e4a7f32dc235ca02712c78cf4be44187c8 libXpm-3.5.5.tar.gz http://xorg.freedesktop.org/releases/individual/lib/libXpm-3.5.5.tar.bz2

Greetings, We don’t normally announce DPMA releases on here but 3.5.5 was just released which resolves a compatibility issue between the latest versions of Asterisk (using PJSIP 2.10) and DPMA. For TCP or TLS traffic it was possible for a crash to occur. It’s recommended to update to 3.5.5. Installs which select DPMA in “make menuselect” will automatically get the latest version or the tarballs

After today's Squeeze upgrade from 3.4.8 to 3.5.5, domain logons were initially broken. I was fortunate to find Thomas Burkholder's workaround from last June, i.e. turn off server signing. Can anyone explain why "server signing = auto" no longer works in 3.5.x? Thanks. Dale http://lists.samba.org/archive/samba/2010-June/156237.html

Just found out that Sun (Oracle) has released supported patches for Solaris 10, to bring Samba from 3.0.37 to 3.5.5 (back in Feb.) http://sparcv9.blogspot.com/2011/02/samba-355-update-for-solaris-10.html?sho wComment=1299265836812#c4735248300290186719 Solaris 10 sparc 119757-19 and 146363-01 Solaris 10 x86 119758-19 and 146364-01 I think this was a big enough upgrade to

I'm trying to add my Solaris 10 server to active directory on Windows 2003 and I keep getting the same error that samba failed to join the DC. I've checked the configuration file under /etc/samba/smb.conf and it's the same as my other server that's working fine. What else could I check to verify my configuration? Thanks, Adrian

Hi, I'm running Debian Squeeze on a few machines that are all authenticating to a pair of Windows 2008 servers. After upgrading to samba 3.5.5 from 3.4.8 idmap has stopped resolving which is preventing user authentication on these boxes. The boxes that have been left at 3.4.8 continue to work fine. On the 3.5.5 boxes wbinfo and net ads show lists of users and groups without issue yet id

So, we're doing a bad thing and re-exporting an NFS file system via Samba. For the most part it's always worked fairly well and we've been cognizant of the various locking scenarios that can come up. Recently, we've run into issues exposing NFS file systems sitting on RHEL6. Our Samba server runs Solaris 10 and the vendor provided Samba daemon (we're currently at 3.5.5 but

I've run into an error when trying to compile libnet/libnet_join.c: cc: "libnet/libnet_join.c", line 111: error 1588: "LDAP_NO_MEMORY" undefined. cc: "libnet/libnet_join.c", line 111: warning 563: Argument #2 is not the correct type. The source below is what triggers it (line 111 is marked): static ADS_STATUS libnet_connect_ads(const char *dns_domain_name,

Release Announcements ===================== These are a security releases in order to address CVE-2010-3069. o CVE-2010-3069: All current released versions of Samba are vulnerable to a buffer overrun vulnerability. The sid_parse() function (and related dom_sid_parse() function in the source4 code) do not correctly check their input lengths when reading a binary representation of

Release Announcements ===================== These are a security releases in order to address CVE-2010-3069. o CVE-2010-3069: All current released versions of Samba are vulnerable to a buffer overrun vulnerability. The sid_parse() function (and related dom_sid_parse() function in the source4 code) do not correctly check their input lengths when reading a binary representation of

All, I'm in the process of migrating a samba server from Solaris 10 (running 3.0.37) to Solaris 11 Express (running 3.5.5). The system is joined to a Win2k3 Active Directory. Migrating the configuration worked fine, the shares are available and everything mostly works as intended. The problem we're having is with the syntax of authentication requests from Windows client machines. On the

Hi, We are running Samba on Solaris 10 cluster as a HA service. There are two nodes in the cluster and Samba versions are 3.5.8 on other node and 3.5.5 on another. Samba build is one that ships with Solaris 10. We are using Sun (Oracle) LDAP for user account data so passwd and group databases related information is retrieved from there. Authentication is done against Windows 2008 AD. This Samba