similar to: Moving a computer from a down domain to a new domain

So as I said, I grabbed EVERYTHING that was in the /etc/samba dir along with ALL .tbd files and ran: # samba-tool domain classicupgrade --dbdir=/root/samba.PDC/dbdir/ --use-xattrs=yes --realm=home.htt --dns-backend=BIND9_DLZ /root/samba.PDC/etc/smb.conf ANd it resulted in (note ldap error): Reading smb.conf NOTE: Service printers is flagged unavailable. NOTE: Service print$ is flagged

Hi, I use Samba + Ldapas a domain controller but after the update the version of Debian6 to Debain 7I can't authenticate my users in the Samba server. logs: [2013/05/23 08:29:55.811240, 1] auth/server_info.c:386(samu_to_SamInfo3) The primary group domain sid(S-1-5-21-3651478259-4121578499-3132057975-513) does not match the domain sid(S-1-5-21-3182595135-1874831366-4239877494) for

Dear reader, I tried to switch my server from samba 3.5 to 3.6. Unfortunately I was not successful. The smb.conf below works without any problems under 3.5 With 3.6.3 I get the following error: [2012/02/23 09:32:21.669389, 1] auth/server_info.c:391(samu_to_SamInfo3) The primary group domain sid(S-1-5-21-463168302-511420122-2937072671-513) does not match the domain

On 08/28/2015 03:56 AM, Rowland Penny wrote: > On 27/08/15 23:23, Robert Moskowitz wrote: >> So as I said, I grabbed EVERYTHING that was in the /etc/samba dir >> along with ALL .tbd files and ran: >> >> # samba-tool domain classicupgrade --dbdir=/root/samba.PDC/dbdir/ >> --use-xattrs=yes --realm=home.htt --dns-backend=BIND9_DLZ >>

I have a domain with Samba 3 acting as PDC, and using LDAP (passdb backend = ldapsam). I now wanted to add a second Samba 3 machine as a simple file server. I get errors with getdomainsid and getlocalsid, so there is obviously still something wrong with my config. The PDC runs Samba 3.5.6 on Debian Squeeze. Sid queries return: # net getdomainsid SID for local machine MY_PDC_HOST is:

dn: cn=Domain Admins,ou=groups,dc=mydomain objectClass: top objectClass: posixGroup objectClass: sambaGroupMapping gidNumber: 512 cn: Domain Admins description: Netbios Domain Administrators sambaSID: S-1-5-21-3936576374-1604348213-1812465911-512 sambaGroupType: 2 displayName: Domain Admins memberUid: root memberUid: sadmin dn: cn=Domain Users,ou=groups,dc=mydomain objectClass: top objectClass:

Hi Harry, sadmin and tadmin are both admin logins. I was trying to domain join with both. sadmin is in ldap The olcdbindex.ldif gave this error SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" ldap_modify: Other (e.g., implementation specific) error (80) additional

On 27/08/15 23:23, Robert Moskowitz wrote: > So as I said, I grabbed EVERYTHING that was in the /etc/samba dir > along with ALL .tbd files and ran: > > # samba-tool domain classicupgrade --dbdir=/root/samba.PDC/dbdir/ > --use-xattrs=yes --realm=home.htt --dns-backend=BIND9_DLZ > /root/samba.PDC/etc/smb.conf > > ANd it resulted in (note ldap error): > > Reading

On 28/08/15 10:47, Robert Moskowitz wrote: > > > On 08/28/2015 03:56 AM, Rowland Penny wrote: >> On 27/08/15 23:23, Robert Moskowitz wrote: >>> So as I said, I grabbed EVERYTHING that was in the /etc/samba dir >>> along with ALL .tbd files and ran: >>> >>> # samba-tool domain classicupgrade --dbdir=/root/samba.PDC/dbdir/ >>>

