[Samba] Domain logons w/ LDAP backend
wheisinger at semcowindows.com
Fri Apr 4 13:04:42 GMT 2008
I would advise against using Samba 3.0.28a if you are using domain
trusts. I spent weeks trying to configure trusts with 3.0.28a and it
didn't work. I went back to samba 3.0.26a and it worked like a charm.
John Drescher wrote:
> On Thu, Apr 3, 2008 at 8:28 PM, Tom Smith <aliase573201 at mac.com> wrote:
>> I have multiple Samba servers working very well using the tdbsam backend.
>> The number of servers is becoming harder to manage now so I began testing an
>> LDAP-based Samba server. Everything works great except when a workstation
>> tries to login to the domain...
>> All users are able to login just fine when accessing network shares.
>> Workstation are able to join the domain. But upon reboot, they're not able
>> to login to the domain.
>> Here's what I'm using:
>> CentOS 4
>> Samba 3.0.10
>> OpenLDAP 2.2.13
>> Windows XP Pro
>> The error message I get on the client is: "Windows cannot connect to the
>> domain either because the domain controller is down or otherwise unavailable
>> or because your computer account was not found." This happens on every
>> My server logs are filled with these messages: "[2008/04/01 13:48:22, 0]
>> lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport
>> endpoint is not connected"
>> I've been trying to find a solution to this for (literally) months. I
>> really, really, really need to get this working--I currently have four
>> office that need to be connected under the same Samba domain, the all
>> already have Samba servers installed but under different domains. And we're
>> gearing up for another growth spurt in the next six to twelve months that
>> will add to this number, which makes it even that more important.
>> Any advice or pointers for resolving this will be very much appreciated!
> Can you please update your samba? That version is > 3 years old. The
> current samba is 3.0.28a.
More information about the samba