I had inquired about this in that past and was not given a direct
answer. For whatever it is worth, here are my findings, also in response
to this thread
http://lists.samba.org/archive/samba-ntdom/2001-January/017142.html
I just discovered that you should make sure that samba has not generated
a
Hello,
This is the 3rd time I'm sending the message.
I've just upgraded from samba3-alpha23 to samba3.0.0 release. I'm
running samba with an LDAP backend and I used the convertSambaAccount
conversion script, and now the latest 3.0.0 ldap schema. The problem I
have is that no Windows user can
Hello,
I've just upgraded from samba3-alpha23 to samba3.0.0 release. I'm
running samba with an LDAP backend and I used the convertSambaAccount
conversion script, and now the latest 3.0.0 ldap schema. The problem I
have is that no Windows user can authenticate against their home
directory, or any
-17 at 14:42, Paul Eggleton wrote:
Hi Kristis,
Kristis Makris wrote on Friday, 18 July 2003 9:19 a.m.:
[2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900)
getpeername failed. Error was Transport endpoint is not connected
[2003/07/17 12:16:06, 0] lib
Hello,
I've been using samba-3alpha22 as a PDC authenticating against LDAP. I
am trying to add NT Groups using the smbgroupedit utility.
It seems to me that smbgroupedit always looks in /etc/group and does not
take into account the ldap configuration options specified in smb.conf.
The relevant