[Samba] getpeername failed. Error was Transport endpoint is not connected (3.0.37)

2011-03-10 Thread Jack Bush
Hi All,
 
I have a Solaris 10 server (Sun Fire T5520) that has recently been patched with 
Samba 3.0.37 but is not able to share any drives to Windows clients. Instead, 
the /var/samba/log/log.smbd is showing the following errros:
 getpeername failed. Error was Transport endpoint is not connected 
    Denied connection from 0.0.0.0 (0.0.0.0) 
    [2011/03/10 21:10:04, 1] smbd/process.c:(1076) 
    [2011/03/10 21:10:04, 0] lib/util_sock.c:(1224) 
    write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
    Error writing 5 bytes to client. -1. (Broken pipe)
 
It would be very much appreciate some guidances on how to resolve this issue.
 
Thanks,
Jack


  
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] getpeername failed. Error was Transport endpoint is not connected

2011-02-18 Thread David Touzeau
I'm using samba 3.5.6 + PDC and connected to LDAP directory

In log level 1 there is many entries like this :
Feb 18 18:13:42 samba smbd[21646]:   getpeername failed. Error was
Transport endpoint is not connected
Feb 18 18:13:42 samba smbd[21646]:   write_data: write failure in
writing to client 0.0.0.0. Error Connection reset by peer

Is it a problem ? or just an informative event ?


Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.423085,  2]
lib/interface.c:340(add_interface)
Feb 18 18:13:42 samba smbd[21646]:   added interface eth0
ip=fe80::250:56ff:fe97:3374%eth0 bcast=fe80:::::%eth0
netmask=:::::
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.423232,  2]
lib/interface.c:340(add_interface)
Feb 18 18:13:42 samba smbd[21646]:   added interface eth0
ip=192.168.200.2 bcast=192.168.200.255 netmask=255.255.255.0
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424046,  2]
smbd/reply.c:554(reply_special)
Feb 18 18:13:42 samba smbd[21646]:   netbios connect: name1=SAMBA
0x20 name2=PC2009-03  0x0
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424135,  2]
smbd/reply.c:565(reply_special)
Feb 18 18:13:42 samba smbd[21646]:   netbios connect: local=samba
remote=pc2009-03, name type = 0
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424320,  0]
lib/util_sock.c:675(write_data)
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.424352,  0]
lib/util_sock.c:1432(get_peer_addr_internal)
Feb 18 18:13:42 samba smbd[21646]:   getpeername failed. Error was
Transport endpoint is not connected
Feb 18 18:13:42 samba smbd[21646]:   write_data: write failure in
writing to client 0.0.0.0. Error Connection reset by peer
Feb 18 18:13:42 samba smbd[21646]: [2011/02/18 18:13:42.425301,  0]
smbd/process.c:79(srv_send_smb)
Feb 18 18:13:42 samba smbd[21646]:   Error writing 4 bytes to client.
-1. (Transport endpoint is not connected)
Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427012,  2]
printing/print_cups.c:550(cups_async_callback)
Feb 18 18:13:42 samba smbd[21647]:   cups_async_callback: failed to read
a new printer list
Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427239,  2]
lib/interface.c:340(add_interface)
Feb 18 18:13:42 samba smbd[21647]:   added interface eth0
ip=fe80::250:56ff:fe97:3374%eth0 bcast=fe80:::::%eth0
netmask=:::::
Feb 18 18:13:42 samba smbd[21647]: [2011/02/18 18:13:42.427480,  2]
lib/interface.c:340(add_interface)
Feb 18 18:13:42 samba smbd[21647]:   added interface eth0
ip=192.168.200.2 bcast=192.168.200.255 netmask=255.255.255.0
Feb 18 18:13:43 samba smbd[21647]: [2011/02/18 18:13:43.886294,  2]
smbd/sesssetup.c:1391(setup_new_vc_session)
Feb 18 18:13:43 samba smbd[21647]:   setup_new_vc_session: New VC == 0,
if NT4.x compatible we would close all

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Samba getpeername failed. Error was Transport endpoint is not connected

2009-05-27 Thread Daniel Müller
Dear All,

Suse 10.2 Samba 3.2.8

How to get rid off the annoying: Samba getpeername failed. Error was
Transport endpoint is not connected.

I made iptables –I INPUT 1 –p tcp –dport 445 –j DROP and it finished. But
this could not be the solution.

Since the newer versions of samba this port makes sense and should be used.

Did someone solve this?

 

Greetings 

Daniel

 

 

 

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] getpeername failed. Error was Transport endpoint is not connected

2005-10-26 Thread Andreas Bauer
Hello NG

