similar to: winbind hang

Displaying 20 results from an estimated 2000 matches similar to: "winbind hang"

2023 Nov 16
1
WInbind hang?
Hello We are running several Red Hat 7 servers as domain members using AD for winbind idmap backend and it had been working fine (no sssd is configured either) The last month or so (possibly since the latest samba-winbind package update we applied on Sep 24), server ssh logins on several servers hang on occasion, until a winbind restart, when it all works again Since this is the Red Hat
2023 Nov 16
1
WInbind hang?
I've had that happen in the past with non-RedHat linux boxes. Fortunately we have Saltstack on all the boxes and can just salt '*' cmd.run 'killall -SIGKILL winbindd; service winbind restart' But it hangs SSH sessions and things like 'ls -lha' that need to resolve usernames and groups. i.e. if you removed winbind from /etc/nsswitch.conf it would stop happening. The
2018 Dec 09
2
"wbinfo -u" considered harmful towards Winbindd...
Our setup: Windows AD realm with ~115K users (and numerous groups etc) FreeBSD servers with Samba 4.7.6 and Samba 4.9.3 (both show the same growth) We just noticed that one of the ‘winbindd’ daemons on the servers seems to be growing and growing forever. A bit of detective work pointed us at the “wbinfo -u” command being that culprit. As part of a systems monitoring script we ran that once a
2019 May 30
1
domain won't go online
Hi. I'm hoping for some advise/help. I have a domain that won't seem to go online: $ wbinfo --online-status BUILTIN : active connection MY-HOST : active connection FOO : no active connection The log for the domain repeats over and over again: [2019/05/30 09:34:10.259173, 3, pid=1606, effective(0, 0), real(0, 0), class=auth] ../../auth/ntlmssp/ntlmssp_sign.c:514(ntlmssp_sign_reset)
2023 Aug 01
1
Joining a new Samba AD DC
On Mon Jul 31 11:17:57 2023 Mark Foley via samba <samba at lists.samba.org> wrote: > On Jul 31 03:00:37 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On 30/07/2023 22:24, Mark Foley via samba wrote: > > > That gave me: > > > > > > # host -t A 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local > > > host:
2013 Jan 24
0
64 Bit Build 3.6.11 on AIX 6 with acls enabled dumps core,
Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
2023 Aug 02
1
Joining a new Samba AD DC
On 01/08/2023 22:40, Mark Foley via samba wrote: > Is not being able to run 'host -t A' a show stopper here? The wiki 'host -t CNAME' > gave, as expected: > > # host -t CNAME 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local. > Host 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local. not found: 3(NXDOMAIN) > > and when trying to add with
2023 Jul 30
1
Joining a new Samba AD DC
While awaiting feedback on the error results of my "samba-tool ntacl sysvolreset" (ref. my message, same thread, of Fri, 28 Jul 2023 17:04:21), I'm going to look at this problem with the DNS ... On Tue Jul 25 01:54:45 2023 Mark Foley via samba <samba at lists.samba.org> wrote: > On Jul 24 13:30:11 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: >
2006 Oct 23
1
Getting users and groups through winbind on FreeBSD
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.
2015 Jun 22
1
nsswitch/libnss_winbind.so.2
OK, issuing this command: $ getent passwd tunix Produces in /var/log/log.wb-STUDELEC-SA: 2015/06/22 12:32:37.473115, 4] ../source3/winbindd/winbindd_dual.c:1346(child_handler) Finished processing child request 20 [2015/06/22 12:32:37.473241, 4] ../source3/winbindd/winbindd_dual.c:1338(child_handler) child daemon request 20 [2015/06/22 12:32:37.473278, 3]
2015 Jun 22
0
nsswitch/libnss_winbind.so.2
On 22/06/15 11:59, Marc Recht? wrote: > Sorry I forgot the /etc/samba/smb.conf: > > [global] > > workgroup = STUDELEC-SA > server string = Samba Server Version %v > > ; netbios name = MYSERVER > > ; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24 > ; hosts allow = 127. 192.168.12. 192.168.13. > > ; max protocol = SMB2 > > #
2020 Jun 12
2
include in smb.conf
Hi Rowland >> The folders must be mounted on a drive letter, ex: "H" in the windows >> clients workstations. >So, you are referring to Windows home Directories, now stored on a Samba >server. Next question, what sort of Samba server, a DC, Unix domain >member or what ? I have 2 DC Samba 4 (migrated from Windows 2008 Server) and the users' Home folders are stored
2015 Jun 22
0
nsswitch/libnss_winbind.so.2
On 22/06/15 13:19, Marc Rechte wrote: > > > Le 22/06/2015 13:23, Rowland Penny a ?crit : >> On 22/06/15 11:59, Marc Recht? wrote: >>> Sorry I forgot the /etc/samba/smb.conf: >>> >>> [global] >>> >>> workgroup = STUDELEC-SA >>> server string = Samba Server Version %v >>> >>> ; netbios name = MYSERVER
2015 Nov 11
0
Printer server on AD server
On 11/11/15 10:41, Daniel Carrasco Marín wrote: > Hi, first of all i'm sorry for my english. > > I'm trying to create a print server in the same server that has the samba > AD but i cannot make it work. For now i've: > > - A working AD server with Samba 4.2.5 > - A Cups server with the print drivers > - GPO policies to install the printers in the
2015 Nov 11
0
Printer server on AD server
On 11/11/15 11:31, Daniel Carrasco Marín wrote: > Thanks to both but did not worked. Tomorrow i'll try to reinstall the > whole OS because maybe i've installed something wrong. > > Greetings!! > > 2015-11-11 12:08 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com > <mailto:rowlandpenny241155 at gmail.com>>: > > On 11/11/15 10:41, Daniel
2015 Nov 12
0
Printer server on AD server
Finally is working... I'm not sure, but maybe the problem was stupid (spool folder did not exist for example). Now I've another weird problem and I don't know how to find out the solution. When I use the original server fqdn or the ip address it works prefect, but I've added another dns entry and using that dns name all shares fail. I can resolve the name and even I can see the
2015 Jun 22
2
nsswitch/libnss_winbind.so.2
Sorry I forgot the /etc/samba/smb.conf: [global] workgroup = STUDELEC-SA server string = Samba Server Version %v ; netbios name = MYSERVER ; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24 ; hosts allow = 127. 192.168.12. 192.168.13. ; max protocol = SMB2 # log files split per-machine: log file = /var/log/samba/smb.log # maximum size of 50KB per log file, then rotate: max log size
2020 Feb 11
0
New DNS-Records not aviable
@Heinz, Thanks for testing also, but what is your samba version, OS and packages samba of compiled samba. To keep info bit more complete @Christian, can you try purge the deleted DNS records. Can you also add the debug 10 log, shown below to this bugreport. https://bugzilla.samba.org/show_bug.cgi?id=14268 I'll retest it here later on today with a few more zones. But i must finish some
2018 Mar 28
1
Winbind not working on Ubuntu 18.04 Samba 4.8.0 File Sever
Good Morning, Ive been trying to test Samba AD on Ubuntu 18.04 using samba version 4.8.0  The DC seems to be working fine all tests have passed.  I was able to connect Win7 RSAT, a Ubuntu workstation and a File server.  My problem is the file server will not give response to 'sudo getent passwd' with or with out username or DOMAIN\username. Everything else works as far as I can tell.
2015 Jun 22
2
nsswitch/libnss_winbind.so.2
Le 22/06/2015 13:23, Rowland Penny a ?crit : > On 22/06/15 11:59, Marc Recht? wrote: >> Sorry I forgot the /etc/samba/smb.conf: >> >> [global] >> >> workgroup = STUDELEC-SA >> server string = Samba Server Version %v >> >> ; netbios name = MYSERVER >> >> ; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24 >> ;