similar to: Samba 3.5 + ldap backend - I can't logon under PDC

Hi , I use Samba 3.4.7 PDC + ldap backend . I can't put the machine if I don't specify the wins server on Pc-client. I try different name resolve order , but nothing change ? Can you help me ? My global is : [global] workgroup = workgroup netbios name = SERVER server string = Server Samba wins support = yes browse list = Yes remote announce = 10.0.0.255/workgroup

Hi Rowland, I tried that but didn't work. # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 9033b998 dn: olcDatabase={1}hdb objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: {1}hdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=testdom olcAccess: {0}to attrs=sambaNTPassword,sambaPwdLastSet,sambaPwdMustChange by dn="cn=admin,dc=testdom" write by self

Hi Im looking to config a BDC with ldap. It seems the connection with ldap primary server works, but Im confused with the shared folders. I understood when you creates a BDC needs to put the same global information: [global] workgroup = DOMAIN netbios name = DOMAIN-PDC security = user enable privileges = yes interfaces = 127.0.0.0/8 eth0 10.0.1.0/24 10.0.0.0/24 server string =

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

Hi list, My brand new samba network is working pretty good, ironing out some glitches. Win XP users cannot change their password. I use SaMBa as a domain-controller with an LDAP backend. A stripped down version of the config is below. I set minimum password length to 8, trying to change the password to a 7 char long gives me the messages that the password does not meet requirements. So that

Hi, I have a little problem with my Samba PDC setup. I have a Debian / Etch with Samba 3.0.24 with OpenLDAP Backend and use it as PDC with domain logons and roaming profiles enabled. The logon for normal domain users work without any problems, but when I login with my domain administrator account my Windows XP Professional client I have a big problem. After the logout, when it tries to copy

Hi community. Let me tell you what happed to me. I configure samba to authenticate to an LDAP server, everything wokrs perfect, I got rid of the /etc/passwd file, now all my users reside in the LDAP database, I can connect via ssh for example without any problem, getent passwd returns the information as expected, till here just like a sharm. No, I connect from a windows 2000 client as

I've almost got it. I swear I've almost got it (and I've been doing a lot of swearing lately). I re-built my PDC, starting from scratch. I'm not using the editposix extensions anymore - I'm using the smbldap tools as shown (I think) in the Samba by Example. I really really thought I did everything right. Obviously I was wrong. What works - all my workstations and

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

Running samba-3.0.24 with ldap on debian etch. Whenever I try to add an xp pro machine to the domain I get (on the pc) "the username can not be found". I'm loggin in as admin. In the samba log I get (for this pc) " passdb/pdb_interface.c:pdb_default_create_user(368) _samr_create_user: Running the command `/usr/local/smbldap-tools/smbldap-useradd -w

Hello list! I'm trying to debug a problem that surfaced after a Samba upgrade from v3.5.x to v4.1.17. The problem is that Win7 workstations appear to randomly experience domain trust issues logging in, although they can log in some times, they are unsuccessful at other times. I cannot so far predict what would result in or influence this behaviour. These are workstations on which

Migration was held in connection with the breakdown of the old server after setting up a new server stopped working to add windows pc to a domain root at pdc:/var/log/samba# cat /etc/samba/smb.conf [global] # Default options allow nt4 crypto = yes client ntlmv2 auth = no disable spoolss = yes dns proxy

Hi, I have a problem with samba3. I run samba 3.0.2 with ldap 2.1.23 and smbldap tools 0.8.4, when i logging to the domain i don't have problems with "Domain Admins" groups, but i try logging to the domain from user in the "Domain Users" groups the client (Windows 2000) send me the message "You do not have access to logon to this Session". When I add the user to

Hello! I have Samba with LDAP password backend. -Logging to shell works with ldap accounts -Logging to smb-share works with ldap accounts -Adding computers to domain with (shown in conf. file) and without (manually) works But here's my problem: -Logging to domain with username & passwd doesn't work When using smbpasswd -file as backend it works After 3 days of googling I'm

Hi samba folks, I'm running an NT$-style samba PDC and 2 BDCs. They are all on samba 3.6.25 (the SERNET packages on debian wheezy) I have a domain trust with another server on another subnet, I think they run samba 3.5, also NT4-style domain. Everything ran fine, they can login to our machines and vice versa, winbind can resolve their usernames etc. Now I upgraded the PDC to debian jessie,

Hello, I have a question about machine accounts. I using Samba 3.0, OpenLDAP 2.1.30 and Berkeley 4.2.52 on backend on RedHat machines. I also have 3 slave/BDC's and 1 master/PDC Right now all of my users and groups exist entirely in the LDAP directory. I have a few accounts in addition to the normal system accounts that are used for emergency access. All authention and group enumeration uses

I have noticed while testing my Samba 3.0.2a primary and backup domain controllers with Windows XP clients, that when I attempt to login to the Samba PDC, the XP client will sometimes randomly choose the backup domain controller. I only want the client to join the backup domain controller when the PDC is offline. I am not experiencing any random network outages or DNS failures so I am bewildered

I'm trying to iron out all the problems on my PDC. It's setup with a LDAP backend that's replicated to an ldap slave/BDC. Here's the problem: # smbldap-groupshow 'domain admins' dn: cn=Domain Admins,ou=People,dc=strozllc,dc=com objectClass: posixGroup,sambaGroupMapping gidNumber: 512 cn: Domain Admins memberUid: Administrator,root,astanley description: Netbios Domain

Hi, i?ve installed Samba Version: 3.0.14a-3sarge1 on Debian Sarge.- Samba works great like a pdc with system users.... but i want to connect with ldap.. but it does not work.- my ldap suffix is like this: ou=samba,o=sernam ou=Users,ou=samba,o=organization ou=Groups,ou=samba,o=organization ou=Computers,ou=samba,o=organization ou=Idmap,ou=samba,o=organization

I am setting up a OpenLdap PDC with file and print services on Ubuntu Jaunty. Jaunty ships with samba 3.3.2. I configured samba to just use the registry back in which I think is pretty cool! What happend when I use the Add print wizard to add my Windows XP drivers I get the famous "unable to install driver access denied" message. I can ssh into the box with my user id and create files in