similar to: password sync "Failed to open/create TDB passwd" - some progress

I am trying to enable unix password sync. PDC is solaris 3.026a on Solaris 9. my smb.conf file includes: [global] workgroup = MYDOMAIN server string = myserver passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat=*New\sPassword:\s%n\nRe-enter\snew\sPassword:\s%n\npasswd:\s password\ssuccessfully\schanged*\n unix password sync

Samba 3.026a on Solaris PDC. I am trying to enable password sync. My smb.conf file includes... passdb backend = tdbsam passwd program = /usr/bin/passwd -r nis %u # passwd chat = *New*Password* %n\n *new*Password* %n\n *changed* # passwd chat = *New*Password* %n\n *Re-enter*new*Password* %n\n *changed* passwd

Hi, Running samba-4.1.12-24 on Centos 7.1, I've created about 15 user accounts which are working perfectly, then for some reason today I go to create another account and it starts erroring? Config; security = user passdb backend = tdbsam [root at sysvm-smb samba]# pdbedit -a testing new password: retype new password: Failed to add entry for user testing. With Debugging; -------------

I am running Samba 3.5.5 on Solaris 10. This is the latest Sun/Oracle provided build. I have an ldap backend for everything (unix+samba accounts, idmapping for domain trusts.) The Samba server is a PDC for a domain we can call "SAMBA." Each samba account is tied to a unix account. I have a one-way domain trust setup with a Windows 2003 domain which we can call

Hi, I was having problem with the tdbsam backend in which a particular user got listed twice with pdbedit. (http://www.mail-archive.com/samba at lists.samba.org/msg109110.html) Without much hope in fixing it, I am planning to re-generating passdb.tdb on my PDC by: (1)exporting tdbsam to smbpasswd backend (2)delete passdb.tdb (3)re-import smbpasswd to tdbsam backend With the command `

Hi. I've tried Samba 3.4.3 and it upgraded my passdb.tdb file. After testing I concluded that I'm not going to upgrade to 3.4.3 yet, because 'getent passwd' was broken in recent BlastWave Solaris packages: http://wiki.blastwave.org/forum/viewtopic.php?f=5&t=447&start=0 Now, after I downgraded the Samba back to 3.0.32, client connections started to malfunction. I saw

Samba 4.x, DC. Em 16/01/2015 16:37, "Gaiseric Vandal" <gaiseric.vandal at gmail.com> escreveu: > Is this samba 3.x or 4.x? DC or member server? > > I found for samba 3.x it was better to not explicitly define any ports in > smb.conf. > > > > > > > On 01/16/15 13:25, Thiago Ten?rio wrote: > >> Hi, >> >> I need to enable smb

If this is an NT4-style domain, then DNS is not essential. Things like SRV records aren't relevant since a lot of the NT4 is back from the NetBios days. It looks like your Win 10 machine thinks it is trying to join an AD domain. Windows clients machines typically are using DNS to resolve server names to IP addresses. However DNS does not provide info on locating PDC's

When I enable server signing in Samba (server signing = mandatory), I can still join a Window 7 machine to the domain but I am no longer able to log on into the domain using a domain user. Is this normal? I am using Samba 3.6.3 on Linux 12.04. Is there anything that needs to be configured on the Windows machine? Thanks, Ali

I currently have several fresh installs of XP that will connect to shares, but will not reconnect after a workstation reboot. These are workstations that are not joined to the domain. Only accessing shares from a local profile, but using the same user/pass to login as to connect to Samba. I get various errors at that point. Upon reboot, attempting to access the share generates: "An error

On 14/05/16 05:10, Ram Prasad Bikkina wrote: > ---------- Forwarded message ---------- > From: Ram Prasad Bikkina <parvathiprasadb at gmail.com> > Date: Sat, May 14, 2016 at 9:39 AM > Subject: Re: [Samba] Not able to join windows 10 clients to samba 3.6.23 > NT4 Style PDC > To: gaiseric.vandal at gmail.com > > > Hi Gaiseric Vandal, > > I applied these

Hi, I resolved NMBD errors, but still same error in windows 10 pro, Could please suggest any changes in windows 10 PC. Applied registry changes suggested by samba wiki but no improvement. I am able to join windows 7 clients without error. Regards, Ram On Mon, May 16, 2016 at 8:11 PM, Ram Prasad Bikkina <parvathiprasadb at gmail.com> wrote: > Hi Gaiseric, > > Thank you for

I prepared samba PDC and not able to join windows 10 clients. Please suggest any windows 10 registry settings.

Hello everybody, we have a problem joining a domain from a remote location. The remote location is connected via VPN. Everything is working as exspected but joining the samba domain from the remote location does not work. - Server Samba Version is 3.5.10 - Windows Client is XP SP3 - Joining the domain locally works without problems - ping does work in both directions - WINS is running on the

Hello, hello I'm writing you this email because when i want to set up a password policy with LDAP, this one isn't recognize by samba. In the log i've got this : ldapsam_getgroup: Did not find group, filter was (&(objectClass=sambaGroupMapping)(sambaSID=S-1-5-11)) ldapsam_getgroup: Did not find group, filter was (&(objectClass=sambaGroupMapping)(sambaSID=S-1-5-2))

The smbpasswd on my PDC (Solaris 9, Samba 3.026a) will truncate or corrupt passwords over 8 chars. The smbpasswd command on the linux clients (Samba 3.024a) is OK. Anyone know if this is a samba version issue or something solaris specific. Thanks

On 05/17/12 11:15, prabu.murugan at emc.com wrote: > > Hi, > > As a security concern we are upgrading samba to 3.4.17. > > I tried all possible option to compile samba 3.4.17 on Solaris 10_U10. > But it is not going through. > > > > User requirement is to compile samba 3.4.17 to support their > application. 3.4.17 is working on Solaris 9 and Solaris 10_U5. But

I am running Samba ver 3.0.33 on Solaris 10 (sparc.) Initially I had the server configured as a domain controller with the "passdb backend = tdbsam" option. The underlying unix accounts were stored in LDAP (Sun Directory Server.) Those accounts are also used for non-Samba services. Since I have domain trusts with NT domains, I am using winbind and idmapping. The idmap data was

On Fri, May 27, 2016 at 3:55 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > Is the netapp a member of the domain? Yes. > My assumption is that you can have domain members that are patched with domain controllers that are not. I don't know what you mean by that. This worked before the samba CVE changes took effect in the latest samba3 RPMs distributed by the CentOS

Hi, I am having a weird issue with samba where once a week approximately at the same time users will lose connectivity, if i run wbinfo -u all users are displayed wbinfo -g all groups are displayed However running getent passwd only shows local-users, no remote users are shown.. To fix the issue I have to change the name of my idmap config and restart samba and winbind and everything works