similar to: Samba 3 + ldap "Domain Users" Can't Logon....

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

I already have LDAP setup fro other purposes and I'm using {MD5} passwords in ou=people,dc=mycompany,dc=com What are the correct settings in smb.conf? is is possible to use stored md5 passwords? Thanks in advance Jeff Saxton

Partially Solved: http://lists.samba.org/archive/samba/2004-May/085233.html thanks om Wisnu... Is there anyone succes with place Users and Computers in different ou's ? regards reza -----Original Message----- From: Mohammad Reza Sent: Thu 7/22/2004 1:56 PM To: Craig White; idx-smbldap-tools@lists.IDEALX.org; samba@lists.samba.org Cc: Subject: [idx-smbldap-tools ] RE: [Samba] Samba+LDAP

Hi , I use Samba 3.5 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

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:

SNIP > > > How to know the NetBIOS name in Linux? Linux does not care. Only Windows cares. > > > > The name of my domain is: DOMAINE.CH > The name of my server: SERVEUR-TPI The posix name of the server does not matter. Nor does the DNS name as it can have more than one DNS name. You need to work with Samba as a somewhat separate entity. It is simply easier to match

Hi All, I have recently successfully configured Samba 3.3.15 and OpenLDAP as my offices PDC. I would like to disable the roaming profiles capability but it appears that no matter what I said, it is being ignored by Samba. First is my relevant snippet for the Logon Path and Logon Home being empty as described in the documentation. Then, following that, is my entire smb.conf -- please let me

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

> > > I do not understand, I will have a hostname and NetBIOS name > different? Yes. > > > > So > > -- Domain = SAMBA > > it'll be my name NETBIOS, and > > -- Realm = TPI.DOMAINE.CH-SERVER > > will my machine name + my domain? > > Thank you > ________________________________ > De : tms3 at tms3.com [tms3 at tms3.com] > Date

I'm using Samba 3.0.3 on Fedora Core 2 with OpenLDAP 2.1.29 for a backend. I'm getting to typical "The user name could not be found." error upon trying to join a Windows box. I've gone through every digest on lists.samba.org and other sites and nothing has worked yet. Any suggestions: Here's what I've done so far: 1. Installed everything via RPMS: [root@smbtest

After, oh, six months of attempts here and there to read everyone's experiences with Samba/LDAP and inability for a windows 2000/XP machine to join the domain, I finally discovered what was not working properly. In my smb.conf I put: add machine script = /usr/local/sbin/smbldap-useradd -w "%u" As instructed by many How-to's and Idealx. However, I thought to myself, %m

hi folks, i hope you can help me!!! i'm using samba v3.0.14a (sernet) on debian sarge. openldap v2 is my backend, smbldap-tools 0.8.4 (patched for our organization). when adding a user via usrmgr.exe to an existing domain group i get the following error: [in usrgmr] The following error occured changing the properies of the user xxx User does not belong to this group [in smbd.logs]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am trying to rename a computer on my samba domain but it fails telling me I hadn't rights to do it. Obviously, I use the same admin account (root) than the one which add this computer on the domain some seconds before. I am using samba 3.0.24 on Debian etch with a openldap SAM backend and smbldap-tools scripts using these conf params :

I have a Samba PDC with LDAP running on a CentOs 4.4 machine. When I first had it all configured, everything worked fine, but now for some reason, login scripts will not run on the client (even though they have access to the shares the login script is trying to map) and I cannot join client machines to the domain automatically using the Windows XP Network Identification Wizard. When I try to

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

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

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