I'm trying without success to join a XP workstation in a Samba/openldap 
domain

SuSE 9.3)and to connect this samba/ldap as fileserver.

On samba machine I'm getting this errormessage:

my var/log/samba/smbd:

[2005/10/26 16:24:04, 0] lib/util_sock.c:get_peer_addr(1150)
  getpeername failed. Error was Transport endpoint is not connected
[2005/10/26 16:26:28, 0] lib/util_sock.c:get_peer_addr(1150)
  getpeername failed. Error was Transport endpoint is not connected



The errormessage of XP after the login machinejoining XP GUI

is:

"couldn't found the username", but the NetBios Administratoraccount

is existing.

Can somebody help me, any idea?



Best regards and many thanks

Andreas



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] getpeername failed. Error was Transport endpoint is not connected

2005-10-04 Thread Alexandre Novello
I have a similar error, I can us XP workstation ad domain members, and they
even use the shares, but two or threes times per day the connection resets,
and I have to kill the smbd and start it again (only restart does not work).
Take look at my LOG. Any idea?
 [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150)
getpeername failed. Error was Transport endpoint is not connected
[2005/10/04 11:02:10, 0] lib/access.c:check_access(328)
[2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150)
getpeername failed. Error was Transport endpoint is not connected
Denied connection from (0.0.0.0 )
[2005/10/04 11:02:10, 1] smbd/process.c:process_smb(1084)
[2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150)
getpeername failed. Error was Transport endpoint is not connected
Connection denied from 0.0.0.0 
[2005/10/04 11:02:10, 0] lib/util_sock.c:write_socket_data(430)
write_socket_data: write failure. Error = Connection reset by peer
[2005/10/04 11:02:10, 0] lib/util_sock.c:write_socket(455)
write_socket: Error writing 5 bytes to socket 27: ERRNO = Connection reset
by peer
[2005/10/04 11:02:10, 0] lib/util_sock.c:send_smb(647)
Error writing 5 bytes to client. -1. (Connection reset by peer)

--

Alexandre Novello
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] getpeername failed, Error was Transport endpoint is not connected

2005-07-06 Thread H.meijerink
Hello,
 
Using Samba 3.014 on SLES9 on a proliant Xeon server.
All clients (XP) fixed IP addresses,
Ip <> hostname in hosts table.
During the boot of a XP client I receive these messages in the log file's
Can anybody explain why or what is causing this.
Most of the XP clients reporting none of these messages.
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:get_peer_addr(1150) 
Jul  6 12:50:24 server4 smbd[27787]:   getpeername failed. Error was
Transport endpoint is not connected 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket_data(430) 
Jul  6 12:50:24 server4 smbd[27787]:   write_socket_data: write failure.
Error = Connection reset by peer 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket(455) 
Jul  6 12:50:24 server4 smbd[27787]:   write_socket: Error writing 4 bytes
to socket 5: ERRNO = Connection reset by peer 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:send_smb(647) 
Jul  6 12:50:24 server4 smbd[27787]:   Error writing 4 bytes to client. -1.
(Connection reset by peer) 
 
Name resolve order in the smb.conf file: lmhosts hosts wins bcast
 
Thanks
Harry
[EMAIL PROTECTED]

 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] getpeername failed, Error was Transport endpoint is not connected

2005-07-06 Thread H.meijerink
Hello,
 
Using Samba 3.014 on SLES9 on a proliant Xeon server.
All clients (XP) fixed IP addresses,
Ip <> hostname in hosts table.
During the boot of a XP client I receive these messages in the log file's
Can anybody explain why or what is causing this.
Most of the XP clients reporting none of these messages.
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:get_peer_addr(1150) 
Jul  6 12:50:24 server4 smbd[27787]:   getpeername failed. Error was
Transport endpoint is not connected 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket_data(430) 
Jul  6 12:50:24 server4 smbd[27787]:   write_socket_data: write failure.
Error = Connection reset by peer 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:write_socket(455) 
Jul  6 12:50:24 server4 smbd[27787]:   write_socket: Error writing 4 bytes
to socket 5: ERRNO = Connection reset by peer 
Jul  6 12:50:24 server4 smbd[27787]: [2005/07/06 12:50:24, 0]
lib/util_sock.c:send_smb(647) 
Jul  6 12:50:24 server4 smbd[27787]:   Error writing 4 bytes to client. -1.
(Connection reset by peer) 
 
Name resolve order in the smb.conf file: lmhosts hosts wins bcast
 
Thanks
Harry
[EMAIL PROTECTED]

 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-18 Thread Guido Lorenzutti
