8 Replies Latest reply on Oct 8, 2016 6:56 PM by Intel Corporation

    Windows 10 I217-V TCP IPV6 Checksum fails on RX

    rootwiler

      ISP has IPV6 enabled and I noticed my desktop PC stopped getting Windows updates.

       

      After much digging and test, I found out that my NIC was dropping TCP packet on the receive from Windows Update. After disabling all Offloading options and enabling options one by one, I was able to narrow it down to TCP RX was the culprit.

       

      Windows 10 1607 x64

      Intel I217-V 12.15.23.1 (5/10/2016)

       

       

      Not sure if anyone else has seen this issue? Windows Update log showed it never received a HTTP response back from Microsoft.

       

       

      2016/08/08 22:32:43.3589251 1416  12388 WebServices     WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

      2016/08/08 22:32:43.3589262 1416  12388 WebServices     WS error: There was an error receiving the HTTP reply.

      2016/08/08 22:32:43.3589268 1416  12388 WebServices     WS error: The connection with the remote endpoint was terminated.

      2016/08/08 22:32:43.3589280 1416  12388 WebServices     WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

      2016/08/08 22:32:43.3589289 1416  12388 WebServices     WS error: There was an error receiving the HTTP reply.

      2016/08/08 22:32:43.3589297 1416  12388 WebServices     WS error: The operation did not complete within the time allotted.

      2016/08/08 22:32:43.3589493 1416  12388 WebServices     WS error: The connection with the server was terminated abnormally

      2016/08/08 22:32:43.3589508 1416  12388 WebServices     Web service call failed with hr = 80240440.

       

      This was one of many things that didn't work correctly when TCP RX Checksum offload was enabled.

       

      Thanks!