[Info-vax] Another "automatic update"

[Andy Burns]

Arne Vajhøj wrote:

> It seems obvious that not everything TCP/IP was broken in Windows 2012.
> That would have caused some headlines.

ISTR that the TCP/IP stack in Windows is [based on] the FreeBSD stack.

> I do not completely understand your description:
> 
> #Turns out it's an error from WEENDOZE TCP/IP, where it attempts to
> #connect to another connection request while the listener is currently
> #attached to another connection.
> 
> But it sound like a somewhat unusual thing.

Could it be port exhaustion caused by an application "chewing through" 
ephemeral ports faster that the 2MSL timer frees them up?  It's possible 
to alter the min/max port number for outbound connections.