similar to: Ldap replication

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

Greetings. I've run into a trouble when trying to add a new Win7 machine on a domain. The domain is controlled by a server running Samba + LDAP (samba compiled with ldap support), on a Debian 5 OS at the local network. I've added the machine name to the LDAP three through phpldapadmin using the option "Samba3 Machine" on the related submenu and via terminal on samba. Then I

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:

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

I have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is

Excuse me for the little flood please, i've just checked it again and now i see SRV1 as master for exedra.cat workgroup, i event can see in the logs Samba name server SRV1 is now a local master browser for workgroup EXEDRA.CAT on subnet 192.168.69.203 So i'll keep digging on how to fix the issue exposed on my first email, tomorrow i'll try to see wether it's an IPV6 issue or

Hi, thanks a lot for your reply. Yes, i enabled wins through "wins support = yes", i also enabled lmhosts lookup and wins on all clients but will check it as you proposed. Tomorrow will try to disable ipv6 on Windows clients following this link https://support.microsoft.com/en-us/kb/929852 Which process did you follow to disable IPV6? I'm also wondering if it's really necessary

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

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

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

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

Hi, we are using SAMBA 3.6.1-1 (updating this archlinux machine is tooo ugly) and 3.6.6-1 on archlinux with the LDAP (Server version is 2.4.26-3) backend and manage the users, groups and computer by using the smbldap-tools. Currently we are experiencing the following problems: 1. changing the passwords takes longer than 30 seconds <- That's bad because we are using a gigabit ethernet

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

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

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

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))