Displaying 20 results from an estimated 5000 matches similar to: "user login passwords are mixed up"
2016 Feb 04
0
user login passwords are mixed up
On 04/02/16 20:02, oeh univie edv lists wrote:
> Hello,
>
> Some users in my domain report that they have to use different (old)
> passwords on different computers. They say that they still have to use
> their "old" passwords after they changed it. My domain setup is that users
> are asked to automatically change their password on Windows 7 Enterprise
> after some
2016 Feb 20
3
user login passwords are mixed up
Hello,
In what samba version is parameter "old password allowed period"
introduced?
This parameter seems be the remedy to my problem but I cannot find it with
"testparm -v | grep password"
or in my
"man smb.conf"
Does it even exist in 4.1.17 (just the regular debian package)?
In this document it says it is for samba version 4:
https://www.mankier.com/5/smb.conf
I
2017 Mar 15
1
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
Try :
apt-get remove libbsd-dev
restart samba, now is the message gone?
Gr.
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens BasSamba via
> samba
> Verzonden: woensdag 15 maart 2017 16:09
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] samba: setproctitle not initialized, please either call
>
2016 Jul 04
3
samba4 stopped working
I've been using Samba4 on Debian/Jessie since it became "stable". After
the last upgrade however, I got a massive failure.
The first symptom I noticed was that I couldn't grab updates from the
Debian servers. However when clients tried to log in, the real problem
revealed itself. They could only log on using a temporary profile and
couldn't connect to any of the shares
2015 Mar 23
1
Samba4 classic upgrade problem
Hello.
I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP
backend on Debian to 4.1.6 on Ubuntu on a new machine.
The samba-tools creates the following *smb.con*f:
*# cat /etc/samba/smb.conf**
*[global]
workgroup = SOMEDOM
realm = somedom.local
netbios name = SOMEDOM
server role = member server
passdb backend = samba_dsdb
server
2015 May 01
2
recurring error in log.samba . . .
Thanks to various contributors on the Samba List (particularly Rowland,
Marc & Andrew), I have successfully configured a Samba AD DC on Ubuntu
14.04 from scratch and joined my Windows 2008 R2 Servers.
However, I have had a recurring error from the beginning --
[2015/04/30 05:06:31.194379, 0]
../source4/smbd/server.c:370(binary_smbd_main)
samba version 4.1.6-Ubuntu started.
2016 Apr 19
3
Samba4 quit working after update
Here's what I get at level 0 right after stopping/starting Samba:
[2016/04/19 12:27:06.043469, 0]
../source4/smbd/server.c:372(binary_smbd_main)
samba version 4.3.8-Ubuntu started.
Copyright Andrew Tridgell and the Samba Team 1992-2015
[2016/04/19 12:27:06.157629, 0]
../source4/smbd/server.c:490(binary_smbd_main)
samba: using 'standard' process model
samba: setproctitle not
2016 Apr 19
2
Samba4 quit working after update
There is no winbindd--it was never installed. I don't recall exactly why I
didn't install it, but I seem to recall something about Samba4 in an AD
domain control role not needing it. I ended up using SSS instead.
Sanatized smb.conf:
# Global parameters
[global]
workgroup = DCS
realm = DCS.LOCAL
netbios name = SERVER
server role = active directory domain
2016 Apr 19
4
Samba4 quit working after update
On 19/04/16 21:08, Thomas Smith wrote:
> It was my understanding that winbind wasn't necessary for Samba4. This
> server has been running for months without it.
>
> Sanatized smb.conf:
>
> # Global parameters
> [global]
> workgroup = DCS
> realm = DCS.LOCAL
> netbios name = SERVER
> server role = active directory domain
2016 Sep 20
2
setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor
Hi for all!
I have Samba 4.3.9-Ubuntu DC in ADDC_Mode and it's working perfectly
But in Samba Log have this: "samba: setproctitle not initialized, please
either call setproctitle_init() or link against libbsd-ctor."
The libbsd-dev package is installed
Is this a problem?
SAMBA.CONF:
# Global parameters
[global]
workgroup = TESTEAD
realm = testead.xxxxx.xxx
netbios name = GTESTE2
2015 Dec 30
4
Samba 4 AD - Samba Fails to Start, hdb_samba4_create_kdc (setup KDC database) failed
Hello to the Samba Mailing List,
This is my first post, so please, should I commit any faux pas, nudge me in
the right direction and I will adjust accordingly.
I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've
deployed for a client. Samba failed a few days ago and I've been unable to
resolve the issue on my own. Google searches are leading me in circles,
2013 Sep 05
1
Samba4 not able to set proc title.
Hey guys I currently am using the samba4 archlinux package to run my home
domain, everything seems to be working
however in my error log I get samba: setproctitle not initialized, please
either call setproctitle_init() or link against libbsd-ctor.
So my question is, how do I setproctitle_init() or link against
libbsd-ctor, or more rather, how do I get samba to?
2016 Dec 04
1
port 135 - NT_STATUS_CONNECTION_REFUSED
On 2016-12-04 10:25, Rowland Penny via samba wrote:
> On Sun, 04 Dec 2016 09:43:25 -0600
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
>
> On 2016-12-04 09:11, Rowland Penny via samba wrote:
>
> On Sun, 04 Dec 2016 08:01:09 -0600
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
>
> I have two DC's running
2018 Jul 24
2
SRV records not added by subsequent DC's
On Tue, 24 Jul 2018 14:15:04 +0100
Rowland Penny via samba <samba at lists.samba.org> wrote:
> On Tue, 24 Jul 2018 15:00:27 +0200
> > dc1 and dc2 have created SRV DNS records:
> >
> > # host -t SRV _ldap._tcp.dc._msdcs.iww.lan
> > _ldap._tcp.dc._msdcs.iww.lan has SRV record 0 100 389 dc1.iww.lan.
> > _ldap._tcp.dc._msdcs.iww.lan has SRV record 0 100 389
2015 Apr 17
2
Joining 2008 R2 to Samba4 AD DC
We have a Samba4 AD DC running on an Ubuntu 14.04 VM
[ smb.conf ]
# Global parameters
[global]
workgroup = MEADORANDCO
realm = meadorandco.com
netbios name = SOGO
server role = active directory domain controller
dns forwarder = 192.168.121.1
idmap_ldb:use rfc2307 = yes
passdb backend = samba
allow dns updates = nonsecure
2016 Mar 04
1
Samba AD/DC crashed again, third time in as many months
Could I get some input regarding restoring ACLs? There's nothing in the
Samba wiki about what to do with the ACL archive. I've finished all of the
other steps already, what do I need to do to restore this archive?
JS
On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org> wrote:
> On 03/03/16 20:33, IT Admin wrote:
>
>> I do have the 4.3.3 sources.
2015 Dec 04
1
setproctitle Errors
Hi List
I've spun up a fresh Debian 8 VM to test out the upgrade steps for a Debian
samba 4.1.17 package deployment to a compiled samba 4.2.5. All seem s to
work fine (apt-get remove samba first, followed by configure/make/install),
but I get the following errors in my samba.log:
samba: setproctitle not initialized, please either call setproctitle_init()
or link against libbsd-ctor
Is this
2016 Apr 19
2
Samba4 quit working after update
I set the Samba debug level to 4 a bit ago, so the logs are a bit
noisy--before that, there didn't seem to be much log activity when I
produced that error.
So with the debug level at 4, these entries kind of stand out a bit:
[2016/04/19 09:55:27.662721, 2]
../source4/smbd/process_standard.c:123(standard_child_pipe_handler)
Child 16336 (winbindd) exited with status 1
These entries repeat
2016 Dec 01
2
member server resolv.conf question
On 2016-12-01 10:00, Rowland Penny via samba wrote:
> On Thu, 01 Dec 2016 09:20:15 -0600
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
>
>> From: Bob of Donelson Trophy via samba <samba at lists.samba.org>
>> To: SAMBA MailList <samba at lists.samba.org>
>> Subject: [Samba] member server resolv.conf question
>> Date: Thu,
2019 Jun 11
2
NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot
Hi,
after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence - task_server_terminate: [XXXd failed to setup interfaces] error messages in log.samba (I removed a couple of "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." lines for better readability):
[2019/06/11 09:23:47.400171, 0]