Apologies in advance if this has already been considered ... If the break is at 120 seconds (plus a tiny bit) then maybe the Windows TcpTimedWaitDelay is kicking in because of something that it thinks did not get acknowledged 2 minutes earlier.
There is a registry key available to adjust from the default of 120 seconds https://learn.microsoft.com/en-us/biztalk/technical-guides/settings-that-can-be-modified-to-improve-network-performance Changing that number (and rebooting) and then seeing if there is a direct correlation with the time when the problem happens would at least help focus things. Note - the key is not present by default. Paul Webster author of \"now playing\" plugins covering radio france (fip etc), planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, abc australia and cbc/radio-canada and, via the extra \"radio now playing\" plugin lots more - see https://forums.slimdevices.com/showthread.php?115201-announce-radio-now-playing-plugin ------------------------------------------------------------------------ Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=104614 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
