[Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux) - Samba

This is a discussion on [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux) - Samba ; Hello people... I had to sign up in the list because I don't know what else I could do... I can't find my error anywhere!! The thing is that I have a Linux server with Ldap (openldap2.3) + Samba (3.0.26) ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

  1. [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    Hello people...

    I had to sign up in the list because I don't know what else I could
    do... I can't find my error anywhere!!

    The thing is that I have a Linux server with Ldap (openldap2.3) +
    Samba (3.0.26) + smldaptools (0.9.2-3), and I want to authenticate a
    windows 2000 Professional client machine against that server, but it
    won't work!!

    The domain is called "JOME", and the LDAP database structure is
    something like this (I hope you'll be able to see it properly)

    dc=jome
    |
    \-cn=Admin
    |
    \-ou=Group
    | |
    | \- cn= Account operators
    | \- cn= Administrators
    | \- cn= Backup Operators
    | \- cn= Domain Admins
    | \- cn= Domain Computers
    | \- cn= Domain Guests
    | \- cn= Domain Users
    | \- cn= Print operators
    | \- cn= Replicators
    | \- cn= test
    |
    \-ou=Hosts
    | |
    | \- uid=Enano$
    | \- uid=xxxx$
    |
    \-ou=Idmap
    |
    \-ou=People
    | |
    | \- uid=nobody
    | \- uid=root
    | \- uid=test
    \-sambaDomainName=JOME


    The user root is the Netbios Domain Administrator and its
    sambaPrimaryGroupSID is the same as Domain Admins.

    All the Group accounts in ou=Group except "test" were created by
    smbldap-populate.

    The linux server is the host called "xxxx" and the windows client is
    the host "enano"

    When I try to join the domain "JOME" from Windows, I am prompted for a
    user that has permission to create "things" in the domain. I fill the
    textboxes with "root" and the "rootpass", and in the samba.log file of
    the server (if the debug level is 2 or higher), it appears:
    "authentication for user [root] -> [root] -> [root] succeeded". After
    this, the machine (enano$) is properly created (if doesn't exist) in
    the Ldap schema (a new entry called enano$ appears in
    ou=Hosts,dc=jome) as shown in the diagram above.The thing is that
    everything seems to be fine until in the windows machine a "error
    window dialog" appears with a very ugly red signal, saying ("username
    not found"). I think it must be something wrong with the user "root",
    because if I try a username that is really non-existent (john, for
    instance) or if I mistype the password, the message that appears in
    windows is different (in my computer appears in Spanish, but it's
    something like "session starting error: username not found or wrong
    password")... I've tried to put a higher debug level in samba
    (smb.conf-> debug level=3) and between several other messages, it
    appears:
    [2008/02/22 15:33:37, 3] passdb/pdb_interface.cdb_default_create_user(354)
    pdb_default_create_user: failed to create a new user structure:
    NT_STATUS_NO_SUCH_USER

    But I don't know what structure user it may be... and I don't know why
    this error only appears when the debug level is that high (I've been
    googling around, and this level was only recomended for developers).
    Anyway, I'm attaching a part of the samba.log file (a complete
    process). You can see on lines #108 and
    #118 that it seems to be authenticating "root" properly, and on line
    #482 the error NT_STATUS_NO_SUCH_USER (as I said, this only appears
    with debug level=3 so I don't know if it is very serious or not...)
    I'm not sure what kind of "user structure" it is trying to create and
    why can't it (it was supposed to be able to create a "enano$" user...
    why can't it do the same now?). As you may see, it's not complete, but
    I took away some lines that I didn't consider relevant (maybe they
    were, but... ) I'm sorry a couple of attachments had to be compressed,
    but otherwise, the mail wouldn't be accepted.

    I have read somewhere
    (http://www.mami.net/univr/tng-ldap/h...2000_to_domain)
    that I need an entry in /etc/passwd for each machine. Ldap is "making"
    the passwd, but the machines (enano$ and xxxx$ are not "users"). A
    getent passwd gives this:

    root@xxxx# getent passwd
    root:x:0:0:root:/root:/bin/bash
    daemon:x:1:1:daemon:/usr/sbin:/bin/sh
    bin:x:2:2:bin:/bin:/bin/sh
    sys:x:3:3:sys:/dev:/bin/sh
    sync:x:4:65534:sync:/bin:/bin/sync
    games:x:5:60:games:/usr/games:/bin/sh
    man:x:6:12:man:/var/cache/man:/bin/sh
    lp:x:7:7:lp:/var/spool/lpd:/bin/sh
    mail:x:8:8:mail:/var/mail:/bin/sh
    news:x:9:9:news:/var/spool/news:/bin/sh
    uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
    proxy:x:13:13roxy:/bin:/bin/sh
    www-data:x:33:33:www-data:/var/www:/bin/sh
    backup:x:34:34:backup:/var/backups:/bin/sh
    list:x:38:38:Mailing List Manager:/var/list:/bin/sh
    irc:x:39:39:ircd:/var/run/ircd:/bin/sh
    gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
    nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
    dhcp:x:100:101::/nonexistent:/bin/false
    syslog:x:101:102::/home/syslog:/bin/false
    klog:x:102:103::/home/klog:/bin/false
    hplip:x:103:7:HPLIP system user,,,:/var/run/hplip:/bin/false
    avahi-autoipd:x:104:112:Avahi autoip
    daemon,,,:/var/lib/avahi-autoipd:/bin/false
    messagebus:x:105:113::/var/run/dbus:/bin/false
    avahi:x:106:114:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
    gdm:x:107:116:Gnome Display Manager:/var/lib/gdm:/bin/false
    haldaemon:x:108:117:Hardware abstraction layer,,,:/home/haldaemon:/bin/false
    hector:x:1000:1000:Hector Blanco,,,:/home/hector:/bin/bash
    openldap:x:109:120:OpenLDAP Server Account,,,:/var/lib/ldap:/bin/false
    sshd:x:110:65534::/var/run/sshd:/usr/sbin/nologin
    test:x:2000:2000:Test User:/home/test:/bin/bash
    root:x:0:0:Netbios Domain Administrator:/tmp:/bin/false
    nobody:x:999:514:nobody:/dev/null:/bin/false

    (the last three users: test, root and nobody only exist in the Ldap database)

    Ah, and from the windows client I am able to access the shared
    resources of the server when I login as "root" or "test" (users from
    the ldap entry ou=People)

    Just in case... an anonymous (without password) smbclient -L to the
    samba server gives this:

    root@xxxx:/var/lib/samba/netlogon# smbclient -L 192.168.1.30
    Password:
    Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]

    Sharename Type Comment
    --------- ---- -------
    netlogon Disk Network Logon Service
    profiles Disk Profile Share
    print$ Disk Printer Drivers
    IPC$ IPC IPC Service (xxxx PDC server
    Version 3.0.26a)
    Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]

    Server Comment
    --------- -------
    XXXX xxxx PDC server Version 3.0.26a

    Workgroup Master
    --------- -------
    JOME XXXX

    I am attaching too the Ldap tree (compressed too, sorry) the smb.conf
    file and the
    sambaldap-tools.conf file... just in case...

    Sorry for such a huge message, but I have no idea of what's wrong...

    Thank you very much in advance... Any hint (whatever) will be deeply
    appreciated!!

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  2. Re: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    have you ran smbpasswd -a root

    Hector Blanco wrote:
    > Hello people...
    >
    > I had to sign up in the list because I don't know what else I could
    > do... I can't find my error anywhere!!
    >
    > The thing is that I have a Linux server with Ldap (openldap2.3) +
    > Samba (3.0.26) + smldaptools (0.9.2-3), and I want to authenticate a
    > windows 2000 Professional client machine against that server, but it
    > won't work!!
    >
    > The domain is called "JOME", and the LDAP database structure is
    > something like this (I hope you'll be able to see it properly)
    >
    > dc=jome
    > |
    > \-cn=Admin
    > |
    > \-ou=Group
    > | |
    > | \- cn= Account operators
    > | \- cn= Administrators
    > | \- cn= Backup Operators
    > | \- cn= Domain Admins
    > | \- cn= Domain Computers
    > | \- cn= Domain Guests
    > | \- cn= Domain Users
    > | \- cn= Print operators
    > | \- cn= Replicators
    > | \- cn= test
    > |
    > \-ou=Hosts
    > | |
    > | \- uid=Enano$
    > | \- uid=xxxx$
    > |
    > \-ou=Idmap
    > |
    > \-ou=People
    > | |
    > | \- uid=nobody
    > | \- uid=root
    > | \- uid=test
    > \-sambaDomainName=JOME
    >
    >
    > The user root is the Netbios Domain Administrator and its
    > sambaPrimaryGroupSID is the same as Domain Admins.
    >
    > All the Group accounts in ou=Group except "test" were created by
    > smbldap-populate.
    >
    > The linux server is the host called "xxxx" and the windows client is
    > the host "enano"
    >
    > When I try to join the domain "JOME" from Windows, I am prompted for a
    > user that has permission to create "things" in the domain. I fill the
    > textboxes with "root" and the "rootpass", and in the samba.log file of
    > the server (if the debug level is 2 or higher), it appears:
    > "authentication for user [root] -> [root] -> [root] succeeded". After
    > this, the machine (enano$) is properly created (if doesn't exist) in
    > the Ldap schema (a new entry called enano$ appears in
    > ou=Hosts,dc=jome) as shown in the diagram above.The thing is that
    > everything seems to be fine until in the windows machine a "error
    > window dialog" appears with a very ugly red signal, saying ("username
    > not found"). I think it must be something wrong with the user "root",
    > because if I try a username that is really non-existent (john, for
    > instance) or if I mistype the password, the message that appears in
    > windows is different (in my computer appears in Spanish, but it's
    > something like "session starting error: username not found or wrong
    > password")... I've tried to put a higher debug level in samba
    > (smb.conf-> debug level=3) and between several other messages, it
    > appears:
    > [2008/02/22 15:33:37, 3] passdb/pdb_interface.cdb_default_create_user(354)
    > pdb_default_create_user: failed to create a new user structure:
    > NT_STATUS_NO_SUCH_USER
    >
    > But I don't know what structure user it may be... and I don't know why
    > this error only appears when the debug level is that high (I've been
    > googling around, and this level was only recomended for developers).
    > Anyway, I'm attaching a part of the samba.log file (a complete
    > process). You can see on lines #108 and
    > #118 that it seems to be authenticating "root" properly, and on line
    > #482 the error NT_STATUS_NO_SUCH_USER (as I said, this only appears
    > with debug level=3 so I don't know if it is very serious or not...)
    > I'm not sure what kind of "user structure" it is trying to create and
    > why can't it (it was supposed to be able to create a "enano$" user...
    > why can't it do the same now?). As you may see, it's not complete, but
    > I took away some lines that I didn't consider relevant (maybe they
    > were, but... ) I'm sorry a couple of attachments had to be compressed,
    > but otherwise, the mail wouldn't be accepted.
    >
    > I have read somewhere
    > (http://www.mami.net/univr/tng-ldap/h...2000_to_domain)
    > that I need an entry in /etc/passwd for each machine. Ldap is "making"
    > the passwd, but the machines (enano$ and xxxx$ are not "users"). A
    > getent passwd gives this:
    >
    > root@xxxx# getent passwd
    > root:x:0:0:root:/root:/bin/bash
    > daemon:x:1:1:daemon:/usr/sbin:/bin/sh
    > bin:x:2:2:bin:/bin:/bin/sh
    > sys:x:3:3:sys:/dev:/bin/sh
    > sync:x:4:65534:sync:/bin:/bin/sync
    > games:x:5:60:games:/usr/games:/bin/sh
    > man:x:6:12:man:/var/cache/man:/bin/sh
    > lp:x:7:7:lp:/var/spool/lpd:/bin/sh
    > mail:x:8:8:mail:/var/mail:/bin/sh
    > news:x:9:9:news:/var/spool/news:/bin/sh
    > uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
    > proxy:x:13:13roxy:/bin:/bin/sh
    > www-data:x:33:33:www-data:/var/www:/bin/sh
    > backup:x:34:34:backup:/var/backups:/bin/sh
    > list:x:38:38:Mailing List Manager:/var/list:/bin/sh
    > irc:x:39:39:ircd:/var/run/ircd:/bin/sh
    > gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
    > nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
    > dhcp:x:100:101::/nonexistent:/bin/false
    > syslog:x:101:102::/home/syslog:/bin/false
    > klog:x:102:103::/home/klog:/bin/false
    > hplip:x:103:7:HPLIP system user,,,:/var/run/hplip:/bin/false
    > avahi-autoipd:x:104:112:Avahi autoip
    > daemon,,,:/var/lib/avahi-autoipd:/bin/false
    > messagebus:x:105:113::/var/run/dbus:/bin/false
    > avahi:x:106:114:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
    > gdm:x:107:116:Gnome Display Manager:/var/lib/gdm:/bin/false
    > haldaemon:x:108:117:Hardware abstraction layer,,,:/home/haldaemon:/bin/false
    > hector:x:1000:1000:Hector Blanco,,,:/home/hector:/bin/bash
    > openldap:x:109:120:OpenLDAP Server Account,,,:/var/lib/ldap:/bin/false
    > sshd:x:110:65534::/var/run/sshd:/usr/sbin/nologin
    > test:x:2000:2000:Test User:/home/test:/bin/bash
    > root:x:0:0:Netbios Domain Administrator:/tmp:/bin/false
    > nobody:x:999:514:nobody:/dev/null:/bin/false
    >
    > (the last three users: test, root and nobody only exist in the Ldap database)
    >
    > Ah, and from the windows client I am able to access the shared
    > resources of the server when I login as "root" or "test" (users from
    > the ldap entry ou=People)
    >
    > Just in case... an anonymous (without password) smbclient -L to the
    > samba server gives this:
    >
    > root@xxxx:/var/lib/samba/netlogon# smbclient -L 192.168.1.30
    > Password:
    > Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]
    >
    > Sharename Type Comment
    > --------- ---- -------
    > netlogon Disk Network Logon Service
    > profiles Disk Profile Share
    > print$ Disk Printer Drivers
    > IPC$ IPC IPC Service (xxxx PDC server
    > Version 3.0.26a)
    > Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]
    >
    > Server Comment
    > --------- -------
    > XXXX xxxx PDC server Version 3.0.26a
    >
    > Workgroup Master
    > --------- -------
    > JOME XXXX
    >
    > I am attaching too the Ldap tree (compressed too, sorry) the smb.conf
    > file and the
    > sambaldap-tools.conf file... just in case...
    >
    > Sorry for such a huge message, but I have no idea of what's wrong...
    >
    > Thank you very much in advance... Any hint (whatever) will be deeply
    > appreciated!!
    >


    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  3. Re: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    On Friday 22 February 2008, Hector Blanco wrote:
    > Hello people...


    > The thing is that I have a Linux server with Ldap (openldap2.3) +
    > Samba (3.0.26) + smldaptools (0.9.2-3), and I want to authenticate a
    > windows 2000 Professional client machine against that server, but it
    > won't work!!


    > When I try to join the domain "JOME" from Windows, I am prompted for a
    > user that has permission to create "things" in the domain. I fill the
    > textboxes with "root" and the "rootpass", and in the samba.log file of
    > the server (if the debug level is 2 or higher), it appears:
    > "authentication for user [root] -> [root] -> [root] succeeded". After
    > this, the machine (enano$) is properly created (if doesn't exist) in
    > the Ldap schema (a new entry called enano$ appears in
    > ou=Hosts,dc=jome) as shown in the diagram above.The thing is that
    > everything seems to be fine until in the windows machine a "error
    > window dialog" appears with a very ugly red signal, saying ("username
    > not found").



    Sounds suspiciously similiar to a problem I've been having, except I'm not
    using LDAP, and my problem is with XP SP2 only. Unfortunately, I haven't
    found a solution to my problem either...yet. Search the archives for
    the "Joining Domain Problem only with XP SP2" if you want to see my thread.


    --
    Fail to learn history-repeat it.
    Fail to learn rights-lose them.
    Learn both-get screwed by previous two groups.
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  4. Re: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    Yes, I did, I did...

    2008/2/23, Adam Williams :
    > have you ran smbpasswd -a root
    >
    >
    > Hector Blanco wrote:
    > > Hello people...
    > >
    > > I had to sign up in the list because I don't know what else I could
    > > do... I can't find my error anywhere!!
    > >
    > > The thing is that I have a Linux server with Ldap (openldap2.3) +
    > > Samba (3.0.26) + smldaptools (0.9.2-3), and I want to authenticate a
    > > windows 2000 Professional client machine against that server, but it
    > > won't work!!
    > >
    > > The domain is called "JOME", and the LDAP database structure is
    > > something like this (I hope you'll be able to see it properly)
    > >
    > > dc=jome
    > > |
    > > \-cn=Admin
    > > |
    > > \-ou=Group
    > > | |
    > > | \- cn= Account operators
    > > | \- cn= Administrators
    > > | \- cn= Backup Operators
    > > | \- cn= Domain Admins
    > > | \- cn= Domain Computers
    > > | \- cn= Domain Guests
    > > | \- cn= Domain Users
    > > | \- cn= Print operators
    > > | \- cn= Replicators
    > > | \- cn= test
    > > |
    > > \-ou=Hosts
    > > | |
    > > | \- uid=Enano$
    > > | \- uid=xxxx$
    > > |
    > > \-ou=Idmap
    > > |
    > > \-ou=People
    > > | |
    > > | \- uid=nobody
    > > | \- uid=root
    > > | \- uid=test
    > > \-sambaDomainName=JOME
    > >
    > >
    > > The user root is the Netbios Domain Administrator and its
    > > sambaPrimaryGroupSID is the same as Domain Admins.
    > >
    > > All the Group accounts in ou=Group except "test" were created by
    > > smbldap-populate.
    > >
    > > The linux server is the host called "xxxx" and the windows client is
    > > the host "enano"
    > >
    > > When I try to join the domain "JOME" from Windows, I am prompted for a
    > > user that has permission to create "things" in the domain. I fill the
    > > textboxes with "root" and the "rootpass", and in the samba.log file of
    > > the server (if the debug level is 2 or higher), it appears:
    > > "authentication for user [root] -> [root] -> [root] succeeded". After
    > > this, the machine (enano$) is properly created (if doesn't exist) in
    > > the Ldap schema (a new entry called enano$ appears in
    > > ou=Hosts,dc=jome) as shown in the diagram above.The thing is that
    > > everything seems to be fine until in the windows machine a "error
    > > window dialog" appears with a very ugly red signal, saying ("username
    > > not found"). I think it must be something wrong with the user "root",
    > > because if I try a username that is really non-existent (john, for
    > > instance) or if I mistype the password, the message that appears in
    > > windows is different (in my computer appears in Spanish, but it's
    > > something like "session starting error: username not found or wrong
    > > password")... I've tried to put a higher debug level in samba
    > > (smb.conf-> debug level=3) and between several other messages, it
    > > appears:
    > > [2008/02/22 15:33:37, 3] passdb/pdb_interface.cdb_default_create_user(354)
    > > pdb_default_create_user: failed to create a new user structure:
    > > NT_STATUS_NO_SUCH_USER
    > >
    > > But I don't know what structure user it may be... and I don't know why
    > > this error only appears when the debug level is that high (I've been
    > > googling around, and this level was only recomended for developers).
    > > Anyway, I'm attaching a part of the samba.log file (a complete
    > > process). You can see on lines #108 and
    > > #118 that it seems to be authenticating "root" properly, and on line
    > > #482 the error NT_STATUS_NO_SUCH_USER (as I said, this only appears
    > > with debug level=3 so I don't know if it is very serious or not...)
    > > I'm not sure what kind of "user structure" it is trying to create and
    > > why can't it (it was supposed to be able to create a "enano$" user...
    > > why can't it do the same now?). As you may see, it's not complete, but
    > > I took away some lines that I didn't consider relevant (maybe they
    > > were, but... ) I'm sorry a couple of attachments had to be compressed,
    > > but otherwise, the mail wouldn't be accepted.
    > >
    > > I have read somewhere
    > > (http://www.mami.net/univr/tng-ldap/h...2000_to_domain)
    > > that I need an entry in /etc/passwd for each machine. Ldap is "making"
    > > the passwd, but the machines (enano$ and xxxx$ are not "users"). A
    > > getent passwd gives this:
    > >
    > > root@xxxx# getent passwd
    > > root:x:0:0:root:/root:/bin/bash
    > > daemon:x:1:1:daemon:/usr/sbin:/bin/sh
    > > bin:x:2:2:bin:/bin:/bin/sh
    > > sys:x:3:3:sys:/dev:/bin/sh
    > > sync:x:4:65534:sync:/bin:/bin/sync
    > > games:x:5:60:games:/usr/games:/bin/sh
    > > man:x:6:12:man:/var/cache/man:/bin/sh
    > > lp:x:7:7:lp:/var/spool/lpd:/bin/sh
    > > mail:x:8:8:mail:/var/mail:/bin/sh
    > > news:x:9:9:news:/var/spool/news:/bin/sh
    > > uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
    > > proxy:x:13:13roxy:/bin:/bin/sh
    > > www-data:x:33:33:www-data:/var/www:/bin/sh
    > > backup:x:34:34:backup:/var/backups:/bin/sh
    > > list:x:38:38:Mailing List Manager:/var/list:/bin/sh
    > > irc:x:39:39:ircd:/var/run/ircd:/bin/sh
    > > gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
    > > nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
    > > dhcp:x:100:101::/nonexistent:/bin/false
    > > syslog:x:101:102::/home/syslog:/bin/false
    > > klog:x:102:103::/home/klog:/bin/false
    > > hplip:x:103:7:HPLIP system user,,,:/var/run/hplip:/bin/false
    > > avahi-autoipd:x:104:112:Avahi autoip
    > > daemon,,,:/var/lib/avahi-autoipd:/bin/false
    > > messagebus:x:105:113::/var/run/dbus:/bin/false
    > > avahi:x:106:114:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
    > > gdm:x:107:116:Gnome Display Manager:/var/lib/gdm:/bin/false
    > > haldaemon:x:108:117:Hardware abstraction layer,,,:/home/haldaemon:/bin/false
    > > hector:x:1000:1000:Hector Blanco,,,:/home/hector:/bin/bash
    > > openldap:x:109:120:OpenLDAP Server Account,,,:/var/lib/ldap:/bin/false
    > > sshd:x:110:65534::/var/run/sshd:/usr/sbin/nologin
    > > test:x:2000:2000:Test User:/home/test:/bin/bash
    > > root:x:0:0:Netbios Domain Administrator:/tmp:/bin/false
    > > nobody:x:999:514:nobody:/dev/null:/bin/false
    > >
    > > (the last three users: test, root and nobody only exist in the Ldap database)
    > >
    > > Ah, and from the windows client I am able to access the shared
    > > resources of the server when I login as "root" or "test" (users from
    > > the ldap entry ou=People)
    > >
    > > Just in case... an anonymous (without password) smbclient -L to the
    > > samba server gives this:
    > >
    > > root@xxxx:/var/lib/samba/netlogon# smbclient -L 192.168.1.30
    > > Password:
    > > Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]
    > >
    > > Sharename Type Comment
    > > --------- ---- -------
    > > netlogon Disk Network Logon Service
    > > profiles Disk Profile Share
    > > print$ Disk Printer Drivers
    > > IPC$ IPC IPC Service (xxxx PDC server
    > > Version 3.0.26a)
    > > Domain=[JOME] OS=[Unix] Server=[Samba 3.0.26a]
    > >
    > > Server Comment
    > > --------- -------
    > > XXXX xxxx PDC server Version 3.0.26a
    > >
    > > Workgroup Master
    > > --------- -------
    > > JOME XXXX
    > >
    > > I am attaching too the Ldap tree (compressed too, sorry) the smb.conf
    > > file and the
    > > sambaldap-tools.conf file... just in case...
    > >
    > > Sorry for such a huge message, but I have no idea of what's wrong...
    > >
    > > Thank you very much in advance... Any hint (whatever) will be deeply
    > > appreciated!!
    > >

    >
    >

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  5. [Samba] Re: Windows 2000 pro doesn't join a domain with Samba+Ldap(linux)

    >Hector Blanco" wrote in message
    news:86e693810802221551h7feaf5e8n2a504646b64ac900@ mail.gmail.com...
    > Hello people...
    >
    > I had to sign up in the list because I don't know what else I could
    > do... I can't find my error anywhere!!
    >


    Hi Hector,

    Can you post your /etc/ldap.conf file and your /etc/nsswitch.conf file?
    Are there any other ldap.conf files in the /etc directory?

    Are you able to add users to the the domain?

    Please post the output from getent passwd group.



    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  6. [Samba] Re: Windows 2000 pro doesn't join a domain withSamba+Ldap(linux)

    "Jamrock" wrote in message
    news:fppc4b$imq$1@ger.gmane.org...
    > >Hector Blanco" wrote in message

    > news:86e693810802221551h7feaf5e8n2a504646b64ac900@ mail.gmail.com...
    > > Hello people...
    > >
    > > I had to sign up in the list because I don't know what else I could
    > > do... I can't find my error anywhere!!
    > >

    >
    > Hi Hector,
    >
    > Can you post your /etc/ldap.conf file and your /etc/nsswitch.conf file?
    > Are there any other ldap.conf files in the /etc directory?
    >
    > Are you able to add users to the the domain?
    >
    > Please post the output from getent passwd group.


    Sorry... That should have read

    Please post the output from getent group



    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  7. Re: [Samba] Re: Windows 2000 pro doesn't join a domain with Samba+Ldap(linux)

    I hope you can get attachments!!... I'll send the files you asked me
    for as attachment and I'll paste them in the message body too, but I
    think it's easier to read if they come in separated files...

    Anyway, I also want to thank the interest to all the people who are
    trying to help me... Thank you guys!

    I forgot to say that I am able to login with a Linux client. In the
    same client computer (the one called "Enano") in which I've got the
    Win2000, I've got a Debian too. That Debian is able to properly login
    with users that only exist in the "Xxxx" server Ldap database (the
    user "test", for instance)

    And adding users to the domain... yes, I think I can... if I can
    create machine accounts, it must be the same for normal users,
    right?... I mean: I can execute succesffuly the "smldap-useradd"
    command... I hope this is what you wanted to know

    I don't think I have any other ldap.conf files in /etc/... I have a
    whole directory called "/ldap" under "/etc", with information about
    the Ldap server and some information for how a client hat to connecto
    to a server (in the /etc/ldap/ldap.conf file), but no... no more stuff
    about the "client" in /etc/ (I don't have pam_ldap.conf or
    libnss-ldap.conf, if that's what you mean... I guess everything has
    been merged into that "/etc/ldap.conf" file)

    I am posting the output for getent group command (of the server):

    ------------------- #getent group ---------------------
    hector@xxxx:~$ getent group
    root:x:0:
    daemon:x:1:
    bin:x:2:
    sys:x:3:
    adm:x:4:hector
    tty:x:5:
    disk:x:6:
    lp:x:7:
    mail:x:8:
    news:x:9:
    uucp:x:10:
    man:x:12:
    proxy:x:13:
    kmem:x:15:
    dialout:x:20:hector
    fax:x:21:
    voice:x:22:
    cdrom:x:24:haldaemon,hector
    floppy:x:25:haldaemon,hector
    tape:x:26:
    sudo:x:27:
    audio:x:29:hector
    dip:x:30:hector
    www-data:x:33:
    backup:x:34:
    operator:x:37:
    list:x:38:
    irc:x:39:
    src:x:40:
    gnats:x:41:
    shadow:x:42:
    utmp:x:43:
    video:x:44:hector
    sasl:x:45:
    plugdev:x:46:haldaemon,hector
    staff:x:50:
    games:x:60:
    users:x:100:
    nogroup:x:65534:
    dhcp:x:101:
    syslog:x:102:
    klog:x:103:
    scanner:x:104:hplip,hector
    nvram:x:105:
    fuse:x:106:
    ssl-cert:x:107:
    lpadmin:x:108:hector
    admin:x:109:hector
    crontab:x:110:
    ssh:x:111:
    avahi-autoipd:x:112:
    messagebus:x:113:
    avahi:x:114:
    netdev:x:115:hector
    gdm:x:116:
    haldaemon:x:117:
    powerdev:x:118:haldaemon,hector
    slocate:x:119:
    hector:x:1000:
    openldap:x:120:
    test:*:2000:test
    Domain Admins:*:512:root
    Domain Users:*:513:
    Domain Guests:*:514:
    Domain Computers:*:515:
    Administrators:*:544:
    Account Operators:*:548:
    Print Operators:*:550:
    Backup Operators:*:551:
    Replicators:*:552:
    -----------------------------------------------------------------

    The last 10 groups from "test" to "Replicators" only exist in the Ldap
    database, and all the groups starting with a capital letter (from
    Domain Admins to Replicators) were created by smbldap-populate

    Thank you all!

    Under these lines I'm writing the contents of the two files you asked me:
    /etc/nsswitch.conf and
    /etc/ldap.conf



    ---------------------------- /etc/nsswitch.conf ------------------------
    # /etc/nsswitch.conf
    #
    # Example configuration of GNU Name Service Switch functionality.
    # If you have the `glibc-doc-reference' and `info' packages installed, try:
    # `info libc "Name Service Switch"' for information about this file.

    passwd: files ldap #compat
    group: files ldap #compat
    shadow: files ldap #files ldap #compat

    hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
    networks: files

    protocols: db files
    services: db files
    ethers: db files
    rpc: db files

    netgroup: nis
    ---------------------------------------------------------------


    ------------------------------------ /etc/ldap.conf ---------------------------
    ###DEBCONF###
    ##
    ## Configuration of this file will be managed by debconf as long as the
    ## first line of the file says '###DEBCONF###'
    ##
    ## You should use dpkg-reconfigure to configure this file via debconf
    ##

    #
    # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $
    #
    # This is the configuration file for the LDAP nameservice
    # switch library and the LDAP PAM module.
    #
    # PADL Software
    # http://www.padl.com
    #

    # Your LDAP server. Must be resolvable without using LDAP.
    # Multiple hosts may be specified, each separated by a
    # space. How long nss_ldap takes to failover depends on
    # whether your LDAP client library supports configurable
    # network or connect timeouts (see bind_timelimit).
    host xxxx #HECTOR: Original

    # The distinguished name of the search base.
    base dc=jome

    # Another way to specify your LDAP server is to provide an
    # uri with the server name. This allows to use
    # Unix Domain Sockets to connect to a local LDAP Server.
    #uri ldap://127.0.0.1/
    #uri ldaps://127.0.0.1/
    #uri ldapi://%2fvar%2frun%2fldapi_sock/
    # Note: %2f encodes the '/' used as directory separator
    #uri ldap://xxxx:389/ #HECTOR: Esta linea no estaba. Descubri con
    horror que si se activa, casca

    # The LDAP version to use (defaults to 3
    # if supported by client library)
    ldap_version 3

    # The distinguished name to bind to the server with.
    # Optional: default is to bind anonymously.
    #binddn cn=proxyuser,dc=padl,dc=com

    # The credentials to bind with.
    # Optional: default is no credential.
    #bindpw secret

    # The distinguished name to bind to the server with
    # if the effective user ID is root. Password is
    # stored in /etc/ldap.secret (mode 600)
    rootbinddn cn=Admin,dc=jome

    # The port.
    # Optional: default is 389.
    #port 389
    #port 636 #HECTOR: Es seguro

    # The search scope.
    #scope sub
    #scope one
    #scope base

    # Search timelimit
    #timelimit 30

    # Bind/connect timelimit
    #bind_timelimit 30

    # Reconnect policy: hard (default) will retry connecting to
    # the software with exponential backoff, soft will fail
    # immediately.
    #bind_policy hard
    #bind_policy soft #HECTOR: Originalmente era la linea anterior... yo,
    yo... lo lei en un tutorial
    (http://www.debuntu.org/ldap-server-a...dap-clients-p2)

    # Idle timelimit; client will close connections
    # (nss_ldap only) if the server has not been contacted
    # for the number of seconds specified below.
    #idle_timelimit 3600

    # Filter to AND with uid=%s
    #pam_filter objectclass=account

    # The user ID attribute (defaults to uid)
    #pam_login_attribute uid #HECTOR: Originalmente esto estaba comentado

    # Search the root DSE for the password policy (works
    # with Netscape Directory Server)
    #pam_lookup_policy yes

    # Check the 'host' attribute for access control
    # Default is no; if set to yes, and user has no
    # value for the host attribute, and pam_ldap is
    # configured for account management (authorization)
    # then the user will not be allowed to login.
    #pam_check_host_attr yes

    # Check the 'authorizedService' attribute for access
    # control
    # Default is no; if set to yes, and the user has no
    # value for the authorizedService attribute, and
    # pam_ldap is configured for account management
    # (authorization) then the user will not be allowed
    # to login.
    #pam_check_service_attr yes

    # Group to enforce membership of
    #pam_groupdn cn=PAM,ou=Groups,dc=padl,dc=com

    # Group member attribute
    #pam_member_attribute uniquemember

    # Specify a minium or maximum UID number allowed
    #pam_min_uid 1000 #HECTOR: Originalmente esto estaba comentado y a 0
    #pam_max_uid 0

    # Template login attribute, default template user
    # (can be overriden by value of former attribute
    # in user's entry)
    #pam_login_attribute userPrincipalName
    #pam_template_login_attribute uid
    #pam_template_login nobody

    # HEADS UP: the pam_crypt, pam_nds_passwd,
    # and pam_ad_passwd options are no
    # longer supported.
    #
    # Do not hash the password at all; presume
    # the directory server will do it, if
    # necessary. This is the default.
    #pam_password md5 #HECTOR: Esto no me acuerdo de como estaba:
    probablemente comentado

    # Hash password locally; required for University of
    # Michigan LDAP server, and works with Netscape
    # Directory Server if you're using the UNIX-Crypt
    # hash mechanism and not using the NT Synchronization
    # service.
    #pam_password crypt #HECTOR: Antes estaba comentado

    # Remove old password first, then update in
    # cleartext. Necessary for use with Novell
    # Directory Services (NDS)
    #pam_password clear_remove_old
    #pam_password nds

    # RACF is an alias for the above. For use with
    # IBM RACF
    #pam_password racf

    # Update Active Directory password, by
    # creating Unicode password and updating
    # unicodePwd attribute.
    #pam_password ad

    # Use the OpenLDAP password change
    # extended operation to update the password.
    #pam_password exop #HECTOR: He visto que en una presentacion que me
    baje del Emule activaban esto...

    # Redirect users to a URL or somesuch on password
    # changes.
    #pam_password_prohibit_message Please visit http://internal to change
    your password.

    # RFC2307bis naming contexts
    # Syntax:
    # nss_base_XXX base?scope?filter
    # where scope is {base,one,sub}
    # and filter is a filter to be &'d with the
    # default filter.
    # You can omit the suffix eg:
    # nss_base_passwd ou=People,
    # to append the default base DN but this
    # may incur a small performance impact.
    #nss_base_passwd ou=People,dc=padl,dc=com?one
    nss_base_passwd ou=People,dc=jome?one #HECTOR: La linea original es
    la de arriba
    #nss_base_shadow ou=People,dc=padl,dc=com?one
    nss_base_shadow ou=People,dc=jome?one #HECTOR: La linea original es
    la de arriba
    #nss_base_group ou=Group,dc=padl,dc=com?one
    nss_base_group ou=Group,dc=jome?one #HECTOR: La linea original es
    la de arriba
    #nss_base_hosts ou=Hosts,dc=padl,dc=com?one
    #nss_base_services ou=Services,dc=padl,dc=com?one
    #nss_base_networks ou=Networks,dc=padl,dc=com?one
    #nss_base_protocols ou=Protocols,dc=padl,dc=com?one
    #nss_base_rpc ou=Rpc,dc=padl,dc=com?one
    #nss_base_ethers ou=Ethers,dc=padl,dc=com?one
    #nss_base_netmasks ou=Networks,dc=padl,dc=com?ne
    #nss_base_bootparams ou=Ethers,dc=padl,dc=com?one
    #nss_base_aliases ou=Aliases,dc=padl,dc=com?one
    #nss_base_netgroup ou=Netgroup,dc=padl,dc=com?one

    # attribute/objectclass mapping
    # Syntax:
    #nss_map_attribute rfc2307attribute mapped_attribute
    #nss_map_objectclass rfc2307objectclass mapped_objectclass

    # configure --enable-nds is no longer supported.
    # NDS mappings
    #nss_map_attribute uniqueMember member

    # Services for UNIX 3.5 mappings
    #nss_map_objectclass posixAccount User
    #nss_map_objectclass shadowAccount User
    #nss_map_attribute uid msSFU30Name
    #nss_map_attribute uniqueMember msSFU30PosixMember
    #nss_map_attribute userPassword msSFU30Password
    #nss_map_attribute homeDirectory msSFU30HomeDirectory
    #nss_map_attribute homeDirectory msSFUHomeDirectory
    #nss_map_objectclass posixGroup Group
    #pam_login_attribute msSFU30Name
    #pam_filter objectclass=User
    #pam_password ad

    # configure --enable-mssfu-schema is no longer supported.
    # Services for UNIX 2.0 mappings
    #nss_map_objectclass posixAccount User
    #nss_map_objectclass shadowAccount user
    #nss_map_attribute uid msSFUName
    #nss_map_attribute uniqueMember posixMember
    #nss_map_attribute userPassword msSFUPassword
    #nss_map_attribute homeDirectory msSFUHomeDirectory
    #nss_map_attribute shadowLastChange pwdLastSet
    #nss_map_objectclass posixGroup Group
    #nss_map_attribute cn msSFUName
    #pam_login_attribute msSFUName
    #pam_filter objectclass=User
    #pam_password ad

    # RFC 2307 (AD) mappings
    #nss_map_objectclass posixAccount user
    #nss_map_objectclass shadowAccount user
    #nss_map_attribute uid sAMAccountName
    #nss_map_attribute homeDirectory unixHomeDirectory
    #nss_map_attribute shadowLastChange pwdLastSet
    #nss_map_objectclass posixGroup group
    #nss_map_attribute uniqueMember member
    #pam_login_attribute sAMAccountName
    #pam_filter objectclass=User
    #pam_password ad

    # configure --enable-authpassword is no longer supported
    # AuthPassword mappings
    #nss_map_attribute userPassword authPassword

    # AIX SecureWay mappings
    #nss_map_objectclass posixAccount aixAccount
    #nss_base_passwd ou=aixaccount,?one
    #nss_map_attribute uid userName
    #nss_map_attribute gidNumber gid
    #nss_map_attribute uidNumber uid
    #nss_map_attribute userPassword passwordChar
    #nss_map_objectclass posixGroup aixAccessGroup
    #nss_base_group ou=aixgroup,?one
    #nss_map_attribute cn groupName
    #nss_map_attribute uniqueMember member
    #pam_login_attribute userName
    #pam_filter objectclass=aixAccount
    #pam_password clear

    # HECTOR: A partir de aqui hay muchas cosas de SSL/TLS

    # Netscape SDK LDAPS
    #ssl on #HECTOR: Originalemnte esto estaba comentado
    #ssl off

    # Netscape SDK SSL options
    #sslpath /etc/ssl/certs
    #sslpath /var/lib/ldap/certs/Client #HECTOR: Originalmente esto esta
    comentado y apuntaba a /etc/ssl/certs (ver linea anterior)
    # OpenLDAP SSL mechanism
    # start_tls mechanism uses the normal LDAP port, LDAPS typically 636
    #ssl start_tls
    ssl start_tls #HECTOR: Originalmente estaba comentado (ver linea anterior)
    #ssl on

    # OpenLDAP SSL options
    # Require and verify server certificate (yes/no)
    # Default is to use libldap's default behavior, which can be configured in
    # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for
    # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes".
    tls_checkpeer yes #HECTOR: Originalmente estaba comentado
    #tls_checkpeer no #HECTOR: Originalmente estaba comentado y a 'yes'

    # CA certificates for server certificate verification
    # At least one of these are required if tls_checkpeer is "yes"
    #tls_cacertfile /etc/ssl/ca.cert
    #tls_cacertfile /var/lib/ldap/certs/cacert.pem #HECTOR: Para ver como
    estaba esto, mirar la linea anterior (es la original)
    #tls_cacertdir /var/lib/ldap/certs #HECTOR: Originalmente esto estaba
    comentado y apuntando a /etc/ssl/certs

    # Seed the PRNG if /dev/urandom is not provided
    #tls_randfile /var/run/egd-pool

    # SSL cipher suite
    # See man ciphers for syntax
    #tls_ciphers TLSv1

    # Client certificate and key
    # Use these, if your server requires client authentication.
    #tls_cert /var/lib/ldap/certs/Client/ldap.client.pem #HECTOR:
    Originalmente estaba comentado
    #tls_key /var/lib/ldap/certs/Client/ldap.client.key.pem #HECTOR:
    Originalmente estaba comentado

    # Disable SASL security layers. This is needed for AD.
    #sasl_secprops maxssf=0

    # Override the default Kerberos ticket cache location.
    #krb5_ccname FILE:/etc/.ldapcache

    # SASL mechanism for PAM authentication - use is experimental
    # at present and does not support password policy control
    #pam_sasl_mech DIGEST-MD5

    -----------------------------------------------------------------------------------------------

    2008/2/23, Jamrock :
    > >Hector Blanco" wrote in message

    > news:86e693810802221551h7feaf5e8n2a504646b64ac900@ mail.gmail.com...
    >
    > > Hello people...
    > >
    > > I had to sign up in the list because I don't know what else I could
    > > do... I can't find my error anywhere!!
    > >

    >
    >
    > Hi Hector,
    >
    > Can you post your /etc/ldap.conf file and your /etc/nsswitch.conf file?
    > Are there any other ldap.conf files in the /etc directory?
    >
    > Are you able to add users to the the domain?
    >
    > Please post the output from getent passwd group.
    >
    >
    >


    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  8. Fwd: [Samba] Re: Windows 2000 pro doesn't join a domain with Samba+Ldap(linux)

    Well... just a new sympthom:

    As Jamrock was asking about nsswitch and so, I thought that maybe I
    should resolve the hosts with Ldap too (it makes sense, doesn't it? )
    but no... It doesn't work. I arranged everything to solve the Hosts
    with Ldap, but no change. I also added the IpHost object class to the
    "enano$" ldap entry, for being able to have this:

    -------------------
    root@xxxx:~# getent hosts
    127.0.0.1 localhost
    192.168.1.30 xxxx
    127.0.0.1 ip6-localhost ip6-loopback
    192.168.1.34 enano$ enano
    --------------------
    The last entry (enano's one) is only in Ldap, and I was able to ping it:
    ______________________
    root@xxxx:~# ping enano
    PING enano$ (192.168.1.34) 56(84) bytes of data.
    64 bytes from enano$ (192.168.1.34): icmp_seq=1 ttl=128 time=0.672 ms
    ------------------------------------

    I also changed the order of resolving in nsswhitch.conf, for Ldap to
    be the first (I had 2 "root" users in passwd, so I tried to make the
    "root" Ldap user the first, but nothing). Still seeing this error in
    /var/log/samba/samba.log
    [2008/02/23 18:15:09, 3] passdb/pdb_interface.cdb_default_create_user(354)
    pdb_default_create_user: failed to create a new user structure:
    NT_STATUS_NO_SUCH_USER

    If I only knew what user it is trying to create... that may help :S

    There's something that surprises me. If I look at "getent passwd" I
    see two "root" users:
    ----------------------
    hector@xxxx:/var/log/samba$ getent passwd
    root:x:0:0:Admin:/root:/bin/bash
    [...]
    root:x:0:0:Netbios Domain Administrator:/tmp:/bin/false
    --------------------------
    Now, (with my current nsswitch.conf file as it is) the first one is in
    "files" and the second is in "ldap". The "gecos" field should be
    "Admin" for the first one and "Netbios Domain Administrator" for the
    second, right?. Then... How doest it come that in
    /var/log/samba/samba.log I get this entry:

    [2008/02/23 18:15:06, 3] smbd/password.c:register_vuid(280)
    User name: root Real name: root

    Shouldn't the "real name" be "Admin" or "Netbios Domain Administrator"?

    And another thing that surprises me (probably is surprising because I
    don't have the concepts very clear in my mind) is the following:

    [2008/02/23 18:15:06, 3] auth/auth.c:check_ntlm_password(221)
    check_ntlm_password: Checking password for unmapped user
    [jome]\[root]@[ENANO] with the new password interface

    It seems that it's trying to check root@Enano... Is that right?? I
    guess it must be, because several lines after that, it says:

    [2008/02/23 18:15:06, 3] auth/auth.c:check_ntlm_password(270)
    check_ntlm_password: sam authentication for user [root] succeeded








    ---------- Forwarded message ----------
    From: Hector Blanco
    Date: 23-feb-2008 17:38
    Subject: Re: [Samba] Re: Windows 2000 pro doesn't join a domain with
    Samba+Ldap(linux)
    To:
    Cc: samba@lists.samba.org


    I hope you can get attachments!!... I'll send the files you asked me
    for as attachment and I'll paste them in the message body too, but I
    think it's easier to read if they come in separated files...

    Anyway, I also want to thank the interest to all the people who are
    trying to help me... Thank you guys!

    I forgot to say that I am able to login with a Linux client. In the
    same client computer (the one called "Enano") in which I've got the
    Win2000, I've got a Debian too. That Debian is able to properly login
    with users that only exist in the "Xxxx" server Ldap database (the
    user "test", for instance)

    And adding users to the domain... yes, I think I can... if I can
    create machine accounts, it must be the same for normal users,
    right?... I mean: I can execute succesffuly the "smldap-useradd"
    command... I hope this is what you wanted to know

    I don't think I have any other ldap.conf files in /etc/... I have a
    whole directory called "/ldap" under "/etc", with information about
    the Ldap server and some information for how a client hat to connecto
    to a server (in the /etc/ldap/ldap.conf file), but no... no more stuff
    about the "client" in /etc/ (I don't have pam_ldap.conf or
    libnss-ldap.conf, if that's what you mean... I guess everything has
    been merged into that "/etc/ldap.conf" file)

    I am posting the output for getent group command (of the server):

    ------------------- #getent group ---------------------
    hector@xxxx:~$ getent group
    root:x:0:
    daemon:x:1:
    bin:x:2:
    sys:x:3:
    adm:x:4:hector
    tty:x:5:
    disk:x:6:
    lp:x:7:
    mail:x:8:
    news:x:9:
    uucp:x:10:
    man:x:12:
    proxy:x:13:
    kmem:x:15:
    dialout:x:20:hector
    fax:x:21:
    voice:x:22:
    cdrom:x:24:haldaemon,hector
    floppy:x:25:haldaemon,hector
    tape:x:26:
    sudo:x:27:
    audio:x:29:hector
    dip:x:30:hector
    www-data:x:33:
    backup:x:34:
    operator:x:37:
    list:x:38:
    irc:x:39:
    src:x:40:
    gnats:x:41:
    shadow:x:42:
    utmp:x:43:
    video:x:44:hector
    sasl:x:45:
    plugdev:x:46:haldaemon,hector
    staff:x:50:
    games:x:60:
    users:x:100:
    nogroup:x:65534:
    dhcp:x:101:
    syslog:x:102:
    klog:x:103:
    scanner:x:104:hplip,hector
    nvram:x:105:
    fuse:x:106:
    ssl-cert:x:107:
    lpadmin:x:108:hector
    admin:x:109:hector
    crontab:x:110:
    ssh:x:111:
    avahi-autoipd:x:112:
    messagebus:x:113:
    avahi:x:114:
    netdev:x:115:hector
    gdm:x:116:
    haldaemon:x:117:
    powerdev:x:118:haldaemon,hector
    slocate:x:119:
    hector:x:1000:
    openldap:x:120:
    test:*:2000:test
    Domain Admins:*:512:root
    Domain Users:*:513:
    Domain Guests:*:514:
    Domain Computers:*:515:
    Administrators:*:544:
    Account Operators:*:548:
    Print Operators:*:550:
    Backup Operators:*:551:
    Replicators:*:552:
    -----------------------------------------------------------------

    The last 10 groups from "test" to "Replicators" only exist in the Ldap
    database, and all the groups starting with a capital letter (from
    Domain Admins to Replicators) were created by smbldap-populate

    Thank you all!

    Under these lines I'm writing the contents of the two files you asked me:
    /etc/nsswitch.conf and
    /etc/ldap.conf



    ---------------------------- /etc/nsswitch.conf ------------------------
    # /etc/nsswitch.conf
    #
    # Example configuration of GNU Name Service Switch functionality.
    # If you have the `glibc-doc-reference' and `info' packages installed, try:
    # `info libc "Name Service Switch"' for information about this file.

    passwd: files ldap #compat
    group: files ldap #compat
    shadow: files ldap #files ldap #compat

    hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
    networks: files

    protocols: db files
    services: db files
    ethers: db files
    rpc: db files

    netgroup: nis
    ---------------------------------------------------------------


    ------------------------------------ /etc/ldap.conf ---------------------------
    ###DEBCONF###
    ##
    ## Configuration of this file will be managed by debconf as long as the
    ## first line of the file says '###DEBCONF###'
    ##
    ## You should use dpkg-reconfigure to configure this file via debconf
    ##

    #
    # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $
    #
    # This is the configuration file for the LDAP nameservice
    # switch library and the LDAP PAM module.
    #
    # PADL Software
    # http://www.padl.com
    #

    # Your LDAP server. Must be resolvable without using LDAP.
    # Multiple hosts may be specified, each separated by a
    # space. How long nss_ldap takes to failover depends on
    # whether your LDAP client library supports configurable
    # network or connect timeouts (see bind_timelimit).
    host xxxx #HECTOR: Original

    # The distinguished name of the search base.
    base dc=jome

    # Another way to specify your LDAP server is to provide an
    # uri with the server name. This allows to use
    # Unix Domain Sockets to connect to a local LDAP Server.
    #uri ldap://127.0.0.1/
    #uri ldaps://127.0.0.1/
    #uri ldapi://%2fvar%2frun%2fldapi_sock/
    # Note: %2f encodes the '/' used as directory separator
    #uri ldap://xxxx:389/ #HECTOR: Esta linea no estaba. Descubri con
    horror que si se activa, casca

    # The LDAP version to use (defaults to 3
    # if supported by client library)
    ldap_version 3

    # The distinguished name to bind to the server with.
    # Optional: default is to bind anonymously.
    #binddn cn=proxyuser,dc=padl,dc=com

    # The credentials to bind with.
    # Optional: default is no credential.
    #bindpw secret

    # The distinguished name to bind to the server with
    # if the effective user ID is root. Password is
    # stored in /etc/ldap.secret (mode 600)
    rootbinddn cn=Admin,dc=jome

    # The port.
    # Optional: default is 389.
    #port 389
    #port 636 #HECTOR: Es seguro

    # The search scope.
    #scope sub
    #scope one
    #scope base

    # Search timelimit
    #timelimit 30

    # Bind/connect timelimit
    #bind_timelimit 30

    # Reconnect policy: hard (default) will retry connecting to
    # the software with exponential backoff, soft will fail
    # immediately.
    #bind_policy hard
    #bind_policy soft #HECTOR: Originalmente era la linea anterior... yo,
    yo... lo lei en un tutorial
    (http://www.debuntu.org/ldap-server-a...dap-clients-p2)

    # Idle timelimit; client will close connections
    # (nss_ldap only) if the server has not been contacted
    # for the number of seconds specified below.
    #idle_timelimit 3600

    # Filter to AND with uid=%s
    #pam_filter objectclass=account

    # The user ID attribute (defaults to uid)
    #pam_login_attribute uid #HECTOR: Originalmente esto
    estaba comentado

    # Search the root DSE for the password policy (works
    # with Netscape Directory Server)
    #pam_lookup_policy yes

    # Check the 'host' attribute for access control
    # Default is no; if set to yes, and user has no
    # value for the host attribute, and pam_ldap is
    # configured for account management (authorization)
    # then the user will not be allowed to login.
    #pam_check_host_attr yes

    # Check the 'authorizedService' attribute for access
    # control
    # Default is no; if set to yes, and the user has no
    # value for the authorizedService attribute, and
    # pam_ldap is configured for account management
    # (authorization) then the user will not be allowed
    # to login.
    #pam_check_service_attr yes

    # Group to enforce membership of
    #pam_groupdn cn=PAM,ou=Groups,dc=padl,dc=com

    # Group member attribute
    #pam_member_attribute uniquemember

    # Specify a minium or maximum UID number allowed
    #pam_min_uid 1000 #HECTOR: Originalmente esto estaba comentado y a 0
    #pam_max_uid 0

    # Template login attribute, default template user
    # (can be overriden by value of former attribute
    # in user's entry)
    #pam_login_attribute userPrincipalName
    #pam_template_login_attribute uid
    #pam_template_login nobody

    # HEADS UP: the pam_crypt, pam_nds_passwd,
    # and pam_ad_passwd options are no
    # longer supported.
    #
    # Do not hash the password at all; presume
    # the directory server will do it, if
    # necessary. This is the default.
    #pam_password md5 #HECTOR: Esto no me acuerdo de como estaba:
    probablemente comentado

    # Hash password locally; required for University of
    # Michigan LDAP server, and works with Netscape
    # Directory Server if you're using the UNIX-Crypt
    # hash mechanism and not using the NT Synchronization
    # service.
    #pam_password crypt #HECTOR: Antes estaba comentado

    # Remove old password first, then update in
    # cleartext. Necessary for use with Novell
    # Directory Services (NDS)
    #pam_password clear_remove_old
    #pam_password nds

    # RACF is an alias for the above. For use with
    # IBM RACF
    #pam_password racf

    # Update Active Directory password, by
    # creating Unicode password and updating
    # unicodePwd attribute.
    #pam_password ad

    # Use the OpenLDAP password change
    # extended operation to update the password.
    #pam_password exop #HECTOR: He visto que en una presentacion que me
    baje del Emule activaban esto...

    # Redirect users to a URL or somesuch on password
    # changes.
    #pam_password_prohibit_message Please visit http://internal to change
    your password.

    # RFC2307bis naming contexts
    # Syntax:
    # nss_base_XXX base?scope?filter
    # where scope is {base,one,sub}
    # and filter is a filter to be &'d with the
    # default filter.
    # You can omit the suffix eg:
    # nss_base_passwd ou=People,
    # to append the default base DN but this
    # may incur a small performance impact.
    #nss_base_passwd ou=People,dc=padl,dc=com?one
    nss_base_passwd ou=People,dc=jome?one #HECTOR: La
    linea original es
    la de arriba
    #nss_base_shadow ou=People,dc=padl,dc=com?one
    nss_base_shadow ou=People,dc=jome?one #HECTOR: La
    linea original es
    la de arriba
    #nss_base_group ou=Group,dc=padl,dc=com?one
    nss_base_group ou=Group,dc=jome?one #HECTOR: La
    linea original es
    la de arriba
    #nss_base_hosts ou=Hosts,dc=padl,dc=com?one
    #nss_base_services ou=Services,dc=padl,dc=com?one
    #nss_base_networks ou=Networks,dc=padl,dc=com?one
    #nss_base_protocols ou=Protocols,dc=padl,dc=com?one
    #nss_base_rpc ou=Rpc,dc=padl,dc=com?one
    #nss_base_ethers ou=Ethers,dc=padl,dc=com?one
    #nss_base_netmasks ou=Networks,dc=padl,dc=com?ne
    #nss_base_bootparams ou=Ethers,dc=padl,dc=com?one
    #nss_base_aliases ou=Aliases,dc=padl,dc=com?one
    #nss_base_netgroup ou=Netgroup,dc=padl,dc=com?one

    # attribute/objectclass mapping
    # Syntax:
    #nss_map_attribute rfc2307attribute mapped_attribute
    #nss_map_objectclass rfc2307objectclass mapped_objectclass

    # configure --enable-nds is no longer supported.
    # NDS mappings
    #nss_map_attribute uniqueMember member

    # Services for UNIX 3.5 mappings
    #nss_map_objectclass posixAccount User
    #nss_map_objectclass shadowAccount User
    #nss_map_attribute uid msSFU30Name
    #nss_map_attribute uniqueMember msSFU30PosixMember
    #nss_map_attribute userPassword msSFU30Password
    #nss_map_attribute homeDirectory msSFU30HomeDirectory
    #nss_map_attribute homeDirectory msSFUHomeDirectory
    #nss_map_objectclass posixGroup Group
    #pam_login_attribute msSFU30Name
    #pam_filter objectclass=User
    #pam_password ad

    # configure --enable-mssfu-schema is no longer supported.
    # Services for UNIX 2.0 mappings
    #nss_map_objectclass posixAccount User
    #nss_map_objectclass shadowAccount user
    #nss_map_attribute uid msSFUName
    #nss_map_attribute uniqueMember posixMember
    #nss_map_attribute userPassword msSFUPassword
    #nss_map_attribute homeDirectory msSFUHomeDirectory
    #nss_map_attribute shadowLastChange pwdLastSet
    #nss_map_objectclass posixGroup Group
    #nss_map_attribute cn msSFUName
    #pam_login_attribute msSFUName
    #pam_filter objectclass=User
    #pam_password ad

    # RFC 2307 (AD) mappings
    #nss_map_objectclass posixAccount user
    #nss_map_objectclass shadowAccount user
    #nss_map_attribute uid sAMAccountName
    #nss_map_attribute homeDirectory unixHomeDirectory
    #nss_map_attribute shadowLastChange pwdLastSet
    #nss_map_objectclass posixGroup group
    #nss_map_attribute uniqueMember member
    #pam_login_attribute sAMAccountName
    #pam_filter objectclass=User
    #pam_password ad

    # configure --enable-authpassword is no longer supported
    # AuthPassword mappings
    #nss_map_attribute userPassword authPassword

    # AIX SecureWay mappings
    #nss_map_objectclass posixAccount aixAccount
    #nss_base_passwd ou=aixaccount,?one
    #nss_map_attribute uid userName
    #nss_map_attribute gidNumber gid
    #nss_map_attribute uidNumber uid
    #nss_map_attribute userPassword passwordChar
    #nss_map_objectclass posixGroup aixAccessGroup
    #nss_base_group ou=aixgroup,?one
    #nss_map_attribute cn groupName
    #nss_map_attribute uniqueMember member
    #pam_login_attribute userName
    #pam_filter objectclass=aixAccount
    #pam_password clear

    # HECTOR: A partir de aqui hay muchas cosas de SSL/TLS

    # Netscape SDK LDAPS
    #ssl on #HECTOR: Originalemnte esto estaba comentado
    #ssl off

    # Netscape SDK SSL options
    #sslpath /etc/ssl/certs
    #sslpath /var/lib/ldap/certs/Client #HECTOR: Originalmente esto esta
    comentado y apuntaba a /etc/ssl/certs (ver linea anterior)
    # OpenLDAP SSL mechanism
    # start_tls mechanism uses the normal LDAP port, LDAPS typically 636
    #ssl start_tls
    ssl start_tls #HECTOR: Originalmente estaba comentado (ver
    linea anterior)
    #ssl on

    # OpenLDAP SSL options
    # Require and verify server certificate (yes/no)
    # Default is to use libldap's default behavior, which can be configured in
    # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for
    # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes".
    tls_checkpeer yes #HECTOR: Originalmente estaba comentado
    #tls_checkpeer no #HECTOR: Originalmente estaba comentado y a 'yes'

    # CA certificates for server certificate verification
    # At least one of these are required if tls_checkpeer is "yes"
    #tls_cacertfile /etc/ssl/ca.cert
    #tls_cacertfile /var/lib/ldap/certs/cacert.pem #HECTOR: Para ver como
    estaba esto, mirar la linea anterior (es la original)
    #tls_cacertdir /var/lib/ldap/certs #HECTOR: Originalmente esto estaba
    comentado y apuntando a /etc/ssl/certs

    # Seed the PRNG if /dev/urandom is not provided
    #tls_randfile /var/run/egd-pool

    # SSL cipher suite
    # See man ciphers for syntax
    #tls_ciphers TLSv1

    # Client certificate and key
    # Use these, if your server requires client authentication.
    #tls_cert /var/lib/ldap/certs/Client/ldap.client.pem #HECTOR:
    Originalmente estaba comentado
    #tls_key /var/lib/ldap/certs/Client/ldap.client.key.pem #HECTOR:
    Originalmente estaba comentado

    # Disable SASL security layers. This is needed for AD.
    #sasl_secprops maxssf=0

    # Override the default Kerberos ticket cache location.
    #krb5_ccname FILE:/etc/.ldapcache

    # SASL mechanism for PAM authentication - use is experimental
    # at present and does not support password policy control
    #pam_sasl_mech DIGEST-MD5

    -----------------------------------------------------------------------------------------------

    2008/2/23, Jamrock :

    > >Hector Blanco" wrote in message

    > news:86e693810802221551h7feaf5e8n2a504646b64ac900@ mail.gmail.com...
    >
    > > Hello people...
    > >
    > > I had to sign up in the list because I don't know what else I could
    > > do... I can't find my error anywhere!!
    > >

    >
    >
    > Hi Hector,
    >
    > Can you post your /etc/ldap.conf file and your /etc/nsswitch.conf file?
    > Are there any other ldap.conf files in the /etc directory?
    >
    > Are you able to add users to the the domain?
    >
    > Please post the output from getent passwd group.
    >
    >
    >


    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  9. Re: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    Hi hector.

    I don't know if you still wondering about your problem as it was a year ago, but if it is, i have the solution. I hope it will be helpfull for you and for others.

    You noticed right about the fact that there is no account found for the machine by "getent passwd".

    Using a network sniffer helps to find out what is wrong and what to do.

    When you are trying to join the Domain, the smbldap-tools created a record for your computer in the LDAP database. The place this record is created in your LDAP tree is configured in the smbldap.conf . I suppose it is for you :
    computersdn="ou=Hosts,${suffix}"

    But when Samba try to retreive this record, it ask nsswitch to find it as a user account, according to the ldap.conf (or libnss-ldap.conf):
    nss_base_passwd ou=People,dc=jome?one

    So that your computer record can not be found in that branch of the LDAP tree.

    The way i solved it, which is not elegant, but works, is to change this line by :
    nss_base_passwd dc=jome?sub

  10. Re: [Samba] Windows 2000 pro doesn't join a domain with Samba+Ldap (linux)

    A better way to solve it is to have 2 nss_base_passwd definition (yes it works).

    nss_base_passwd ou=People,dc=jome?one
    nss_base_passwd ou=Hosts,dc=jome?one

+ Reply to Thread