Are you sure? In wich scenario? I have a pdc on samba and when i check 
the "netstat" i have a lot of open conections with the 445 port on the 
smbd binary.

Ed Kasky wrote:
I went around and around with this issue for months replacing cables, 
switches and nics on a couple of machines all to no avail.   I played 
around with something I found in the archives:

http://lists.samba.org/archive/samba/2004-April/084048.html
Using iptables to drop port 445, I eliminated the errors.  I have not 
seen the error return nor experienced any other negative impact on 
performance.

Ed
At 08:36 AM Monday, 4/18/2005, Dimitri Yioulos wrote -=>
I've also seen a post somewhere (forgive, don't remember where 
"somewhere is)
suggesting that "smb ports = 445" would corect this issue.  So, which 
is it,
139 or 445?

Dimitri
On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote:
> I've already seen this in my logs...
> A little search on Google shows me that Windows XP client try try to
> connect to port 139 and 445 in parallel and drop the connection to 
port
> 139 if the connect to 445 is successful.
> In fact, no one was complaining about real network connection loss ...
> More informations here : http://www.linuxaa.com/ftopic6568.html
> Hope this helps.
>
> On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote:
> > I get this error message "getpeername failed. Error was Transport
> > endpoint is not connected" in my logs very often. Any ideas how 
to fix
> > it?
> >
> > Tnxs in advance
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Ed Kasky
~
Randomly Generated Quote (194 of 477):
"Things may come to those who wait, but only the things
 left by those who hustle."  - Abraham Lincoln
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-18 Thread Ed Kasky
I went around and around with this issue for months replacing cables, 
switches and nics on a couple of machines all to no avail.   I played 
around with something I found in the archives:

http://lists.samba.org/archive/samba/2004-April/084048.html
Using iptables to drop port 445, I eliminated the errors.  I have not seen 
the error return nor experienced any other negative impact on performance.

Ed
At 08:36 AM Monday, 4/18/2005, Dimitri Yioulos wrote -=>
I've also seen a post somewhere (forgive, don't remember where "somewhere is)
suggesting that "smb ports = 445" would corect this issue.  So, which is it,
139 or 445?
Dimitri
On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote:
> I've already seen this in my logs...
> A little search on Google shows me that Windows XP client try try to
> connect to port 139 and 445 in parallel and drop the connection to port
> 139 if the connect to 445 is successful.
> In fact, no one was complaining about real network connection loss ...
> More informations here : http://www.linuxaa.com/ftopic6568.html
> Hope this helps.
>
> On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote:
> > I get this error message "getpeername failed. Error was Transport
> > endpoint is not connected" in my logs very often. Any ideas how to fix
> > it?
> >
> > Tnxs in advance
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba
Ed Kasky
~
Randomly Generated Quote (194 of 477):
"Things may come to those who wait, but only the things
 left by those who hustle."  - Abraham Lincoln
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-18 Thread Dimitri Yioulos
I've also seen a post somewhere (forgive, don't remember where "somewhere is) 
suggesting that "smb ports = 445" would corect this issue.  So, which is it, 
139 or 445?

Dimitri

On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote:
> I've already seen this in my logs...
> A little search on Google shows me that Windows XP client try try to
> connect to port 139 and 445 in parallel and drop the connection to port
> 139 if the connect to 445 is successful.
> In fact, no one was complaining about real network connection loss ...
> More informations here : http://www.linuxaa.com/ftopic6568.html
> Hope this helps.
>
> On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote:
> > I get this error message "getpeername failed. Error was Transport
> > endpoint is not connected" in my logs very often. Any ideas how to fix
> > it?
> >
> > Tnxs in advance
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-18 Thread Tony Earnshaw
man, 18.04.2005 kl. 08.58 skrev Guido Lorenzutti:

> I get this error message "getpeername failed. Error was Transport 
> endpoint is not connected" in my logs very often. Any ideas how to fix it?

Correct your network problems; make sure that all computers in your
network are reachable and booted.

--Tonni

-- 
Nothing sucksseeds like a pigeon without a beak ...

mail: [EMAIL PROTECTED]
http://www.billy.demon.nl
 
They love us, don't they, They feed us, won't they ...

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-18 Thread Fabian Arrotin
I've already seen this in my logs...
A little search on Google shows me that Windows XP client try try to
connect to port 139 and 445 in parallel and drop the connection to port 
139 if the connect to 445 is successful.
In fact, no one was complaining about real network connection loss ...
More informations here : http://www.linuxaa.com/ftopic6568.html
Hope this helps.

On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote:
> I get this error message "getpeername failed. Error was Transport 
> endpoint is not connected" in my logs very often. Any ideas how to fix it?
> 
> Tnxs in advance


