[Samba] Samba 3.0.3pre2 Available for Download
Collen Blijenberg <MLHJ>
------------------------------------------------------
[2004/02/19 14:03:00, 0] lib/util_sock.c:read_socket_data(342)
read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/02/19 14:06:18, 0] lib/util_sock.c:get_peer_addr(952)
getpeername failed. Error was Transport endpoint is not connected
[2004/02/19 14:06:18, 0] lib/util_sock.c:send_smb(605)
Error writing 4 bytes to client. -1. (Connection reset by peer)
-----------------------------------------------------
Collen Blijenberg (Montessori Lyceum Herman Jordan)
Monday, April 5, 2004, 6:26:22 PM, you wrote:
GJC> -----BEGIN PGP SIGNED MESSAGE-----
GJC> Hash: SHA1
GJC> This is the second preview release of the Samba 3.0.3 code base
GJC> and is provided for testing only. This release is *not* intended
GJC> for production servers. Use at your own risk.
GJC> There have been several bug fixes since the 3.0.2a release that
GJC> we feel are important to make available to the Samba community
GJC> for wider testings. See the "Changes" section for details on
GJC> exact updates.
GJC> Common bugs fixed in this preview release include:
GJC> ~ o Substitution errors for %[UuGg] in smb.conf.
GJC> ~ o winbindd crashes when using ADS security mode.
GJC> ~ o SMB signing errors.
GJC> New features introduced in this preview release include:
GJC> ~ o Experimental support for storing DOS attribute on files
GJC> ~ and folders in Extended Attributes.
GJC> The source code can be downloaded from:
GJC> ~ http://download.samba.org/samba/ftp/pre/
GJC> The uncompressed tarball and patch file have been signed
GJC> using GnuPG. The Samba public key is available at
GJC> ~ http://download.samba.org/samba/ftp/samba-pubkey.asc
GJC> Links to binary packages can be found on the
GJC> ~ http://www.samba.org/samba/samba.html
GJC> A simplified version of the CVS log of updates since 3.0.3pre1
GJC> can be found in the the download directory under the name
GJC> ChangeLog-3.0.3pre1-3.0.3pre2. The release notes are also available
GJC> in the same directory.
GJC> As always, all bugs are our responsibility.
GJC> ~ --Enjoy
GJC> ~ The Samba Team
GJC> -----BEGIN PGP SIGNATURE-----
GJC> Version: GnuPG v1.2.1 (GNU/Linux)
GJC> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
GJC> iD8DBQFAcYiuIR7qMdg1EfYRAnCPAKDihuJSZwd5j/9w7HzZMVmbjKLdVgCglAJr
GJC> ZciCvu4QpvzwZ6rx72260is=
GJC> =70/e
GJC> -----END PGP SIGNATURE-----
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Gerald (Jerry) Carter
Hash: SHA1
On Tue, 6 Apr 2004, Collen Blijenberg <MLHJ> wrote:
> Just wandering, wether this bug is fixed in the 303 pre 2 ??
> ------------------------------------------------------
> [2004/02/19 14:03:00, 0] lib/util_sock.c:read_socket_data(342)
> read_socket_data: recv failure for 4. Error = Connection reset by peer
> [2004/02/19 14:06:18, 0] lib/util_sock.c:get_peer_addr(952)
> getpeername failed. Error was Transport endpoint is not connected
> [2004/02/19 14:06:18, 0] lib/util_sock.c:send_smb(605)
> Error writing 4 bytes to client. -1. (Connection reset by peer)
> -----------------------------------------------------
The client disconnected. This is not a Samba bug. Best to check
for bad network hardware, hubs, switches, mismatched duplex settings on
NICs, etc...
Now if we did something to cause the client to disconnect (e.g. blue
screen the client), then we would need to fix that.
cheers, jerry
- ----------------------------------------------------------------------
Hewlett-Packard ------------------------- http://www.hp.com
SAMBA Team ---------------------- http://www.samba.org
GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc
"...a hundred billion castaways looking for a home." ----------- Sting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQFAcm+LIR7qMdg1EfYRAiy1AJ9/kHvF125iphdpTpzhOTR3bGIk5wCfQiyC
DfuYD54GBUh+4irRyE/y6fI=
=Y2uI
Collen Blijenberg <MLHJ>
with differend nic's (intel, realtek and 3com)
and differend switches ( 2 networks)
i thought it was caused by that 0.0.0.0 broadcast..
(i vagely remeber seeing some in my log files, some time ago)
-----------------------------------------------------
Collen Blijenberg (Montessori Lyceum Herman Jordan)
Tuesday, April 6, 2004, 10:51:20 AM, you wrote:
GJC> -----BEGIN PGP SIGNED MESSAGE-----
GJC> Hash: SHA1
GJC> On Tue, 6 Apr 2004, Collen Blijenberg <MLHJ> wrote:
>> Just wandering, wether this bug is fixed in the 303 pre 2 ??
>> ------------------------------------------------------
>> [2004/02/19 14:03:00, 0]
>> lib/util_sock.c:read_socket_data(342)
>> read_socket_data: recv failure for 4. Error = Connection reset by peer
>> [2004/02/19 14:06:18, 0] lib/util_sock.c:get_peer_addr(952)
>> getpeername failed. Error was Transport endpoint is not connected
>> [2004/02/19 14:06:18, 0] lib/util_sock.c:send_smb(605)
>> Error writing 4 bytes to client. -1. (Connection reset by peer)
>> -----------------------------------------------------
GJC> The client disconnected. This is not a Samba bug. Best to check
GJC> for bad network hardware, hubs, switches, mismatched duplex settings on
GJC> NICs, etc...
GJC> Now if we did something to cause the client to disconnect (e.g. blue
GJC> screen the client), then we would need to fix that.
GJC> cheers, jerry
GJC> -
GJC> ----------------------------------------------------------------------
GJC> Hewlett-Packard ------------------------- http://www.hp.com
GJC> SAMBA Team ---------------------- http://www.samba.org
GJC> GnuPG Key ----
GJC> http://www.plainjoe.org/gpg_public.asc
GJC> "...a hundred billion castaways looking for a home." ----------- Sting
GJC> -----BEGIN PGP SIGNATURE-----
GJC> Version: GnuPG v1.2.1 (GNU/Linux)
GJC> Comment: For info see http://quantumlab.net/pine_privacy_guard/
GJC> iD8DBQFAcm+LIR7qMdg1EfYRAiy1AJ9/kHvF125iphdpTpzhOTR3bGIk5wCfQiyC
GJC> DfuYD54GBUh+4irRyE/y6fI=
GJC> =Y2uI
GJC> -----END PGP SIGNATURE-----
===8<===========End of original message text===========
--
Best regards,
Collen mailto:systee...@hermanjordan.nl
mroj...@eastgranby.k12.ct.us
Transport endpoint is not connected” message appearing on our logs. This
message was being produced very frequently during the day and somewhat
less frequently at night.
Our configuration is samba 3.0.2a as a PDC with WINS support. Our network
has about 60 XP Pro PC’s and 100 W98 PC’s. The signorseal registry patch
was applied to all the XP Pro PC’s last year while we were still running
samba 2.
It was quickly apparent that this message was only being issued for our XP
Pro PC’s. Also, at night when the network was pretty idle, the message
was being issued only on certain XP PRO PC’s, but the PC’s varied on a
nightly basis. Furthermore, at night, for a particular XP Pro PC, the
messages were occurring at intervals that were multiples of 15 minutes.
After doing some reading and taking some network traces, I inferred that
the XP PRO PC’s for which the message occurred at night were backup
browsers getting their 15 minute refresh. By disabling the Computer
Browsing service on a bunch of the XP Pro PC’s, the night time messages
were reduced.
In any event, I did some more reading and looked at some more network
traces, without a real understanding. However, one of the items I read
was that the XP Pro PC Client attempts to initially communicate with the
server over both ports 445 and 139 and that whichever port responds first
is used for further communication. So I decided to try disabling port 445
at the server by using iptables to force all session traffic across port
139.
“iptables -I INPUT 1 -p tcp --dport 445 -j DROP”
I did this last night and, since applying this iptables rule, there have
been no “getpeername failed. Error was Transport endpoint is not
connected” messages in the log. It is now midmorning with regular
network traffic. I regard this as a circumvention rather than a fix.
So I suspect that the production of this message is a software issue that
is somehow related to the initial communication over both ports 445 and
139 rather than being any type of network hardware issue. If the samba
group needs some network traces, I can supply them.
Mark Orenstein
East Granby School System (Connecticut, USA)
Gerald Drouillard
> “iptables -I INPUT 1 -p tcp --dport 445 -j DROP”
Be careful running this on a Samba 3.x PDC with other samba servers on
the network. It appears that you will loose the ability for windows
clients to map drives to the other non-PDC servers on the network from
my test today.
Regards
Gerald Drouillard
http://convert2samba.com