environment:

Redhat 7.4

ixgbe, ixgbevf  (82599es ethernet controller)

is it possible to classify the incoming traffic solely based on vlan than on mac.  (ie from pf to vf only based on vlan and ignoring mac address)

My ISP (Spectrum) has upgraded my service to 200MBPS.  However I can connect at more than 94 MBPS.

I downloaded the latest driver from Itel and when I select the 1GB option in Windows I loose network connectivity.

Had the ISP tech shoot the line and do a speed test thru my cabling and they can get up to 240MBPS.

Is this a NIC issue?

Environment

ASUS Z170-A Gaming computer

WIndows 7 PRO OS

Netgear NIghthawk AC 1900

DOCSYS Modem provided by Spectrum

Any ideas?

Canopygirl

I want to create Multi vlan for network card I210 and I217-LM on my PC.

but I always got "one or more VLAN(s) could not be created, Please check the adapter status and try again", meanwhile network card disabled.

my operation system is windows 764bit Ultimate.

after I tried several times, there were several virtual network card created, but no vlan. I even can not uninstall the created virtual network card.

anybody can give some suggestion?

When I boot my Lenovo X201i laptop with Win 7 64-bit I get the error message:" Initializing Intel Boot Agent GE V1.3.51

PXE-E05 The LAN adapter's NVM configuration is corrupted or has not been initialized. The Boot Agent cannot continue"

However, the computer boots, but after several weeks of flakey behavior in which I need the network troubleshooter to reestablish connection, now I cannot access the network at all. The entire time network troubleshooter has been returning the message:

The Intel(R) 82577LC Gigabit Network Connection adapter is experiencing driver- or hardware-related problems

and The Intel(R) WiFi Link 1000 BGN adapter is experiencing driver- or hardware-related problems 

The troubleshooter listed the following details:

Diagnostics Information (Network Adapter) 

Details about network adapter diagnosis:

Network adapter Local Area Connection 2 driver information:

   Description . . . . . . . . . . : Intel(R) 82577LC Gigabit Network Connection

   Manufacturer  . . . . . . . . . : Intel

   Provider  . . . . . . . . . . . : Intel

   Version   . . . . . . . . . . . : 11.5.10.0

   Inf File Name . . . . . . . . . : C:\Windows\INF\oem4.inf

   Inf File Date . . . . . . . . . : יום שני 14 דצמבר 2009  07:37:10

   Section Name  . . . . . . . . . : E10EB.6.1.1

   Hardware ID . . . . . . . . . . : pci\ven_8086&dev_10eb

   Instance Status Flags . . . . . : 0x1802400

   Device Manager Status Code  . . : 10

   IfType  . . . . . . . . . . . . : 6

   Physical Media Type . . . . . . : 14 . : 9

There is much more information provided, but I will only post if told that it is relevant.

Updating the driver did not help. What is status code 10?

Is this indeed a situation in which the 82577LC can be repaired? If so, where can I find instructions on how to do it?

Thanks

Paul

The Intel(R) 82577LC Gigabit Network Connection adapter is experiencing driver- or hardware-related problems

Dear all:

    We have a problem of windows 2008 R2 NIC teaming problem.we use two Intel 82599 10 gigabit dual port network adapters for nic teaming, but recently ,for  unknown reasons,the primary network adapter switch from Primary adapter to secondary adapter.When switching, we can see thousands of switch in the network switch.Please help：

1. how can I find which process or software will cause the teaming switch?

2. we can only see the switch happened one time in windows log, why there were thousands of switch in network switch?

I compiled and installed the network adapter driver for PCIe 40 Gb Ethernet(version 3.4.2). The driver is also loaded in the kernel successfully (Ubuntu 16.04). However, when I connect QSFP+ cables I am getting the following error message:

Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

Is this because I am not using Intel QSFP+ cables?

Is there any way to allow unsupported SFP?

Best,

Marjan

Hello,

Can I please ask clarifications on XL710 on VLAN steering. I have few questions regarding it on top of what was asked before. Really appreciate for your valuable input please

1. 7.4.8.4 "VEB/VEPA Switching Algorithm" states that filtering happens by MAC+VLAN. It is impossible to perform filtering by VLAN only, as I understand it is HW limitation.

XL710 has something called "7.4.8.2 S-comp Forwarding Algorithm" which looks like exactly what we want. It does forwarding of packets to specific VSI based on S-tag. S-tag is a part of "7.4.9.5.5.1 Add VSI (0x0210)" command. I guess we can configure several VSIs for expected S-tags. Can you help us understand how to use this algorithm please?