Hello, I am using samba 4.1 sambaSID in my server alway change a new value after reboot. What wrong in my config? and How can sambaSID be stable? Thanks all! This is my samba server config: [global] workgroup = NISCI netbios name = NISCI server string = %h server (Samba, SAMBA) ;enable privileges = yes interfaces = lo eth1

I had been running a system on Centos 5.1 at INIT 3. I did the upgrade to Centos 5.2 with the aid of the powernowk8 patch. Previously I would VNC into the unit when I needed to do admin stuff with a GUI. Well I noticed that I was NOT getting GNOME via VNC since the upgrade (worked before just fine with 5.1). So I tried an INIT 5 from the command line (always worked before), but the system

Hi there, Sorry to come back to that, I tried to follow the code at https://github.com/samba-team/samba/blob/master/source3/auth/auth.c#L214 (and below) but I still can't understand why one Samba client can connect, but the other can't. I can't understand why, with one client, the code would go into "check_samsec.c:183" (and return "sam_account_ok") while, with

Hi Gruss, Had to ditch the VM and start again. Here is the info: tdbdump secrets.tdb |egrep -v '^data|^}|^{' key(21) = "SECRETS/SID/mydomain" key(18) = "SECRETS/SID/sam3dc" key(42) = "SECRETS/LDAP_BIND_PW/cn=admin,dc=mydomain" key(25) = "SECRETS/DOMGUID/mydomain" key(42) = "SECRETS/MACHINE_SEC_CHANNEL_TYPE/mydomain" key(42) =

Hello there. I'm having an issue authenticating a Windows 7 (not in a domain) against a Samba 4.1.17 (debian Jessie). It appears that the client is trying to authenticate using with it's machine name and not the user filled in the auth form. I'm using security = user and I can confirm that the share is working with Win8. Could you check my conf & the error and share me your

Hello, I?m currently having a problem where a non-root user can?t change his/her own password using smbpasswd command after the password expiration and would like to know how I could solve this problem. Currently, I have a samba server running on CentOS 6.5 with its passdb backend configured to another LDAP server. The samba version I?m currently using is samba-3.6.9-169 which should be the

Hello to all, is the first time I write to this mailing list, I wanted to ask you a hand about an upgrade of samba I did on a centos 5.5 i386 with kernel 2.6.18-308.24.1.el5, which I updated with yum samba3x-3.3. 8-0.52.el5_5.2 bringing it to samba3x-3.6.6-0.129.el5. Now I can not put the computer to the domain, the error is that I find myself Jan 24 17:53:03 VmPDC smbd[15115]: [2013/01/24

Hello, i have migrate a Samba (3.0.20b-3.19-1616-SUSE) to debian 9 (4.5.16-Debian). On the old suse users are created with smbpasswd -an foo On Windows (10) users have a User account with also empthy passwords. No AD or NT4-Domain (round about 10 Users) Then I try to connect to the share smbclient -NL \\192.xxx.xxx.xxx work. Connect from Windows to share with no password dosed work. Set a

The logs below still look like Samba is configured for encrypted passwords. As to your other mail, please, please use a more recent version than Samba 4.9 Andrew Bartlett On Sat, 2024-03-09 at 15:37 -0500, Tygre via samba wrote: > Hi there, > Sorry to come back to that, I tried to follow the code at > https://github.com/samba-team/samba/blob/master/source3/auth/auth.c#L214 > (and

Hi, I think that someone has the solution for my problem! ;) After i did the upgrade process in a samba server, from debian squeeze to wheezy, the new samba version (3.6.6) is not working. Searching on web, there are many causes for this error, and i dont know what is mine. I can't connect with smbclient -L host -U ldapuser, that give me error "session setup failed:

On Mon, 2024-03-04 at 20:10 -0500, Tygre via samba wrote: > Hi there, > I have looked for a solution to my problem on the Internet (and > in particular this mailing list), but couldn't find one, probably due > to searching for the wrong thing :-) > I have an RPI running Samba version 4.9.5-Debian. "pdbedit -L" > shows that the user "smbuser" exists. I