The problem:

"Network cable disconnected" error after installing PROSet software suite on a SuperMicro blade nodes with B1SA4-2750F mainboard and Intel i354 2.5 Gbe Backplane Network adapters (x2).

I need teaming and VLANs features from PROSet suite, that`s why i`m using that software. If only the drivers are installed, both NICs works fine, but in Windows 8.1 there are no teaming feature - tested also with PowerShell.

Tested also with Windows 10, Windows Server 2012/2012 r2 - same issue - if only drivers are added (doesn`t matter if they are installed from software suite or from Device Manager), both NICs works fine, no matter how many times I`ve restart the machine. Windows 10 have teaming from PowerShell, but can`t define VLANs...

If PROSet suite is installed, both NICs change their status at "Network Cable Unplugged". The only resolution for this issue i`ve found so far (not always) is Right Button on adapter=> Properties=> Configure - after that, the adapter changes his status normal, but if machine is restarted, networks are disconnected again...

I`ve installed a lot of different versions of Intel PROSet software, tested with Unplug/Plug blade nodes, also with changing blade nodes position - no result.

Any resolution?

Ok. I have an Elitebook 840 G2, I once used connectify to share my work wifi to my other devices and it did work. But after updating my OS to Windows 10 it stopped working.

When i did "netsh wlan show drivers"

Interface name: Wi-Fi

    Driver                    : Intel(R) Dual Band Wireless-N 7265

    Vendor                    : Intel Corporation

    Provider                  : Intel

    Date                      : 6/22/2015

    Version                   : 18.11.0.8

    INF file                  : C:\WINDOWS\INF\oem81.inf

    Files                     : 3 total

                                C:\WINDOWS\system32\DRIVERS\Netwtw02.sys

                                C:\WINDOWS\system32\DRIVERS\Netwfw02.dat

                                C:\WINDOWS\system32\DRIVERS\vwifibus.sys

    Type                      : Native Wi-Fi Driver

    Radio types supported     : 802.11b 802.11g 802.11n 802.11a

    FIPS 140-2 mode supported : Yes

    802.11w Management Frame Protection supported : Yes

    Hosted network supported  : No

    Authentication and cipher supported in infrastructure mode:

                                Open            None

                                Open            WEP-40bit

                                Open            WEP-104bit

                                Open            WEP

                                WPA-Enterprise  TKIP

                                WPA-Enterprise  CCMP

                                WPA-Personal    TKIP

                                WPA-Personal    CCMP

                                WPA2-Enterprise TKIP

                                WPA2-Enterprise CCMP

                                WPA2-Personal   TKIP

                                WPA2-Personal   CCMP

                                Open            Vendor defined

                                Vendor defined  Vendor defined

    Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)

=> I then uninstalled my driver and installed a clean one from the intel website.
And in device manager  "Microsoft Hosted Network Virtual Apdapter" wasn't there anymore...

Did i do something wrong.

Please Help

Please let me know the procedure to downgrade NVM on X710

Hey,

I created 2 VFs on a 10 Gigabit port (Intel 82599 10 Gigabit NIC).

Should only VFs be used as 2 5-Gigabit virtual ports?

Or PF is also usable? If it is, then if I use both PF and VFs - each of them gets 3.33-Gigabit of throughput?

Can I assign both PF and VFs to a single VM?

What is the recommeded use?

Thanks,

Shaham

Hi,

I am facing issue with i40e driver for Ethernet Converged Network Adopter X710 while using it with 10G SFPs (Fiberxon).

How can I enable an option for allow unsupported sfp in i40e (version 1.2.48) driver?

Thanks in advance,

Ishwar.

Hi,

   I need to transmit/receive raw Ethernet packet for fast communication in Windows 7+. Is there a way to do that directly with Intel NIC driver or API ?

Hello all,

This is my first post.

I upgraded my dell precision m4800 this weekend at home. When I came into work this morning I discovered I cannot talk to  our management vlan. After some research I found that I need to install the new drivers for windows 10.

I downloaded the x64 driver for i127-LM, unpacked and ran it. Its gets 3/4 of the way through and freezes. I then have to restart my laptop to be able to try the install again. Have tried this about 5 times, then redownloaded the file and tried again with nothing but freezes at the 3/4 mark.

Can anyone out there help with this, I can't do my job if I can't access the management VLAN.

thanks

Max

Recently we got a few new servers. All have identical configuration. Each has dual E5-2620v3 2.4Ghz CPUs, 128GiB RAM (8 x 16GiB DDR4 DIMMs), 1 dual-40G XL710, and two dual 10G SPF+ mezz cards (i.e. 4 x 10G SPF+ ports). All of them run CentOS 7.1 x86_64.  These XL710s are connected to the 40G ports of QCT LY8 switches using genuine Intel QSFP+ DACs.  All 10G SPF+ ports are connected to Arista 7280SE-68 switches, but using third party DACs.  All systems have been so far minimally tuned:

• In each's BIOS, the pre-defined "High Performance" profile is selected, furthermore, Intel I/OAT is enabled, VT-d is disabled (We don't need them to run virtual machines, they are for HPC applications).
• In each's CentOS, the tuned-adm active is set to network-throughput.
  

After the servers have been setup, we have been using iperf3 to run long-running tests among such servers. So far, we have observed consistent packet drops on the receiving side.  An example:

[root@sc2u1n0 ~]# netstat -i

Kernel Interface table

Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg

ens10f0  9000 236406987      0      0 0      247785514      0      0      0 BMRU

ens1f0    9000 363116387      0  2391 0      2370529766      0      0      0 BMRU

ens1f1    9000 382484140      0  2248 0      2098335636      0      0      0 BMRU

ens20f0  9000 565532361      0  2258 0      1472188440      0      0      0 BMRU

ens20f1  9000 519587804      0  4225 0      5471601950      0      0      0 BMRU

lo      65536 19058603      0      0 0      19058603      0      0      0 LRU

We have also observed iperf3 retries at the beginning of a test session and often, during a session (not as often however).  Two examples:

40G pairs:

$ iperf3 -c 192.168.11.100  -i 1 -t 10

Connecting to host 192.168.11.100, port 5201

[  4] local 192.168.11.103 port 59351 connected to 192.168.11.100 port 5201

[ ID] Interval          Transfer    Bandwidth      Retr  Cwnd

[  4]  0.00-1.00  sec  2.77 GBytes  23.8 Gbits/sec  54    655 KBytes  

[  4]  1.00-2.00  sec  4.26 GBytes  36.6 Gbits/sec    0  1.52 MBytes  

[  4]  2.00-3.00  sec  4.61 GBytes  39.6 Gbits/sec    0  2.12 MBytes  

[  4]  3.00-4.00  sec  4.53 GBytes  38.9 Gbits/sec    0  2.57 MBytes  

[  4]  4.00-5.00  sec  4.00 GBytes  34.4 Gbits/sec    7  1.42 MBytes  

[  4]  5.00-6.00  sec  4.61 GBytes  39.6 Gbits/sec    0  2.01 MBytes  

[  4]  6.00-7.00  sec  4.61 GBytes  39.6 Gbits/sec    0  2.47 MBytes  

[  4]  7.00-8.00  sec  4.61 GBytes  39.6 Gbits/sec    0  2.88 MBytes  

[  4]  8.00-9.00  sec  4.61 GBytes  39.6 Gbits/sec    0  3.21 MBytes  

[  4]  9.00-10.00  sec  4.61 GBytes  39.6 Gbits/sec    0  3.52 MBytes  

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval          Transfer    Bandwidth      Retr

[  4]  0.00-10.00  sec  43.2 GBytes  37.1 Gbits/sec  61            sender

[  4]  0.00-10.00  sec  43.2 GBytes  37.1 Gbits/sec                  receiver

82599 powered 10G pairs:

$ iperf3 -c 192.168.15.100 -i 1 -t 10

Connecting to host 192.168.15.100, port 5201

[  4] local 192.168.16.101 port 53464 connected to 192.168.15.100 port 5201

[ ID] Interval          Transfer    Bandwidth      Retr  Cwnd

[  4]  0.00-1.00  sec  1.05 GBytes  9.05 Gbits/sec  722  1.97 MBytes  

[  4]  1.00-2.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.80 MBytes  

[  4]  2.00-3.00  sec  1.10 GBytes  9.42 Gbits/sec  23  2.15 MBytes  

[  4]  3.00-4.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.16 MBytes  

[  4]  4.00-5.00  sec  1.09 GBytes  9.41 Gbits/sec    0  2.16 MBytes  

[  4]  5.00-6.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.17 MBytes  

[  4]  6.00-7.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.18 MBytes  

[  4]  7.00-8.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.22 MBytes  

[  4]  8.00-9.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.27 MBytes  

[  4]  9.00-10.00  sec  1.10 GBytes  9.42 Gbits/sec    0  2.34 MBytes  

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval          Transfer    Bandwidth      Retr

[  4]  0.00-10.00  sec  10.9 GBytes  9.38 Gbits/sec  745            sender

[  4]  0.00-10.00  sec  10.9 GBytes  9.37 Gbits/sec                  receiver

Looking around, I ran into a 40G NIC Tuning article on the DOE Energy Science Network fast data site, quoted "At the present time (February 2015), CPU clock rate still matters a lot for 40G hosts.  In general, higher CPU clock rate is far more important than high core count for a 40G host.  In general, you can expect it to be very difficult to achieve 40G performance with a CPU that runs more slowly than 3GHz per core."  We don't have such fast CPUs The E5-2620v3 is a mid-range CPU from the Basic category, not even the Performance category. So,

• Are our servers too rich in NICs, but under-powered CPU-wise? 
• Is there anything that we can do to get these servers to behave at least reasonably?  Especially, not dropping packets?

BTW, a few days ago we updated all servers with the most recent Intel stable i40e and ixgbe drivers, but we have not run the set_irq_affinity CPU yet. Neither we have tuned the NIC (e.g. adjusting rx-usecs value etc). The reason is because each server runs two highly concurrent applications which tend to use all the cores. We are afraid that to use the set_irq_affinity script, we may negatively impact the performance of our applications. But if Intel folks consider running the script beneficial, we are willing to try.

Regards,

-- Zack

Hi,

I am having difficulties programming the I210 Flash. In lanconf the flash option to write is greyed out.

If I try to write update NVM image from file in lanconf, I get an error saying the device ID is 0531 but the file ID is 1533.

The Flash I am using is SST25VF040B. The security_enable strapping is enabled with a 3k3 pull down.

If I place a pre-programmed Flash device onto the board in place of the empty device everything works fine. However pre-programming is not an option as we would really like to be able to program them on board.

I really appreciate any help on this matter.

Please let me know if you require any further information.

Kyle.

Hello everyone,

Since I upgrade my PC from Windows 7 Pro to Windows 10 Pro several days ago, I do have issue to get my on-board network card running. My Hardware is:

Mainboard: ASUS P8Z68-V Pro/Gen3

On-Board NIC: Intel 82579V Gigabit

Let me try to explain my problem. The LAN Adapter is disapearing completly every few seconds, if I do have the device manager open, I can see a refreh all few seconds. In the network and sharing center I can see the LAN adapter disapering. In the event log I can see the following error (I am trying to translate it from German)

- For the network adapter "Intel...." a reset operation was started. While the hardware is beeing reset, network connections are unavailble. Reason: The network driver did send a reset operation. die network adapter was reseted 150 times since the last initialization

The original error message can be found in the attachment.

Regarding to the driver, I am using the latest Windows 10 driver which I found on the intel page (Screenshot is attached)

- driver date: 15.02.2015

- driver version: 12.12.140.22

I found something in an other community that disabled EEE will solve the issue - but it did not.

Really hope you guys can help me out.

Thanks.

Hello,

Need some help to figure out if I am missing something.  I've been trying to set 'speed and duplex' value under Link Speed to 1 Gbps, but get an error message - SetSetting failed

I've tried the same with and without connecting network cable to the port. 

Appreciate comments/suggestions.  Thanks!

Screenshot shown below:

Hi,

I'm using an ASRock Rack EPC612D8A-TB motherboard with two Intel onboard NICs (I210 (Ethernet 2) and I217-LM (Ethernet)), running Win 8.1 Pro x64 with all Windows Updates installed and the latest Intel Ethernet driver package (20.2.3001.0). My problem is with the I217-LM, according to the Intel spec sheet it does support RSS (cp. figure on page 2).

In the I217-LM's advanced driver settings there is an option to enable and disable RSS. However Windows itself always says that the I217-LM is not RSS-capable.

The same option in the I210 driver options has the expected effect: With the PowerShell command get-SmbClientNetworkInterface you can see the RSS capability changing from True to False and vice versa.

Can anyone tell why the I217-LM is not getting the RSS feature?

Further system details:
CPU: Xeon E5-1620-V3

RAM: 2 x 16 GiB Crucial DDR4-2133 ECC

The motherboard does not have a later BIOS/UEFI release than the one installed.

Thank you very much for your help!

I have an issue with my onboard network card on an ASUS Z170 Pro Gaming mainboard. I get disconnects all the time and i had no problem at all before i got the mainboard with the Intel NIC. The error id "e1cexpress eventID: 27" is occuring in the Windows event log. It is 100% not a router or internet provider problem as everything works fine with other devices connected to the same network.

I tried many things posted in other threads here that looked like similar issues but the problem still exists.

The Intel i219-V is not even listed in the intel download center, so i only found up to date drivers on other computer manufacturer websites. I also tried to set the ethernet energy feature off, but it does not help. Maybe it delays the problem a little bit as it only occurs every 3 or 4 hours now.

But as i am also playing online-games, this is an absolutely no-go as it kicked me out of some games a few times already while i was playing.

I am using Windows 10 Pro. Currently i have installed the drivers that came with the mainboard (from the driver CD).

Maybe some other people with this mainboard also have this issue and found a solution. Please help.

My PC is installed with Intel(R) 82567LM-3 Gigabit Network Connection (version 12.10.13.0). Could anyone please tell me if this is compatible with Windows 10, and if not, what version do I need to download. I am currently running Windows 7 Pro.

I'm working on virtual router evaluation with SR-IOV now. My virtual router cannot speak and has proper OSPF relation with external box. Does anyone know how to look into the synopsis deeper? Here are my setup.

1. CSR1K, Cisco virtual router which is running over a server box speaks with an external box

2. SR-IOV is enabled on the server

3. the external box speaks with CSR1K, that means OSPF neighbor has been established

4. CSR1K cannot speak with the external box, it looks that CSR1K cannot recieve any MC/BC packet

5. ethtool shows ixgbe is running with 4.0.1-k-rh7.1, ixgbevf is running with 2.12.1-k

Any input would help me out.

Thanks in advance,

Yuichiro

L.S.

In my latest laptop (HP 650G1, feb-2015) running windows 8.1-64, my lan card is an Intel I217-V.

After installing the proset software, I should be able to configure VLAN's. I did this on my previous laptop once in a while to check VLAN configurations. Great function.

On this latest laptop, trying to configure VLAN's almost alway's results in a BSOD with the message "BAD POOL CALLER"

Since then I did the following:

- update drivers

- full uninstall / reboot / install of intel Proset

- manual cleanup of the registry, (There appear to get one or more ians miniport devices that get stuck in my device manager). Specially HKLM\SYSTEM\CurrentControlset\Enum\ROOT\IANSMINIPORT

(Tricky to clean up. Use psexec -i -s regedt32.exe to get permission, then regdelnull to clean up data, then able to remove)

But even after full clean-up after uninstall / reboot / install / reboot does not appear to solve the issue.

Any help apreciated.

Thomas Roes

I am creating an windows embedded image for different Intel servers.

Here after installing ProSet and ProAdmin I can able to see Advanced Network Option in device properties.

But after doing sysprep in source machine and restarted the machine and now the Advanced options are not available.

I have an issue with my onboard network card on an ASUS Z170 Pro Gaming mainboard. The network works ok with windows 7 but when i upgrade to windows 10 I'm getting disconnects & time outs all the time. I am using the driver downloaded from the Asus web site. I also did a clean install of windows 10 with the same results  I have tried various games on steam in windows 10 & all seem to work ok but if I try to download anything on steam its very slow & stop starts alot. I have since gone back to windows 7 & all is working again. Have also searched for other drivers but was not able to find any. This seems to be a driver issue. Any help would be welcome.

Good Morning All,

First id like to thank you all in advance for any assistance given.

I'm here today because I am building  a sweet SAN/NAS for work, and I'm having trouble identifying the proper 10GBe Nic's to use for the connection between the SAN/NAS and the hypervisors.

I think I have nailed it down to this product family "Intel® Ethernet Converged Network Adapter X520 Product Family"

But am still unsure on which adapter to choose.

I'm still teetering back and forth between 10GBe copper and fiber, I think I would prefer copper but am flexible.

Any suggestions?

The plan is to use ISCSI over IP. There will be 2x Primary Hyper-V boxes connecting to the SAN/NAS via 10GBe, we will also have a few other hyper-v boxes connected to this san via existing 1GBe connections (backup/ play boxes)

Again thank you for any advice given.

Hi,

I have a problem using Wake-On-Lan (WOL) when Windows 10 has "Fast Start-Up" enabled.

Specs of system:

Operating System: Windows 10 Pro 64-bit

CPU: Intel Core i5

RAM: 8.00GB DDR3

Motherboard: ASUS H97M-PLUS

SSD: INTEL SSDSC2CW180A

This is an office PC which needs to WOL for its nightly remote backup and I would really like it to "fast start-up".

I have the most up to date Intel LAN Driver V12.13.17.4

With "fast start-up" off WOL works perfectly. With "fast start-up" on WOL refuses to work.

I have triedthe following:

• "Fast Start-Up" ON/OFF
• "Resting condition" Shutdown/Hibernate/Sleep
• "Hybrid Sleep" Visible/Not Visible
• RG_SZ "WakeOnFastStartup" 0/1

These are my results:

As you can see there is a not very useful corner-case, where the default position for Windows 10 Professional (Fast Start-Up = ON, Resting Condition = Shutdown, Hybrid Sleep = Not visible and WakeOnFastStartup = 0) does not response to a WOL magic packet.

I would be grateful for some help with this issue.

Many thanks,

theduck01