signature.asc
Description: This is a digitally signed message part
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] "getpeername failed. Error was Transport endpoint is not connected"

2005-04-17 Thread Guido Lorenzutti
I get this error message "getpeername failed. Error was Transport 
endpoint is not connected" in my logs very often. Any ideas how to fix it?

Tnxs in advance
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] "getpeername failed. Error was Transport endpoint is not connected", don't solve?

2004-10-19 Thread Fernando Ribeiro
Hi all,

I'm using Samba 3.0.7, OpenLDAP 2.2.17, smbldap-tools-0.8.5

It has been configured pdc with tls.

tls work fine:

ldapsearch -x -ZZ -h ldap.domain.com.br -D 
cn=suport,dc=domain,dc=com,dc=br -L -W

...
...
# numResponses: 20
# numEntries: 19

my user has been found and accept password in the ldap

[EMAIL PROTECTED]:~# id fernando.ribeiro
uid=1000(fernando.ribeiro) gid=1000(suporte) groups=1000(suporte),512(Domain 
Admins)

[EMAIL PROTECTED]:~# smbclient -L ldap.domain.com.br -U fernando.ribeiro
Password: 
Domain=[domain] OS=[Unix] Server=[Samba 3.0.7]
...

WorkgroupMaster
---
domain   PDC

my ldap.conf

base dc=domain,dc=com,dc=br
uri ldap://ldap.domain.com.br
ssl start_tls
port 389

TLS_CACERT /usr/local/ssl/cacert.pem

rootbinddn cn=suporte,dc=domain,dc=com,dc=br
nss_base_passwd ou=Usuarios,dc=domain,dc=com,dc=br?one
nss_base_shadow ou=Usuarios,dc=domain,dc=com,dc=br?one
nss_base_group ou=Grupos,dc=domain,dc=com,dc=br?one


[global]
   workgroup = domain
   netbios name = PDC 
   server string = PDC
   security = user
   encrypt passwords = yes
   load printers = yes
   log file = /var/log/samba/%m.log
   max log size = 50
   log level = 5
   os level = 255
   local master = yes
   domain master = yes 
   preferred master = yes
   domain logons = yes
   admin users = fernando.ribeiro, wesley.lago
   logon script = %U.bat
   logon path = \\%L\profiles\%U
#   wins support = no
#   wins proxy = no
#   dns proxy = no
# name resolve order = wins lmhosts hosts bcast
#   smb ports = 137 138 139 445
#   interfaces = 10.0.0.0/24 127.0.0.1
#   bind interfaces only = Yes
   ldap passwd sync = yes
 ldap delete dn = Yes
 ldap port = 389
 ldap ssl = start_tls
   passdb backend = ldapsam:ldap://ldap.domain.com.br/
   ldap admin dn = cn=suporte,dc=domain,dc=com,dc=br
   ldap suffix = dc=domain,dc=com,dc=br
   ldap group suffix = ou=Grupos
   ldap user suffix = ou=Usuarios
   ldap machine suffix = ou=Computadores
   idmap uid = 1-15000
 idmap gid = 1-15000
   nt acl support = yes 
   create mask = 600
   directory mask = 0700
   force directory mode = 0700
   passwd chat = *New*password* %n\n *Retype*new*password* 
%n\n*passwd:*all*authentication*tokens*updated*successfully*
   socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192
 add user script = /usr/local/sbin/smbldap-useradd -m "%u"
 add group script = /usr/local/sbin/smbldap-groupadd -p "%g"
 add machine script = /usr/local/sbin/smbldap-useradd -w "%u"
 delete user script = /usr/local/sbin/smbldap-userdel "%u"
 delete group script = /usr/local/sbin/smbldap-groupdel "%g"
 add user to group script = /usr/local/sbin/smbldap-groupmod -m "%u" "%g"
   delete user from group script = /usr/local/sbin/smbldap-groupmod -x "%u" "%g"
 set primary group script = /usr/local/sbin/smbldap-usermod -g "%g" "%u"
   dos charset = UTF-8
 unix charset = UTF-8
 cups server = 10.0.0.11
#use sendfile = no

[homes]
comment = Diretorio Home
browseable = no
writable = yes
  force user = %U
 
[profiles]
  path = /home/profiles
  read only = No
  create mask = 0600
  directory mask = 0700
  browseable = No
  guest ok = Yes
  profile acls = Yes
  csc policy = disable
  force user = %U
valid users = %U @"Domain Admins"

[netlogon]
path = /home/netlogon
browseable = No
read only = yes
   
[printers]
   comment = Impressoras
   path = /var/spool/samba
   browseable = no
   guest ok = no
   writable = no
   printable = yes

