similar to: wbinfo -K no such user

I'm struggling with a permission problem on a samba server that is configured to resolve unix uids and gids via nss using sssd. This mostly works. The windows side sees files as being owned by SID=S-1-22-<unix uid of user> and the group is SID=S-1-22-<unix gid of group> This all works fine for files owned by the windows user, or files that are world readable, but fails for

Dear List! I have the problem described at http://lists.samba.org/archive/samba/2008-February/138451.html It is materialized after an upgrade of samba/winbind. Everything was working before. I could not find the solution neither on the net, nor from people originally having the problem, so here I am. This problem is a showstopper for me. (I can login by changing pam_winbind to pam_krb5, but this

Hi! The problem lies in the "winbind separator" settings. If I use winbind separator = \\ everything goes well. I believe this is due to a bug. As I don't want to register to yet another bugzilla, please someone issue the report there. Explanation: winbindd_raw_kerberos_login uses parse_domain_user to generate the kerberos principal from state->request.data.auth.user at this

Andrew, Thanks for the pointers about looking into the ldap client libs. I think I've found a situation where tls connections to the AD server on port 389 have trouble. I've added the CA cert to ldap.conf, and to the ca_root_nss file on this system. First what works: 1. ldapsearch commands with -Z to force use of tls (configured in /usr/local/etc/ldap.conf) 2. ssl connections with

On 20/04/16 22:24, Gerben Roest wrote: > I have set up a samba 4.4.2 AD server, and it works fine for its Windows > and Linux clients. Only the server itself behaves peculiar: > > Linux accounts show up as DOMAIN\username (in prompt and with whoami), > on all Linux clients the user accounts are normal (just their username), > > and only on the server "wbinfo -K

I have set up a samba 4.4.2 AD server, and it works fine for its Windows and Linux clients. Only the server itself behaves peculiar: Linux accounts show up as DOMAIN\username (in prompt and with whoami), on all Linux clients the user accounts are normal (just their username), and only on the server "wbinfo -K username" fails. On the clients it works. The server complains about that:

Hi All, I tried multiple topics and did some further analyzing regarding this. I found that described error below only appears if I restart the device when connecting from "online" to "offline". If I keep my device running winbind caches the users correctly. Based this I found the following bug report: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1165461 There the

Hello, I'm trying to connect my Debian 4 samba box to my Windows 2003Server Active Directory. I successfully joined the domain, with net ads join. Wireshark captures a lot of packets going over the wire, and I get the message "joined the domain successfully". In my AD, under 'computers', the samba box appeared. So that all works. Asking a kerberos ticket for a user with

Hello All, I am at the switch from sssd to winbind based samba domain members (Debian 9 stretch). I am using Samba 4.10.2 packages from Louis ( http://apt.van-belle.nl/ ) and rid backend for idmap. *My problem:* I am able to logon to my domain members using winbind_pam as long as my client is connected to a network where a domain controller is reachable. As soon as I shutdown and connect a

Hello! Please help! I have been googling and experimenting for the past few days, but I can't get user authentications to work with my AD domain. Fedora Core 2 running Samba 3.0.7-2.FC2 Windows Server 2003 Standard Edition After much fuss, I was able to get it to join the domain (had to disable client signing). "wbinfo -u" and "wbinfo -g" both work fine, and I can see

Hai,   Im setting up a new proxy and im testing a bit around. Goal is, get everyting working with minimal changes to the system.   Setup: Debian 8 with NFS nfsv3 and v4 (krb) automounts,  winbind 4.5.3 , squid 3.5.24 (with ssl support) Which is basicly a copy of my other proxy but a new install with more systemd and less packages used.   Working: -          ssh logins with AD users.

I have 20+ freebsd 10 samba 4 servers joined to our local microsoft active directory. At the moment things work well enough. However the windows administrator wants to tighten his AD security by requiring tls encrypted ldap. When I add: ldap ssl = start_tls ldap ssl ads = yes cldap port = 389 the net ads commands fail: net ads testjoin Failed to issue the StartTLS instruction: Connect error

It seems I have the same problem that was discussed briefly earlier on this list in a mail from Kris Kaido. I didn't see any solution, so I'm wondering if it's considered a bug that needs to be fixed or simply a configuration error. To be more specifc; I have joined a Win2008R2 Forest/Domain AD with my server running RHEL5.4 - samba-3.0.33-3.14.el5 without problems. I can view

Am 21.07.2016 um 20:56 schrieb Russell R Poyner: > Jeremy, > > I think this is exactly a complex interaction between FreeBSD and > Samba. Best guess would be some system call that is fast in linux but > slow in FreeBSD holding things back. > > Russ > > On 07/21/2016 01:00 PM, Jeremy Allison wrote: >> On Thu, Jul 21, 2016 at 12:23:01PM -0500, Russell R Poyner

On 05/11/2019 19:06, Vex Mage wrote: > > > > > Collected config ?--- 2019-11-05-10:26 ----------- > > Hostname: samba4 > DNS Domain: sambaad.engr.ucsb.edu <http://sambaad.engr.ucsb.edu> > FQDN: samba4.sambaad.engr.ucsb.edu <http://samba4.sambaad.engr.ucsb.edu> > ipaddress: 128.111.27.62 192.168.0.235 > > ----------- > > Kerberos SRV

On Thu, Jul 21, 2016 at 10:50:16PM +0200, Achim Gottinger wrote: > > > Am 21.07.2016 um 20:56 schrieb Russell R Poyner: > >Jeremy, > > > >I think this is exactly a complex interaction between FreeBSD and > >Samba. Best guess would be some system call that is fast in linux > >but slow in FreeBSD holding things back. > > > >Russ > > >

Guys, I'm running out of hair to pull out ;). Can anyone out there say that this does work?? To me this is looking like a bug and I'm not sure whether it's the sieve plugin or the dovecot deliver program. I have also had no luck the the "reject" sending any reply back to the sender. My setup: OS: Solaris 10 sparc platform postfix: 2.5.2 dovecot: 1.1.2 sieve plugin: 1.1.5

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry to bring this up again. I have now configured my test server to pass all email messages off to our central campus email filter gateway. This gateway scans all email traffic for viruses/spam before being delivered to any local mail servers. Once I did this my auto vacation replies are getting canned due to the fact the from header line is empty

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm at a loss here. Details of my setup: OS: Solaris 10 gcc version: 3.4.3 postfix version 2.5.2 dovecot version 1.1.2 dovecot sieve version 1.1.5 How I installed: Postfix: make makefiles CCARGS='-DUSE_SASL_AUTH \-DDEF_SERVER_SASL_TYPE=\"dovecot\" -DUSE_TLS -I/opt/csw/include' \AUXLIBS="-R/opt/csw/lib -L/opt/csw/lib

I have 2 samba servers. One with centos5+samba 3.033 that has been in service for a few years now. I have installed a centos6+samba 3.6.9. I followed the how-to I did with the first one, copied over the krb5.conf and smb.conf from the working server and all seemed to go well. It is a member server of a window AD. We have 2 DC's that are part of the same forest: SEAS and SEAS-S. I