Displaying 5 results from an estimated 5 matches for "makris".
Did you mean:
makis
2003 Jul 17
1
write_socket: Error writing 4 bytes to socket 5: ERRNO =Connection reset by peer
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/util_sock.c:write_socket_data(388)
> write_socket_data: write failure. Error...
2003 Oct 31
1
samba-3.0.0 release won't authenticate
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 authenticate against their home
directory, or any other machine. Authentication against the
2003 Mar 11
0
smbgroupedit does not honor ldap parameters from smb.conf
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 ldap entries are:
passdb backend = ldapsam:ldap://ebola/
ldap suffix="dc=datasoft,
2003 Jul 17
0
write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Hello,
I originally posted this on samba-technical
(http://lists.samba.org/pipermail/samba-technical/2003-July/046076.html), but I just verified that I'm also seeing the same error message with samba-3.0.0beta3. I have not tested if I'm also getting disconnects and Word saving problems that way. But, people using 2.2.7 must have also seen this.
Here are some messages I've seen in
2004 Jan 28
0
No Mapping between account names and security IDs was done
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 new sambaDomainName=<domainname> entry in LDAP that contains a SID
that's different than