similar to: What does "NT_STATUS_PIPE_BROKEN" in log files mean ?

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

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 experts, I am currently investigating an issue with a bigger winbindd installation which causes all following winbindd requests to fail until winbindd is restarted. We use a slightly patched version of winbindd based on Samba 3.5.8. In the used setup the winbindd is joined to an AD domain and is quite busy with answering winbindd requests of type PAM_AUTH_CRAP, LOOKUPNAME, GETUSERSIDS,

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

So, I have "working" builds of Samba 3.6.10, and 4.0.2 using the traditional build system on AIX, both built with XLC. For historical reasons, we're needing to use 'encrypt passwords = no', so that Samba uses the OS password. The odd thing, is, the 3.6.10 Samba works just fine, but the 4.0.2 doesn't allow connections. Here's the Samba config I'm using on both:

I have a domain running a Windows 10 system on an Ubuntu 16.10 host system. The domain has 4096MiB of memory. When I try to save the domain, or managedsave the domain, I get an error when it's about 96% complete. The terminal session looks like this: virsh # save Windows10 windows10-20170402.save --bypass-cache --verbose Save: [ 95 %]error: Failed to save domain Windows10 to windows10-

Hello Louis and list, Le 03/11/2017 à 10:25, L.P.H. van Belle via samba a écrit : > Sorry for the slow reaction here. I was few days out of the office. No problem, thanks for your quick answer. > But can you try the universal 2 driver. That one works fine for me. > And if you send me the exact driver your trying to me, i'll test that one in my setup. In my second mail, i said

Hello everyone I am having an issue with one particular windows 10 PC not being able to map a samba share. When I map the network drive:*\\hostname\share* the window prompt to login pops up. I enter the correct username and password and after a minute I get this error: *The network path was not found. 0x80070035*. Looking at the windows 10 logs, I can see this message: *file and print

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

Was just browsing web and tried to save some files on a samba share and got: permission denied 3 times in a row... (and now on 4th try, it worked). The log for the past hour looks a bit odd... why so many module reloads? wouldn't they load once? Also I've never seen the "New VC == 0, if NT4.x compatible we would close all old resources." Why would I get so many session

I have tried everything, This is CentOS 6.4 with SELinux DISABLED, Bind version BIND 9.8.2rc1-RedHat-9.8.2-0.17, samba 4.0.6 downloaded as a tar.gz from samba.org -- I have read EVERY maillinglist, IRC Log, how-to on google, tutorial on samba.org, and many many people have had this problem and not once have any of the posters resolved it, so I am now a desperate man reaching out to you with as

Hello experts I currently have a file server running on CentOS 7. The file server is joined to the enterprise.com domain (with Samba 4.5). The enterprise.com domain (with samba 4.5) maintains a trust relationship with the example.com domain running on windows server 2012R2. The problem occurs when a user of the example.com (windows server) domain authenticates on a workstation of the

I'm playing around with Domain Membership to a WIndows 2012 AD Server. It appears I'm able to join the AD domain, but the domain member doesn't seem to authenticate anything against the DC once joined. Here is my smb.conf netbios name = Member workgroup = ZARTMAN security = ADS realm = ZARTMAN.LOCAL dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and

Hello LLVM-people, I have a problem and I hope that you could help me. I'm jitting some .BC files at runtime with the LLVM under Windows 7. Thanks to the function " getImageBase()" located in RuntimeDyldCOFFX86_64.h I'm able to support exceptions. But when moving the program to Windows 10, the exceptions will crash the program. I read that the __ImageBase is important for

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

Dear Samba friends, I have recently upgraded from Samba 3.0.36 to Samba 3.5.6. After upgrade I encounter the following error in log.smbd: [2011/06/03 10:09:43, 0] smbd/server.c:1119(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/06/03 10:09:43.379106, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The "share modes" option is

Just to make sure: Both Operatingsystems have the same architecture (x64 or x86)? And in both cases you JIT to the same Architecture? 2018-02-05 16:21 GMT+01:00 via llvm-dev <llvm-dev at lists.llvm.org>: > Hello LLVM-people, > > I have a problem and I hope that you could help me. I'm jitting some .BC > files at runtime with the LLVM under Windows 7. Thanks to the function

I'm trying to setup a Samba4 Active Directory server. I've gotten the server running, the IP addresses resolve properly. The Windows10 client can join the domain. I've run the basic checks that seem to be listed on the samba wiki and get the expected results. I've modified nsswitch.conf to include winbind on the passwd and group lines. I've made sure all machines are

I'm running samba4 as an AD DC, built from git (built ~3 days ago), with about ~20 Windows 8 clients. I've noticed a number of errors in the logs, pasted below. That group of errors repeats pretty consistently for a lot of different client machines. [2013/09/08 08:12:14.539679, 2] ../source3/smbd/reply.c:592(reply_special) netbios connect: name1=SERVER-NAME 0x20