[Discuss] (ssh) Write failed: Broken pipe

[greg at freephile.com (Greg Rundlett (freephile))]

[SOLVED]
There was a second machine on the network that was configured with the same
static IP address.  Someone turned on that machine. Sometimes client SSH
connections would get routed to machine B.  I'm outside the network, so I
don't have much more detail than that.  I'm also not sure how this scenario
plays out with varying degrees of "enterprise" switching/routing hardware,
but I'd expect a good router to wave big flags when there are two
interfaces claiming the same IP with different MACs

Greg Rundlett


On Thu, Sep 5, 2013 at 6:07 PM, Richard Pieri <richard.pieri at gmail.com>wrote:

> The last time I saw something like this it had nothing to do with SSH per
> se. The NIC was flaky. The NIC would randomly reset itself -- killing
> active TCP sessions -- and renegotiate the link. My SSH sessions were
> hapless victims.
>
> Replaced the NIC, problem went away.
>
> --
> Rich P.
>
> ______________________________**_________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/**listinfo/discuss<http://lists.blu.org/mailman/listinfo/discuss>
>