And while i try include a workstation (windows XP with SP2) it return
this error:

[2004/10/19 16:12:19, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Transport endpoint is not connected
  [2004/10/19 16:12:19, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
  [2004/10/19 16:12:19, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 22: ERRNO =  Connection reset by peer
  [2004/10/19 16:12:19, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)


It created the windows$ entry in ldap:

[EMAIL PROTECTED]:~# ldapsearch -x -ZZ -h ldap.domain.com.br -D
cn=suporte,dc=domain,dc=com,dc=br uid=windows$ -W -LLL
Enter LDAP Password: 
dn: uid=windows$,ou=Computadores,dc=domain,dc=com,dc=br
objectClass: top
objectClass: inetOrgPerson
objectClass: posixAccount
cn: windows$
sn: windows$

Re: [Samba] getpeername failed. Error was Transport endpoint is not connected

2004-10-06 Thread Fernando Ribeiro
It trying port 430 and 455?
Why??


Palavras de Fernando Ribeiro [Tue, Oct 05, 2004 at 01:45:26PM -0300]:
> Hi all,
> 
>   I'm using slackware 10, running samba-3.0.7, OpenLDAP-2.2.17 with ssl,
>   tls and sasl2.
> 
> 
>   While i trying include a workstation windows xp in the samba domain it
>   return this:
> 
>   [2004/10/05 12:51:25, 0] lib/util_sock.c:send_smb(647)
>   Error writing 4 bytes to client. -1. (Connection reset by peer)
>   [2004/10/05 12:51:26, 0] lib/util_sock.c:get_peer_addr(1000)
>   getpeername failed. Error was Transport endpoint is not connected
>   [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket_data(430)
>   write_socket_data: write failure. Error = Connection reset by peer
>   [2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket(455)
>   write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection 
> reset by peer
>   [2004/10/05 12:51:26, 0] lib/util_sock.c:send_smb(647)
>   Error writing 4 bytes to client. -1. (Connection reset by peer)
> 
>   Anyone know why?
> 
>   My configuration has been in
>   http://www.nerdgroup.org/doc/samba+ldap+qmail.txt
> 
>   Thanks
> 
> -- 
> Fernando Ribeiro - GPG-KEY: 0x8D7255F4
> Linux Counter: #273768 - ICQ: 175630330
> Linux Professional Institute - LPIC-1
> Death the graph! Death the mouse!
> Death patents! Death closed standards!
> http://www.nerdgroup.org
> http://musb.nerdgroup.org
> --
> "Grandes mentes discutem idéias;
> Mentes medianas discutem eventos;
> Mentes pequenas discutem pessoas."
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
> 

-- 
Fernando Ribeiro - GPG-KEY: 0x8D7255F4
Linux Counter: #273768 - ICQ: 175630330
Linux Professional Institute - LPIC-1
Death the graph! Death the mouse!
Death patents! Death closed standards!
http://www.nerdgroup.org
http://musb.nerdgroup.org
--
"Grandes mentes discutem idéias;
Mentes medianas discutem eventos;
Mentes pequenas discutem pessoas."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] getpeername failed. Error was Transport endpoint is not connected

2004-10-05 Thread Fernando Ribeiro
Hi all,

I'm using slackware 10, running samba-3.0.7, OpenLDAP-2.2.17 with ssl,
tls and sasl2.


While i trying include a workstation windows xp in the samba domain it
return this:

[2004/10/05 12:51:25, 0] lib/util_sock.c:send_smb(647)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2004/10/05 12:51:26, 0] lib/util_sock.c:get_peer_addr(1000)
getpeername failed. Error was Transport endpoint is not connected
[2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket_data(430)
write_socket_data: write failure. Error = Connection reset by peer
[2004/10/05 12:51:26, 0] lib/util_sock.c:write_socket(455)
write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection 
reset by peer
[2004/10/05 12:51:26, 0] lib/util_sock.c:send_smb(647)
Error writing 4 bytes to client. -1. (Connection reset by peer)

Anyone know why?

My configuration has been in
http://www.nerdgroup.org/doc/samba+ldap+qmail.txt

Thanks

-- 
Fernando Ribeiro - GPG-KEY: 0x8D7255F4
Linux Counter: #273768 - ICQ: 175630330
Linux Professional Institute - LPIC-1
Death the graph! Death the mouse!
Death patents! Death closed standards!
http://www.nerdgroup.org
http://musb.nerdgroup.org
--
"Grandes mentes discutem idéias;
Mentes medianas discutem eventos;
Mentes pequenas discutem pessoas."
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba