F5F Stay Refreshed Power Users Networks Search for IOCREST Intel NICs and similar products on Aliexpress (I225/6-v)

Search for IOCREST Intel NICs and similar products on Aliexpress (I225/6-v)

Search for IOCREST Intel NICs and similar products on Aliexpress (I225/6-v)

B
brobear7
Posting Freak
892
04-18-2019, 02:18 PM
#1
Hello, In one of the recent videos, an IOCREST M.2 10G adapter was suggested (brand logo from NCIX – maybe a stretch, but I’m curious if someone familiar could assist with a driver problem). I purchased two very inexpensive Intel NICs from Aliexpress and am encountering issues where the latest Intel wired version (28.3) reports an error about the "certificate of signature" expiring. Even using an older driver, the issue remains, though it’s less specific – sometimes it shows a generic code like "Code 10". I’ve learned these seem to be non-WHQL certified and there’s a guide on signing drivers yourself (link provided). This works on Windows 7, but not on Windows 10 because of stricter rules. The only workaround I found is disabling driver signature verification and putting Windows 10 in testing mode. The hardware appears to be from Intel, with the X570 Taichi and integrated cards functioning well. There are some community discussions, but no clear solution. PS: This card matches exactly what I have – here’s the link: https://www.amazon.com/IO-CREST-Ethernet...D3HMB?th=1. Also, my setup includes an X570Taichi with Intel I211 and AX200 integrated NICs, which all work smoothly in Ubuntu 22.04. One card shows the "igc" networking driver, another is Intel I226-v, and another is I225-v rev b3. On PS4 it’s running with a newer driver I signed myself, and on PS5 it’s fine. Let me know if you have more details!
B
brobear7
04-18-2019, 02:18 PM #1

Hello, In one of the recent videos, an IOCREST M.2 10G adapter was suggested (brand logo from NCIX – maybe a stretch, but I’m curious if someone familiar could assist with a driver problem). I purchased two very inexpensive Intel NICs from Aliexpress and am encountering issues where the latest Intel wired version (28.3) reports an error about the "certificate of signature" expiring. Even using an older driver, the issue remains, though it’s less specific – sometimes it shows a generic code like "Code 10". I’ve learned these seem to be non-WHQL certified and there’s a guide on signing drivers yourself (link provided). This works on Windows 7, but not on Windows 10 because of stricter rules. The only workaround I found is disabling driver signature verification and putting Windows 10 in testing mode. The hardware appears to be from Intel, with the X570 Taichi and integrated cards functioning well. There are some community discussions, but no clear solution. PS: This card matches exactly what I have – here’s the link: https://www.amazon.com/IO-CREST-Ethernet...D3HMB?th=1. Also, my setup includes an X570Taichi with Intel I211 and AX200 integrated NICs, which all work smoothly in Ubuntu 22.04. One card shows the "igc" networking driver, another is Intel I226-v, and another is I225-v rev b3. On PS4 it’s running with a newer driver I signed myself, and on PS5 it’s fine. Let me know if you have more details!

J
JXLPixels
Junior Member
22
04-20-2019, 01:04 AM
#2
A single NIC is connected to the desktop PC while another is linked via a Halo 2.5GB switch to a NAS. Transferring files from the Windows machine to a ZFS array on an SMB share runs smoothly with consistent performance and minimal interruptions.
J
JXLPixels
04-20-2019, 01:04 AM #2

A single NIC is connected to the desktop PC while another is linked via a Halo 2.5GB switch to a NAS. Transferring files from the Windows machine to a ZFS array on an SMB share runs smoothly with consistent performance and minimal interruptions.

N
N015iA
Member
209
04-20-2019, 05:55 AM
#3
Never tried this before. I was using an i225 B3 M.2 adapter from Ali for a while on my Windows 11 box with a PCIe to M.2 adapter, and it functioned properly. (I just had these two items from a past project, so it seemed like a temporary fix rather than purchasing a new NIC.) It seems driver signing should not affect the NIC itself, as long as the NIC matches the correct IDs in the driver's INF file—then it should work fine. Not very useful, though.
N
N015iA
04-20-2019, 05:55 AM #3

Never tried this before. I was using an i225 B3 M.2 adapter from Ali for a while on my Windows 11 box with a PCIe to M.2 adapter, and it functioned properly. (I just had these two items from a past project, so it seemed like a temporary fix rather than purchasing a new NIC.) It seems driver signing should not affect the NIC itself, as long as the NIC matches the correct IDs in the driver's INF file—then it should work fine. Not very useful, though.

B
BigB1129
Member
50
04-21-2019, 12:54 PM
#4
Wow, you're wondering if others face the same problem?
B
BigB1129
04-21-2019, 12:54 PM #4

Wow, you're wondering if others face the same problem?

J
jasonmbranson
Junior Member
14
04-27-2019, 10:51 PM
#5
It's an odd situation, since Ubuntu shows it should function properly.
J
jasonmbranson
04-27-2019, 10:51 PM #5

It's an odd situation, since Ubuntu shows it should function properly.