similar to: understanding the ldap backend

Not sure if this is where I should ask about this, but if I try to run any of the smbldap-* scripts, I get the following kind of output: oink:/usr/local/sbin # ./smbldap-populate Using builtin directory structure erreur LDAP: Can't contact master ldap server (IO::Socket::INET: Bad protocol 'tcp') at /usr/local/sbin//smbldap_tools.pm line 153. I feel like this must be from a typo

On Samba 3.5.4, I have a share that should be writable by all in the Domain Users group. When I write to the share, the permission mode is correct but the data doesn't have the correct group and instead lists the username as the group. I tried using "force group" but the share stopped being accessible after a restart so I removed it. It doesn't seem like this is standard

Hello! I'm using Samba as PDC in a small company (~40 computers), the environment is the following: Gentoo linux 2.6.14-hardened-r5, Samba 3.0.22-r2, OpenLDAP 2.3.24-r1, nss_ldap 2.49, Windows XP clients The problem is that profile-portability doesn't work. A user first logs into a machine, then he can't use his profile on another one. The samba log says: [2006/08/27 20:20:37, 1]

I've been fiddling lately with Samba 3 coupled with openldap, nss_ldap, pam_ldap and the smbldap-tools to create a PDC. Following various examples, most things work, but I have an issue with changing passwords from Windows. If I manually change a password with smbldap-passwd, the script correctly adjusts the sambaPwdMustChange attribute according to what defaultMaxPasswordAge is set to. If

Sorry for the duplicate I forget to fill in the subject line. smbd crashes on startup /var/log/samba/smbd output: [2008/10/30 00:58:56, 1] passdb/pdb_ldap.c:ldapsam_enum_group_memberships(2850) User account [nobody] not found! [2008/10/30 00:58:56, 0] lib/fault.c:fault_report(40) =============================================================== [2008/10/30 00:58:56, 0]

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

Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -

My Configuration, On my PDC: Samba version 3.2.15 /LDAP-Master (slurpd)/SMBD4wins <-- version 3.3.12 not working. Downgrade again On my BDC: Samba version 3.3.12 /LDAP-Slave <-- version 3.3.12 working [global] on PDC [global] workgroup = tuepdc.local bind interfaces only = true interfaces = 192.168.135.143/24 127.0.0.0/8 socket address = 192.168.135.255 profile acls = no hosts allow

I've been trying to do this for days, and I think I'm really close. It's become one of those so-close-yet-so-far sorts of things. I'm running Gentoo -- all sync'ed up and current as of a week ago -- with the following package versions: openldap-2.1.30-r5 pam_ldap-178-r1 nss_ldap-239-r1 smbldap-tools-0.9.1-r1 phpldapadmin-0.9.5 (very cool, I must say!) samba-3.0.14a-r2

I've upgrade to Samba 3.0.4 a System wich it's running SLES 8. The System is working with LDAP and smbldap-tools 0.8.4 for managing users and groups. I'd like to manage the user and group with usrmgr.exe running into a Windows 2000. When I tried adding new user the programs didn't work and it's reported an error. The log system running in the PDC [SLES 8], reporting:

Hi All, I'm having a problem with cross subnet browsing and name resolution across an openvpn tunnel. i've found quite a few people who've had the same on mail lists but none of their fixes have worked. The spec of the setups at both ends of the tunnel are as follows: OS - CentOS 5.5 Samba Version 3.5.4 OpenVPN Version 2.0.9-1 Each server is configured in gateway mode with two NICS,

I have a Samba PDC setup using LDAP as the passdb. I want to add another Samba server to the mix. I believe I want to add it in as a Domain Server; however, I can't seem to get it working. On the PDC server I am running: - linux (2.6.latest) - openldap (latest) - samba (3.latest) - nss On the Domain Server I am running: - samba (latest 3.latest) - nss I thought someone might

I've been trying for the past week to get Samba and LDAP to work together as a PDC on my Gentoo box and allow some XP boxes to get in. I've read and followed the how-to's (emerged and unmergred more then a few times) My LDAP accounts all seem to work when I do the ssh test into them. Changing the domain in XP fails with the "network path not found error" even after all

I recently set up a backup domain controller using Samba 3.0.23. I have a Samba PDC already running, and all is working fine, but once I added the BDC, now when people log in to their windows account, their home directory is now being mapped to their home on the BDC (which is empty) instead of the PDC. Conf files from each below: PDC Samba Conf: [global] unix charset = LOCALE

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

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

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

Hi people: I'm using Samba 3.5.11 with some sharing settings like these: [global] workgroup = MARKETING netbios name = SMBSERVER server string = Samba, OpenLDAP Server obey pam restrictions = Yes passdb backend = ldapsam:"ldap://localhost" passwd program = /usr/sbin/smbldap-passwd %u passwd chat = *New*password* %n\n

Hello. I have some problem, with a new configuration on a new PC. I want to setup a SAMBA PDC using an HOWTO. This howto was working on OPENSUSE 10.1 with a X86 processor and I have used it a lot of time. Now I use OPENSUSE 10.3. The new PC run a X64 processor. After the fresh install and following : http://samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html I could not make

Hi there, I'm not able to get winbind to work, although searched google and studied and tried nearly every howto and forum entry on the net the last week.... it simply doesn't work and I don't understand why.... My Samba3-Domain SUPZ (samba & ldap Linux PDC, Windows Clients) works perfektly with all ldap users, groups (linux and from windows) and computer accounts (Win2000 WS).