The problem is triggered when we send a lease break while the send queue is congested, so the lease break packet is queued behind other packets. As we've implemented a unacked lease break logic to detect channel failures for multichannel, this currently quite short timer fires (TCP RTO * 6, so 1.5 seconds in the case we've debugged) and disconnects the channel and also exits if it's the only channel. We have several ideas how this should be addressed including: - prioritize lease breaks in Samba's send queue - increase timeout - don't use a timeout if there's only one channel - restart timer every time the client consumes data (my favorite one :) ) - make the timeout configurable - more ... ?