similar to: smbpasswd fails when changing user passwords

Hello, I still cannot change user passwords with my Samba 2.0.3 server: When I try to change a users password either through SWAT or when logged in, I get the following error message when trying to change the password: --- machine 127.0.0.1 rejected the session setup. Error was: ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or Session Setup are invalid.). Failed to

Running Samba 2.0.3 on a Digital Unix 4.0D system. All functions of the new Samba version appear to run properly (previously ran 1.9.15) with exception of users being able to change their own Samba password (root is only able to change password on behalf of users). Following is permissions assigned to smbpasswd: -rwxr-xr-x 1 root system 901120 Mar 31 16:06 smbpasswd Following is

On 30.08.19 11:01, Andrew Bartlett wrote: > I'm very sorry to advise that this script is not race-free in the > locking done on the AD databases, which is why we have written the > 'samba-tool domain backup offline' tool which holds the correct locks. > > You should only need to back up the domain on one DC as long as you are > confident the DC is correctly

Hi List! The following behavior was tested from Windows and smbclient, with different user-ids. Samba is PDC. Host is FC2. My shares: [projekte] comment = Projekte path = /var/smb/share/Projekte [projekteee] comment = Projekte path = /var/smb/share/Projekte You see, both

On Thu, 17 May 2018 09:07:21 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > We already "solved" this by using the long form of the domain name, > but I want to learn if we should do something additional: > > We had a mixed setup in the field, some PCs had a WINS server > configured, some not. We removed the WINS info from

We already "solved" this by using the long form of the domain name, but I want to learn if we should do something additional: We had a mixed setup in the field, some PCs had a WINS server configured, some not. We removed the WINS info from DHCP and saw no new problems (we wanted to have things the same way on all clients). Yesterday the local admin tried to join a new PC and entered

Am 2017-09-25 um 16:29 schrieb Rowland Penny via samba: >> DC # samba-tool user create kamleitnerl Le26xxx >> --nis-domain=arbeitsgruppe --unix-home=/home/kamleitnerl >> --uid-number=10070 --login-shell=/bin/false --gid-number=100 >> > > Where did you get the GID '100' from ? > Is this the gidNumber for Domain Users ? I think so: # wbinfo --gid-info=100

Arg.. wbinfo --gid-info=100 DC: Confirmed, DOMAIN\Domain Users Member: Fail. failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for gid 100 But both server show the same with : wbinfo -n "NTDOM\domain users" So imho, report bug if Rowland can confirm this with a samba from source. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Hi Stefan, > I am googling around for an issue and can't figure it out so far. > > Status: > > 2 Debian 9.3 ADCs with samba-4.6.12 each. > > 1 Gentoo Samba Domain Member server "main", > Samba version 4.5.15 (we downgraded because of another issue a month ago > or so). > > *one* AD user is able to log into his Windows10 PC, but doesn't get a >

Am 2017-12-04 um 12:42 schrieb Rowland Penny: > II take it that 'arbeitsgruppe' is the workgroup name, it should be > 'ARBEITSGRUPPE' in the 'idmap config' lines. The output of testparm shows them lowercase, smb.conf has it in uppercase: [global] security = ADS workgroup = ARBEITSGRUPPE realm = arbeitsgruppe.hidden.tld log file =

On Fri, 30 Dec 2016 15:52:33 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-12-30 um 14:44 schrieb Rowland Penny via samba: > > On Fri, 30 Dec 2016 14:26:01 +0100 > > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > > >> Am 2016-12-30 um 14:07 schrieb Rowland Penny via samba:

On Mon, 4 Dec 2017 12:56:37 +0100 "Stefan G. Weichinger" <lists at xunil.at> wrote: > Am 2017-12-04 um 12:42 schrieb Rowland Penny: > > > II take it that 'arbeitsgruppe' is the workgroup name, it should be > > 'ARBEITSGRUPPE' in the 'idmap config' lines. > > The output of testparm shows them lowercase, smb.conf has it in >

ok, edited etc all uidNumber now > 10000 except that "root", I was unsure now (?) gidNumber: # ldbsearch -H /var/lib/samba/private/sam.ldb cn=Domain\ Users | grep 'gidNumber' gidNumber: 10001 - smb.conf on member: idmap config * : backend = tdb idmap config * : range = 2000-2999 idmap config ARBEITSGRUPPE:backend = ad idmap config

And in addition to Rowlands comments.. Correct you hosts file to /etc/hosts 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # This server name and ip. 10.0.0.221 main.arbeitsgruppe.secret.tld main 10.0.0.224 backup.arbeitsgruppe.secret.tld backup Second. Post you

Hai Stephan, You need also this in smb.conf # enable offline logins winbind offline logon = yes I did also test my logins with one DC turned off. And login on the DM is no problem or my pcs, no problem. I did not test the AD logins thats because these have only linux logins for maintainance. And that always works. In a 2 DC setup, setup your nameservers first to the LAN ip of the

I am googling around for an issue and can't figure it out so far. Status: 2 Debian 9.3 ADCs with samba-4.6.12 each. 1 Gentoo Samba Domain Member server "main", Samba version 4.5.15 (we downgraded because of another issue a month ago or so). *one* AD user is able to log into his Windows10 PC, but doesn't get a network share connected. If I test that from the DM server or the

Am 2016-12-30 um 13:20 schrieb L.P.H. van Belle via samba: > And in addition to Rowlands comments.. > > Correct you hosts file to > /etc/hosts > 127.0.0.1 localhost > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > > # This server name and ip. >

Am 2016-12-30 um 14:07 schrieb Rowland Penny via samba: > Is this the smb.conf you got when you ran the classicupgrade ? > I don't think it is, can I suggest you remove any and all lines you > have added and restart samba that was the output of testparm smb.conf on DC: [global] workgroup = ARBEITSGRUPPE realm = arbeitsgruppe.secret.tld netbios name = BACKUP server role =

On Sun, 1 Jan 2017 15:40:53 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > googled and tried stuff: > > # net ads search '(|(uidNumber=*)(gidNumber=*))' sAMAccountName > uidNumber gidNumber -P | grep uidN | sort -n > > ... shows me uidNumbers: > > uidNumber: 0 You definitely shouldn't have a user with the ID

On Sun, 1 Jan 2017 17:05:44 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > ok, edited etc > > all uidNumber now > 10000 > > except that "root", I was unsure now (?) If you have a user called 'root', then it is easy, remove it, 'root' shouldn't exist in AD, it is a Unix only user and you need to