As I understood "port virtualizer" (7.4.2.4.3 "Cascaded VEB and port virtualizers") supposed to be configured to use this switching algorithm. In i40e driver (kernel or DPDK) I do not see anything related to configuration of "port virtualizers", except "i40e_aq_add_pvirt" function which is not used anywhere.

Is it possible to configure "port virtualizer" with existing latest i40e driver?

Another question is about "i40e_aq_set_vsi_uc_promisc_on_vlan" function in i40e driver (7.4.9.5.9.5 "Set VSI Promiscuous Modes"). It enables promiscuous mode for unicast packets with specific VLAN, so all packets with that VLAN will be replicated to configured VSI. In XL710 datasheet I`ve found that it works only in "Cloud VEB algorithm" (7.4.8.6). Can we somehow enable this algorithm with existing i40e drivers?

Thannk you so much

Hi.

I am having problems with I219-V VLAN tag. Whan adding  a tag I get blue screen every single time., reason Bad_pool_caller.

First step I am adding new VLAN in VLAN tab from Intel Ethernet conection I219-V:

And when adding new VLAN tag, let's say 13 it crashes:

I don't even get a chance to press second OK in Intel window, it crashes right here. It says Configuring for two seconds, maybe tree and the blue screen. I can make it anytime I want.
I tried with versions 12.17.8.7 and 12.15.25.6:

I have Lenovo T470s. Any help would be gratefull.

Regards

Hi there,

I'm using X710-DA4 with SR-IOV mode on Skylake servers.

latest fw and drivers (i40e) installed on system. and vf driver is added into blacklist.

there is a VF that belongs to a PF. and that VF is attached to a VM.

after that, I tried ping from VM to a pc that connected to the server port that has the PF.

it works well. ping packets are received by the pc.

the problem (or different behavior) is that,

even the PF link goes down using "ifconfig xx down or ip link set xxx down" but the VF still sending packet to the pc.

is this right behavior on X710/XL710?

if yes, any architectural/tech background that I can get?

Regards,

Hello,

I have a network adapter "EXPI9301CTBLK", which I wanted to flash now.

I have entered the following commands "BootUtil -SAVEIMAGE -FILE = Backup.FLB" and "BootUtil -FE -ALL". Then I wanted to flash the new firmware with "BootUtil -UP = EFI -ALL-FILE = BOOTIMG.FLB".

Unfortunately, something went wrong.

First came a message that the Nic can not be initialized.

And now the adapter is no longer recognized, so I can not flash back.

Is the adapter still somehow save?

Please excuse my bad English, I write with translator.

Thanks in advance.

Good morning!

I have a problem with the 82579LM card.

Let me start with a description of the situation, we have been producing mining machines for the explosion-risk zone for years. We have been using an Ethernet connection of a PLC with a PC for about 10 years. The connection is 4-core 10Mb. Between the PC and the PLC, ethernet separators (EI-0D2-10Y-10B from pepperl-fuchs) are used. These barriers are "transparent".

For many years, this configuration works with an industrial PC of B & R APC620, which has an Intel PRO / 100 VE card. Currently, its production has ended, therefore I am installing a newer APC910 model. This model has an INTEL 82579LM network card.

Unfortunately, I can not configure it to work in this configuration.

If I omit the Ethernet separators, the connection works.

If I apply the switch between the PC and the barrier, the connection works.

If I install a USB Ethernet card to the computer, the connection works.

If I put an older type of computer in place of the new one, it also works.

If I connect the computer in accordance with the diagram in place of the old one, the system detects the network, however with a mistake.

The system is Windows 7 Standard Embedded.

The most up-to-date Bios, the most up-to-date drivers.

Please help

Regards

Lukasz

Hello Sharon,

I have a Intel Gigabit CT Desktop Adapter, EXPI9301CTBLK schematics received from INTEL.

I have some of the doubts on the data lines Being Used.

PURPOSE OF-

1.NC_SI

2. NVM - Non Volatile Memory.

3. SMBUs.

4.External Power Transistor Options.

5.PCIe differential Data.

PFA files of 82574l section for clarification.

Also I have attached our schematics according to the Reference Design.

Kindly Let I know If there are any errors.

PLEASE DO HELP.

Regards,

Saravana

Does the X540-T2 NIC supported on Windows Server 2016?

Hello;

I have a Box (supermicro) with:

S.O :    FreeBSD 11.1-STABLE (FreeNAS)

NIC: - Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02).

- Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k

- dev.ixl.0.fw_version: fw 5.0.40043 api 1.5 nvm 5.05 etid 80002a43 oem 1.261.0

I have issues with the connection  Flapping on the interfaces 10G and a lot of messages "ixl0: Malicious Driver Detection event 2 on TX queue 2, pf number 0"

I m trying to Upgrade the Firmware to 6.0.1; but the procedure (./nvmupdate64e) says:

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) I350 Gigabit Network Connection  1.99  1521 00:001     Update not

                                                                                                             available

02) Intel(R) Ethernet Controller X710 for     5.05  1572 00:002     Update not

    10GbE SFP+                                                                                  available

Tool execution completed with the following status: Device not found.

Hi.

I am having problems with 82574L

Hardware :

03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

System:

Centos 7.3   kernel：3.10.0-514.el7.x86_64

Output from message

Feb 26 20:50:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 20:50:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 22:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 22:10:04 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 22:40:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 22:40:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 23:20:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 23:20:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 23:30:02 localhost kernel: e1000e: slot0_GE2 NIC Link is Down

Feb 26 23:30:02 localhost kernel: e1000e: slot0_GE2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 27 01:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 27 01:10:04 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 27 03:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 27 03:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

modinfo

filename:       /lib/modules/3.10.0-514.el7.x86_64/updates/drivers/net/ethernet/intel/e1000e/e1000e.ko

version:        3.3.6-NAPI

license:        GPL

description:    Intel(R) PRO/1000 Network Driver

author:         Intel Corporation, <linux.nics@intel.com>

rhelversion:    7.3

srcversion:     6453212B70344504D53DE09

alias:          pci:v00008086d0000105Esv*sd*bc*sc*i*

depends:        ptp

vermagic:       3.10.0-514.el7.x86_64 SMP mod_unload modversions

parm:           copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)

parm:           TxIntDelay:Transmit Interrupt Delay (array of int)

parm:           TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)

parm:           RxIntDelay:Receive Interrupt Delay (array of int)

parm:           RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)

parm:           InterruptThrottleRate:Interrupt Throttling Rate (array of int)

parm:           IntMode:Interrupt Mode (array of int)

parm:           SmartPowerDownEnable:Enable PHY smart power down (array of int)

parm:           KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)

parm:           CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)

parm:           EEE:Enable/disable on parts that support the feature (array of int)

parm:           Node:[ROUTING] Node to allocate memory on, default -1 (array of int)

parm:           debug:Debug level (0=none,...,16=all) (int)

[root@localhost ~]# ethtool -k slot0_GE4

Features for slot0_GE4:

rx-checksumming: on

tx-checksumming: on

tx-checksum-ipv4: off [fixed]

tx-checksum-ip-generic: on

tx-checksum-ipv6: off [fixed]

tx-checksum-fcoe-crc: off [fixed]

tx-checksum-sctp: off [fixed]

scatter-gather: on

tx-scatter-gather: on

tx-scatter-gather-fraglist: off [fixed]

tcp-segmentation-offload: on

tx-tcp-segmentation: on

tx-tcp-ecn-segmentation: off [fixed]

tx-tcp6-segmentation: on

udp-fragmentation-offload: off [fixed]

generic-segmentation-offload: on

generic-receive-offload: on

large-receive-offload: off [fixed]

rx-vlan-offload: on

tx-vlan-offload: on

ntuple-filters: off [fixed]

receive-hashing: on

highdma: on [fixed]

rx-vlan-filter: on [fixed]

vlan-challenged: off [fixed]

tx-lockless: off [fixed]

netns-local: off [fixed]

tx-gso-robust: off [fixed]

tx-fcoe-segmentation: off [fixed]

tx-gre-segmentation: off [fixed]

tx-ipip-segmentation: off [fixed]

tx-sit-segmentation: off [fixed]

tx-udp_tnl-segmentation: off [fixed]

tx-mpls-segmentation: off [fixed]

fcoe-mtu: off [fixed]

tx-nocache-copy: off

loopback: off [fixed]

rx-fcs: off

rx-all: off

tx-vlan-stag-hw-insert: off [fixed]

rx-vlan-stag-hw-parse: off [fixed]

rx-vlan-stag-filter: off [fixed]

busy-poll: off [fixed]

tx-sctp-segmentation: off [fixed]

l2-fwd-offload: off [fixed]

hw-tc-offload: off [fixed]

[root@localhost ~]#

Hi,

I am observing a strange issue with i354 when auto-negotiation is turned off.

The device I have has 6 ethernet ports. Port 1 and 2 are based on i210 and port

3 to 6 are based on i354 (connected thru an external PHY). The CPU is Atom

Rangeley (4 core).

I have connected ports 3 and 4 back to back with an external cable. When the

link is forced to 100M/Full duplex with auto-negotiation off on both the ports,

the link does not come up.

Whereas the link comes up fine when eth3 (i354) and eth1 (i210) are connected

back to back and forced to 100M/Full duplex with auto-negotiation off.

This issue is seen with linux kernel (ubuntu 14.04).

Is this a known issue ?

Following are logs when running the test using ethtool from linux

admin@Ananda-Desk:~$ lspci | grep Ethernet

00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth2

00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth3

00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth4

00:14.3 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth5

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth0

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth1

admin@Ananda-Desk:~$ ethtool -i eth3

driver: igb

version: 5.2.13-k

firmware-version: 0.0.0

bus-info: 0000:00:14.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

[Force 100M/Full on eth3]

admin@Ananda-Desk:~$ sudo ethtool -s eth3 autoneg off duplex full speed 100

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: Yes

        Speed: 100Mb/s

        Duplex: Half

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: on

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

[Force 100M/Full on eth4]

admin@Ananda-Desk:~$ sudo ethtool -s eth4 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<

[Connect cables between eth1 and eth3]

[Force 100M/Full on eth1]

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ sudo ethtool -s eth1 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth1

Settings for eth1:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

I am sorry to hijack this thread.

We are also seeing the similar issue at our hosts. After upgrading Intel NIC firmware, the NICs do not detect the link anymore. They were fine before the NIC firmware update. We tried updating i40e driver to the latest available, but it did not help.

Host information

Model                                            Dell R630

Bios Version                                 2.7.1

I have intel 82579LM network card in my DELL M6700. Windows version 1709 16299.309. Intel PROSet Version: 23.1.100.0. Intel Driver: 12.15.31.4. When I creating VLAN the error occured:

"One or more VLANs could not be created. Please check the adapter status and try again."

Can anybody help me. Thanks.

Hi all

We are currently experiencing an issue on several Dell latitude 5480/5580 laptops that have the Intel I219-LM ethernet adapter.

All laptops are running the latest version of Windows 10. Plugging in Ethernet to these laptops, they receive the correct DHCP information. the correct DHCP and DNS servers are displayed in the ethernet properties and they receive the correct IP information. However, after receiving the information from our DHCP server, we are not able to ping: default gateway, DHCP, Active Directory, DNS, or any other internal or external resource.

These are connected through Extreme Summit Switches. Connecting the laptops to an external dock with ethernet capability will allow the laptop to regain network connectivity and act normally. The drivers are fully up-to-date. Working on a campus with a number of buildings, separated by VLAN/subnets, we can try troubleshooting techniques and maybe eventually get it to work, either by sheer tenacity or dumb luck -- manually inserting it into our network access control, enabling/disabling ports, etc. But there is no consistent way to fix the issue, it's hit-or-miss.

I'm wondering if there is anyone else that is experiencing this issue or has experienced this issue, or if I can get any feedback regarding a way to troubleshoot.

If any more information is necessary that I've left out please let me know and I'll be happy to supply that.

Thank you.

Hello,

I'm having this same exact problem with several HP ProDesk 600 G3 SFF machines at different offices all running Windows 10 x64 Pro.  They're connecting to Juniper EX4200 switches.  For no reason at all the NIC will go offline then come up and down on its own (you can see the system tray LAN indicator going from a red X to a yellow exclamation point)..  They won't re-negotiate DHCP leases and the event log on every machine has a bunch of Event ID 10400 entries that read:

"The network interface "Intel(R) Ethernet Connection (5) I219-LM" has begun resetting.  There will be a momentary disruption in network connectivity while the hardware resets.

Reason: The network driver detected that its hardware has stopped responding to commands.

This network interface has reset 17 time(s) since it was last initialized."

These are followed by Event ID 27 from e1dexpress saying the "Network link is disconnected" which is then followed by Event ID 32 saying "Network link has been established at 1Gbps full duplex" and the cycle repeats over and over until the user reboots (which doesn't always fix the issue) or sometimes they just wait and anywhere from 5 minutes to 60 minutes later the problem resolves itself without any user intervention.

I've already updated them to the latest driver version but I'm still having this problem with dozens of machines at different locations?  Are they all faulty?  Seems unlikely to me.

Thank you,

-Tim