I have te following bug:
I set up a PDC and a BDC using Samba 3.0.2a using LDAP as a backend (PDC has
the master LDAP as backend and BDC has the slave LDAP as backend).
At first things work fine.
If I shut down the Master, windows machines are still able to log in
authenticating against the BDC.
Matthias Eichler wrote:
members server cant find bdc for logon service
Hello,
I have exactly the same problem you have. I wonder i you found a solution.
I came to the conclusion it is a bug in Samba.
I have a setup very similar to yours (Samba PDC and BDC). If I have a
Windows member server I
I am using the following in smb.conf.
unix charset = ISO-8859-1
It works fine for characters used in spanish. Should work fine for you.
Michel Jouvin wrote:
Hi,
I recently upgraded from 2.2.8 to 3.0.1 (keeping the same configuration
file). As a consequence, file names containing a
Beast wrote:
On Thu, 15 Jan 2004 22:54:54 -0400
Vegeta [EMAIL PROTECTED] wrote:
No, the key is not the smb.conf file but the ldap.conf file. Samba seems
to look for machine accounts among users returned by the Name Service
Switch (what you get when you run the command 'getent passwd
Beast wrote:
I'm just storing machine accounts under
ou=computer,ou=site,dc=domain,dc=com and it works.
Tested with W2K sp2 and W2K sp3, recreating from fresh ldif 2 times were
never failed. Im sure it is 'stable' right now :-)
'works' means it was able to add machine trust on-the-fly,
On Thursday 15 January 2004 10:32, you wrote:
Hello Vegeta,
I've looked at your post at samba mailing list.
Same as you are, I am having a nightmare making a windows 2000
pro to logon to my domain.
But unlike you, smbldap-tools worked fine-ish for me. They
have populated the database
Andrew Bartlett wrote:
On Thu, Jan 15, 2004 at 09:42:53AM -0400, Vegeta wrote:
Beast wrote:
I'm just storing machine accounts under
ou=computer,ou=site,dc=domain,dc=com and it works.
Tested with W2K sp2 and W2K sp3, recreating from fresh ldif 2 times
were never failed. Im sure
OK.
I am starting to believe that Samba 3.0.x is not stable.
At least, the documentation for Samba as PDC with OpenLDAP backend (which is
what I have been trying to do for four days) is crap.
All the documentation for 3.0.x is mixed with 2.2.x. Most documents start as
instructions for 3.0.x but
Craig White wrote:
On Wed, 2004-01-14 at 19:13, Vegeta wrote:
I expect this story could help others trying to do the same I am doing.
The next battle will be configuring a BDC, but that will be another day.
--
The truth is, with 3.0.0 on RH AS 3, I got it running, ldap backend
Sundaram Ramasamy wrote:
On Sun, 11 Jan 2004 15:01:27 -0400
Vegeta [EMAIL PROTECTED] wrote:
I found in an older post in the list that there is a bug in Samba 3.
It says that Samba 3 does not search in the ou=Computers
(ou=Computadoras in
my case) so one has to put the machines in the ou
than I am. I haven't been able to
add W2K machines to the domain.
Can you tell me what you did to add them?
On Monday 12 January 2004 13:32, Sundaram Ramasamy wrote:
Vegeta,
I had problem while adding windows 2000 machine to domain with
ou=Computer. As per John advice I moved computer account
I found in an older post in the list that there is a bug in Samba 3.
It says that Samba 3 does not search in the ou=Computers (ou=Computadoras in
my case) so one has to put the machines in the ou=People (ou=Personas in my
case) section of the LDAP server.
I did that and smbpasswd -a -m worked.
12 matches
Mail list logo
