Here's what we knew:
It only happened on the first connection.
And it only happened after the machine has been idle for long periods of time for a given host.
It turns out that it's a known issue. According to
A network engineering chick talking about network engineering topics. And stuff.
No comments:
Post a Comment