similar to: Password change caused lose X flag

Displaying 20 results from an estimated 200 matches similar to: "Password change caused lose X flag"

2011 Nov 08
1
Problem while log on: Windows Server 2008 R2 in samba domain
Hi, I have a strange problem with a Windows Server 2008 R2-System as a member of a samba domain (Samba-Version on PDC: 3.4.12). Join was successfully, but when I log on Windows I got an error "Unknown user name or bad password." (Event ID 4625). Here an abstract of logfile for Windows Server 2008 R2-System (log level 10). Maybe some of you has an idea:
2019 Apr 23
3
Problem to join a windows XP
Hi, I'm not able to join a windows XP machine in samba AD DC. This XP machine is a VM. No problems when joining Windows 10 machines to this DC. On XP machine, after inserting the Administrator username\password to join the domain, the error message is - error while attempting to join the domain "VIDROESTE.IND": Internal error. I can see that the XP machine account was created in AD
2019 Apr 24
2
Problem to join a windows XP
Rowland, it was a typo. Sorry, I paste the smb.conf twice. I changed the smb.conf as you proposed, so: dns forwarder removed - yes it's in named.conf, and ntlm auth / lanman auth removed. I also checked the NTLMv2 configuration in windows XP. But the error is still there. I guess it's MIT as saw this in log: /usr/lib/mit/sbin/krb5kdc: kerberos: 10 But how can I confirm which kerberos
2015 Jun 04
1
error when samba-tool domain classicupgrade
When you try to upgrade on a test stand, an error occurs. I do not understand that you need to add ldap, or improve migration script? Before that I tried to version 4.1.7, but the error was the sam root at dc1:~/smb_old# samba --version Version 4.2.2-SerNet-Ubuntu-7.trusty I also modified the file --- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600 +++
2016 Jul 18
3
Debian Jessie joining AD as member fails with "The object name is not found."
Hi all! To clarify, it must have been removed from the copy-pasta, but “net ads join -U” did produce a password prompt as expected. The dig command produced the following: root at host:~$ dig -t SRV _ldap._tcp.domain.local ; <<>> DiG 9.9.5-9+deb8u6-Debian <<>> -t SRV _ldap._tcp.domain.local ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode:
2016 Jul 19
1
Debian Jessie joining AD as member fails with "The object name is not found."
Hi all! I had originally been using a DHCP-assigned address. I have now switched to a static IP, but that didn't solve the problem (same error message). I'm attaching my resolv.conf, nsswitch.conf and krb5.conf files. I have not manually altered either of them, although krb5.conf appears to have been updated by some tool somewhere along the way because my domain is listed as the
2013 Feb 05
1
Samba4 4.0.3 classicupgrade - Error converting string to value for line: "CurrentVersion"
Hello everyone, I'm trying to migrate from samba3 to samba4 (4.0.3 installed from source in a debian squeeze 6.0.6) And I'm getting this error: Setting up the registry convert_string_talloc: Conversion not supported. Error converting string to value for line: "CurrentVersion" I found this thread in internet about this
2016 Jul 10
0
Debian Jessie joining AD as member fails with "The object name is not found."
Hi all! I'm trying to join Debian Jessie to an existing AD domain as a member server (AD DC is Server 2012R2) to run it as a file server. I installed acl, samba, winbind, libnss-winbind, and krb5-user using APT, and configured /etc/samba/smb.conf according to the Samba wiki article. The error the join command is producing is " Failed to join domain: failed to join domain
2016 Jul 18
0
Debian Jessie joining AD as member fails with "The object name is not found."
I'll bet static ip, with correct resolv.conf hosts and nsswitch.conf and krb5.conf. This must be the clue... > Creation of workstation account failed: NT_STATUS_OBJECT_NAME_NOT_FOUND So the join reaches the AD but here something happens. Russelt, can you try again with debug 10 and post both logs. net ads join -UAdministrator and net ads join -UAdministratos -S YOUR_ADDC.domain.tld.
2018 Sep 05
2
Migration samba 3 to 4
Hello, Indeed when I copied the result for the mailing I made a mistake. MY.DOMAIN is a dummy name. The result of the migration command is Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Provisioning Exporting account policy Exporting groups Severe DB
2011 Jan 21
0
Can not set SPN errors (again)
Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and
2018 Sep 05
0
Migration samba 3 to 4
On Wed, 5 Sep 2018 16:53:50 +0200 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello, > > Indeed when I copied the result for the mailing I made a mistake. > MY.DOMAIN is a dummy name. The result of the migration command is > > Reading smb.conf > WARNING: The "idmap backend" option is deprecated > WARNING: The "idmap uid"
2003 Aug 08
0
smbpasswd -m, changing account to a machine account.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had a problem with smbpasswd -m The man pages says: -m This option tells smbpasswd that the account being changed is a MACHINE account. Currently this is used when Samba is being used as an NT Primary Domain Controller. This option is only available when
2018 Sep 06
2
Migration samba 3 to 4
Le 05/09/2018 à 18:32, Rowland Penny via samba a écrit : > On Wed, 5 Sep 2018 16:53:50 +0200 > Philippe Maladjian via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> Indeed when I copied the result for the mailing I made a mistake. >> MY.DOMAIN is a dummy name. The result of the migration command is >> >> Reading smb.conf >>
2018 Sep 18
2
Migration samba 3 to 4
Hello, I realize again test by resuming all 0 with the following configuration and I arrive at the same result. -------------------- smb.conf [global]     netbios name = svdom     server string = Gestionnaire de domaine     workgroup = dom.domain     hosts allow = 192.168.15. 192.168.6. 10.0.7.     security = user     domain master = yes     domain logons = yes     prefered master =
2018 Sep 04
2
Migration samba 3 to 4
Hello, I am working on the migration of our samba 3.5 domain controller (redhat 5.7) with ldap backend to samba 4.5 on a new server (debian 9.5). On the new server I transferred the smb.conf and all the contents of the /var/lib/samba folder to a temporary folder /root/samba3. To start the migration I use the command: # samba-tool domain samba3upgrade --dbdir =/root/samba3/ --realm =
2018 Sep 18
0
Migration samba 3 to 4
On Tue, 18 Sep 2018 11:30:04 +0200 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello, > > I realize again test by resuming all 0 with the following > configuration and I arrive at the same result. > > -------------------- smb.conf > > [global] >     netbios name = svdom >     server string = Gestionnaire de domaine >     workgroup
2018 Sep 05
2
Migration samba 3 to 4
Hello, I'm testing with this link but i'have the same error. # samba-tool domain classicupgrade --dbdir=/root/samba3/dbdir/ --realm=dom.hilaire --dns-backend=SAMBA_INTERNAL /root/samba3/etc/smb.conf # ll /root/samba3/ total 8 drwxr-xr-x 2 root root 4096 sept.  5 11:23 dbdir drwxr-xr-x 2 root root 4096 sept.  5 11:21 etc # ll /root/samba3/dbdir/ total 11900 -rw------- 1 root root   
2018 Sep 06
3
Migration samba 3 to 4
Le 06/09/2018 à 10:47, Rowland Penny via samba a écrit : > On Thu, 6 Sep 2018 09:16:05 +0200 > Philippe Maladjian via samba <samba at lists.samba.org> wrote: > >> >> >> Le 05/09/2018 à 18:32, Rowland Penny via samba a écrit : >>> If you are going to sanitise an object, please use it everywhere. >>> >>> The upgrade is trying to use
2018 Sep 18
2
Migration samba 3 to 4
Hello, On my current installation samba announces domain dom.domain, windows machines and users are registered on domain dom.hilaire, root dn of my ldap is dc = domain, dc = fr. At first I tested a migration by applying the vm of my server samba3 and my ldap. I migrated these VMs out of the production network and validated that with a pc from my production network (once the network settings