similar to: winbindd requests failing with NT_STATUS_PIPE_BROKEN

Hello all. I have a Samba 3.5.4 server that we're attempting to join to an existing Windows 2008 ADS. Doing "net ads join" seems to go ok, and a follow up "net -P ads testjoin" says we're OK. However... at this point, doing "wbinfo -u" or "wbinfo -g" returns no data (the programs exit with erro code 0, and no output). Attempting to log into a

Hi All, One day we upgraded client pc's OS from Windows7 to Windows10, Windows10 clients could not access a samba server. When we re-enabled the SMBv1 protocol on Windows10, Windows10 clients still could not access a samba server. After adding the following [global] settings, Windows10 clients could access a samba server at last.

Good morning, Samba list. =) I've been experiencing intermittent winbind failures over the past few weeks. The symptom is that users that haven't connected in a while, and thus aren't in the winbind cache, are unable to connect to any shares. I see a lot of NT_STATUS_PIPE_BROKEN in the logs when the failures occur, like this one from log.winbind: ### [2011/04/26 09:20:54.671225,

Hi~ Samba(Version 4.0.4) run on an embedded system (kernel version: linux 2.6.32) with conf file like this: " [global] workgroup = MYGROUP netbios name = DFTNAS server string = Samba Server security = user log file = /var/log.%m passdb backend = tdbsam [smbshared] comment = Stuff path = /var/smbshared public = no writable = yes printable = no " Everything is OK when I'm

Hi Jay/Samba peeps, Emailing in reference to http://lists.samba.org/archive/samba/2011-April/162277.html I have seen a very similar issue with a similar setup. Users fail to be verified with: getent passwd username Entry in the log at same time is: [2012/01/23 16:58:53.159761, 3] winbindd/winbindd_misc.c:352(winbindd_interface_version) [18510]: request interface version [2012/01/23

I am hoping someone can shed some light on this. We have a setup that is using Active Directory Windows 2008 R2 with 2 domains, A and B. They are across forests, with a one-way trust between the forests. A is the trusted domain, B is the trusting domain. We have a 3.6.9 samba server joined to B's Active Directory. If we try authenticating from our machine in B's domain as a user from A

I have a RedHat 8 box configured as a Samba server using winbind (version 2.2.7 installed from RedHat's rpms.) The server successfully joined my Win2K domain. Everything works great. Users can log in to the RedHat server via ssh using their AD accounts. Users can connect to the shares from their windows machines. All except one. I have one account that has problems. If I restart

Hi We have a few Linux samba servers that authenticate against our Active Directory domain (Small Business Server 2000). I've added a couple of disks to a FreeBSD 6.1 server in our office and I'm trying to achieve the same but not having much luck. I'm new to all this... I'm not our network admin, but he is BSD-phobic so I thought it was safer to do it myself.

I just upgraded from 3.0.23d to 3.0.25 and I'm noticing that winbind is chewing up a lot of CPU usage. There are always 2 winbindd processes and one uses about 80% cpu and the other use 15% cpu. When I run a tcpdump and look at the traffic going to/from the domain controller winbindd is connected to, there is a constant flow of traffic. Here is the winbind setup from my smb.conf file:

I am running Samba ver 3.0.37 on Solaris 10 (sparc) as a PDC with LDAP for the backend for both samba and unix accounts. Assume the samba SMBPDC is called "PDC." I have also set up a trust with an Windows domain- lets call it WINDOMAIN- (the PDC for the Windows domain is Win 2003 but is in mixed mode for backwards compat.) The SAMBA domain trusts the WINDOWS domain, not not vice

Dear I have connected Samba 3.5.6 to an Active Directory server this active Directory store about 1500 users Winbind is unable to retrieve users and failed to retrieve group list. The strange thing is Winbind found 775042106 users when trying to query groups!! How can i solve the issue ? wbinfo --all-domains BUILTIN ONESYS-SAMBA USGPEOPLEFR ASP SMARTPEOPLE USGMCFR USGPEOPLEAT USGPEOPLEBE

Hi,dovecot is create an Fatal Panik Error. <AM5DMwaCBlgpDQAAWm89Cw>: Fatal: master: service(lmtp): child 3369 killed with signal 6 (core dumps disabled) <1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script != NULL) <1jx3DhuCBlg1DQAAWm89Cw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x93fae)

Hi folks ! Has someone any idea on this issue on AIX 5.3 TL 10 with winbind ? I'm really stuck now ... I think everything is working pretty well with WINBIND and AD 2k3 , but not my most important point : I absolutely need the Secondary groups of each AD user which get connected to the AIX to use this filter with sudo... I only get Primary Group (which is by default "Domain Users"

Hello, is my understanding of the parameter "imap_idle_notify_interval" right, if i say, it's the time between two point where dovecot tells the client he is here, and sould have nothing directly todo with the notification of new mails arrived. I played with the values around. And the courios is, in thunderbird the folloing. set to 30 seconds. Thunderbird pop up around 25 seconds

Hi. I'm using CentOS 5 with samba3x packages (Samba 3.5.10) and Solaris 10 (Samba 3.5.8) for achieving AD integration. Samba hosts are added as domain members. Now, I've tried to add CentOS 6, which also uses 3.5.10, but have encountered a problem -> users cannot authenticate for some reason. Configurations are pretty much the same across the board, and they look like this: #

* Stephan Bosch <stephan at rename-it.nl>: > Op 10/18/2016 om 10:28 PM schreef Sven Roellig: > > Hi,dovecot is create an Fatal Panik Error. > > <AM5DMwaCBlgpDQAAWm89Cw>: Fatal: master: service(lmtp): child 3369 killed with signal 6 (core dumps disabled) > > <1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts):

I shut my Samba PDC and all members down for some PC rearranging and now having an issue with one member server on Ubuntu 10.12 with Samba 3.5.4 after restarting all. It would not connect, I tried to remove the computer name from LDAP and re-join the domain, that was successfully joined and the entry reappears in LDAP, but it times out when trying to connect to that host via the network or

Everyone, I am going nuts trying to figure this problem out. I have successfully joined a SUSE 10 server to our domain and configured samba for ADS authentication. This exact setup works on all my other servers. On this one, I keep getting access denied when entering my domain password despite the fact that I have tried it literally dozens of times. I am 100% confident I am

Hi. First, sorry by my bad english :) I had a samba 3.0 and use a script with smbclient to send messages to 30 computers in my laboratory. I upgrade to debian squeeze and samba 3.5 and now i dont use the script command. root at escort:~# echo "Testando" | smbclient -NM LAB5-01 -I 192.168.3.200 Type your message, ending it with a Control-D cli_message returned NT_STATUS_PIPE_BROKEN I

Hi, I recently updated my Samba from 3.3 to 3.5, and while that worked fine, I can no longer access my shares - it asks for a password, which fails even if I do enter a correct one. Here is one of my shares - very simple, I think: [myshare] comment = My Share path = /path/to/myshare public = yes read only = yes writable = no browseable = yes printable = no guest ok = yes