SendOneXPacket operation failed

Question

Hi!

When the workstation starts, the (only) first onex authentication stops at a given handshake point (the client waits up to 30 seconds for a response or starts a new authentication).
Authentication is EAP-MSCHAP v2 (computer authentication).
The network adapter is Intel I219-LM.
Latest drivers available Clean installs tested from both OEM (HP EliteDesk 800 G4 WKS TWR) and Intel.

At first I thought it was a Windows problem, but I was unsure.
The problem also exists in Windows 10 and 11 environments.
This phenomenon was not experienced with a Realtek network card tested in the same environment.
The Microsoft-Windows-Wired-AutoConfig/Diagnostics log notes the phenomenon as follows:
21004 DeviceLayerSendPacket operation failed, 0x1F
21026 Adapter ({.. I219-LM ..}): SendOneXPacket operation failed: 0x1F
(Tried a couple of settings such as turning off energy saving, turning off Gb speed, but no change resulted from this point of view.)

I would love to read any progress.

Thanks & Regards!

Answer 1

The problem also occurs with drivers provided by MS.)

What driver exactly?

Answer 2

Yes, I raised this issue with Intel as well.

(Maybe I didn't make it clear:

As it turns out, the problem is not only seen on Intel network cards.

The problem also occurs with drivers provided by MS.)

Regardless of Intel:

"startPeriod: Specifies the length of time, in seconds, to wait before an EAPOL-Start is sent."

Compared to what would this delay the launch (at first I thought about the profile application, but I don't see any effect)?

Thanks!

Answer 3

Is this the same question that you asked on the Intel Community?

I219-LM DeviceLayerSendPacket Error - Intel Community

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

As I explained previously, the issue is not related to Windows, and this is Intel's I219-LM network card. I would suggest you continue waiting for a response on the Intel Community, as the experts there are more familiar with the relevant product and can provide more accurate answers.

Answer 4

Hello Yuhao Li!

More information was obtained.

Interruption of the EAP handshake also affects other network cards, and also occurs with network card adapters provided by MS (I219-LM 12.19.1.32).

The problem can also be detected with EAP-TLS, for example.

By setting OneX reauth to 2 sec, the error can be suppressed because the 2nd authentication success does not wait for the default 18 seconds.

If I delay the network connection by a few seconds, the problem does not occur and the first attempt is also successful!

In the OneX/diag log, there is no record of the last packet of the (interrupted) handshake (which is clearly visible from wireshark)!

EapHost/Debug logging stops at this point!

We have many such clients based on Raduis (5440 Endpoint abandoned EAP session ...) and they can only authenticate with the 2nd attempt after the default 18 seconds.

Thank you!

Answer 5

Hello, adorj706

Welcome to Microsoft Community.

Based on the information you provided, the issue seems to occur in both Windows 10 and Windows 11 environments, despite clean installations of the latest drivers from OEM (HP) and Intel. It's likely that the problem is unrelated to the operating system or drivers. Considering that the issue doesn't occur with the Realtek network card in the same environment, it could be due to compatibility issues or specific configurations required by the Intel I219-LM network adapter. This is not something Microsoft can resolve since it's not a Microsoft product.

However, I found an article that might be related to the issue you're experiencing:

KB5014754—Certificate-based authentication changes on Windows domain controllers - Microsoft Support

Different network cards may have variations in how they handle certificate mapping due to different implementations. You can compare the certificates used by Intel and Realtek network cards for authentication and check if there are any differences in the subject, issuer, or UPN fields. Additionally, you can contact the network card manufacturer to learn more about how they support certificate mapping methods.

Please note that making changes to the registry can have significant impacts on the system, so be cautious. For added protection, before making edits based on officially published Microsoft documentation, be sure to back up the registry. Then you can restore it if a problem occurs: How to open Registry Editor in Windows - Microsoft Support

Yuhao Li

Microsoft Community Technical Support