I've still been experiencing the issues myself, but the frequency I'd been seeing it happen diminished significantly for a couple of months after my last post. Maybe once or twice a week.
However, within the past few weeks, it's come back with a vengeance, and it's only been happening when I start watching a show within the first couple of minutes.
Given that there's three of us running Server 2019 with the same issue, that got me thinking that maybe there's a TCP stack setting interfering with it.
I figure that most users of Channels on Windows are probably using Win 10, and they aren't reporting any issues, so I did a comparison of the TCP settings between Win 10 1909 and Server 2019 last night.
Here are the differences I noted:
Server 2019:
ECN Capability: enabled
Initial RTO: 3000
Max SYN Retransmissions: 2
Fast Open: disabled
MemoryPressureProtection: enabled
PacketCoalescingFilter: Disabled
Win 10:
ECN Capability: disabled
Initial RTO: 1000
Max SYN Retransmissions: 4
Fast Open: enabled
MemoryPressureProtection: disabled
PacketCoalescingFilter: Enabled
The one that stood out to me is the memory pressure protection. According to this article, MPP is a feature designed to protect against DDoS attacks. It can potentially misidentify an attack, and when it thinks it's under attack, it kills the existing TCP connections and drops incoming SYN requests.
I disabled it last night, and I've watched something on all three of my ATVs since then. No issues yet, so I'm hopeful this might be it.
@mhartman, give it a try by running: netsh int tcp set security mpp=disabled
If you haven't already, also set the autotuning level back to normal. That also made no difference for me.