1 2 3 4 Previous Next 590 Replies Latest reply on Jun 19, 2017 2:37 AM by johnkristian Go to original post
      • 15. Re: I211/I217-V Windows 10 LACP teaming fails
        Nomgle

        "Important Note: In order to create Intel® ANS teams and VLANs on Microsoft Windows® 10, you must install the Microsoft Cumulative update located here:  Microsoft KB3081448.

        Failure to install the update will result in teams and VLANs that do not pass traffic."


        I note that this message above has now been removed from the download page - https://downloadcenter.intel.com/download/25016/Network-Adapter-Driver-for-Windows-10 - and replaced with a new message :

         

        Important Note:  Creating Intel® ANS teams and VLANs on Microsoft* Windows* 10 is currently not supported.  As a result, when created, teams and VLANs do not pass traffic.  We expect that ANS will be supported on Microsoft* Windows* 10 client in a future release.

         

        I have two systems running Intel I350 dual port cards.

        The first system was upgraded from Windows 8.1 to Windows 10, and once I had visited Windows update and checked for the presence of KB3081448, I installed the ProSet package and Teaming worked just fine.

        The second system has just been upgraded from Windows 7 to Windows 10 more recently. Even though I have applied all Windows Updates, KB3081448 is not listed in the update history - and Teaming doesn't pass any traffic on this machine. I can create the Team with no issue, it just doesn't send or receive anything !

         

        Hopefully a new driver pack appears soon...


        • 16. Re: I211/I217-V Windows 10 LACP teaming fails
          Nomgle

          Second time lucky - I've just rebooted and recreated the Team, and this time it's working fine !

           

          Both machines are now Teaming successfully with their I350 dual port cards in Windows 10.

          • 17. Re: I211/I217-V Windows 10 LACP teaming fails
            Zishy

            your adapters are supported currently. alot of others arent. thats why it worked with yours and it didnt work for the original poster and me

            • 18. Re: I211/I217-V Windows 10 LACP teaming fails
              wb_Intel

              HI Nomgle,

               

              Thank you for shaing your test result. glad to know it works for you.

               

              rgds,

              wb


              • 19. Re: I211/I217-V Windows 10 LACP teaming fails
                aga2015

                Can someone explain in lucid terms how anything is working given the explicit Intel  message (posted above) that states that Teaming isn't supported (yet) in Win 10 ?

                Sorrywb_Intel, you haven't helped the situation with any type of clarity.  How about we dispense with the mixed messages and determine what works and why.

                Thanks.

                • 20. Re: I211/I217-V Windows 10 LACP teaming fails
                  Nomgle

                  Zishy, you said earlier in the thread you're using Pro 1000 PT cards.

                   

                  The Windows 10 drivers - here -> https://downloadcenter.intel.com/download/25016/Network-Adapter-Driver-for-Windows-10 - only support the models below. When Windows 10 first released, I also had some old Pro 1000 PT cards - but I replaced them with the I350 cards, because they aren't supported by Intel on Windows 10. I didn't even try Teaming on my 1000 PT cards...

                   

                  The only adaptors supported on the Windows 10 driver download page are :

                  • 21. Re: I211/I217-V Windows 10 LACP teaming fails
                    Zishy

                    since you arent an official intel employee and you arent adding any usefull information to the thread i would ask you to not post here just for the sake of posting.

                     

                    we KNOW that not all adapters are supported yet. the driver download page of the PT adapters lists a windows10 driver tab and therefor is missleading ppl about the support. the card itself supports operation in the windows 10 enviroment and its safe for customers to asume that windows 10 would support teaming, if win7/win8.1 supported it without any flaws. if intel decides to stop supporting the older server adapters that is unfortunate for alot of people, because they are perfectly good cards and i dont see a reason to sidegrade to i350s. there is no incentive whatsoever to upgrade a high quality server adapter if you dont go to at least a 10gbe. we are simply waiting for intel to give us some information about the reasons why drivers work for singleports but teaming doesnt currently work in windows 10.

                     

                    TLDR, please dont post, if you cant add anything beyond what the official intel employees allready told us earlier. we know its not supported right now and we are waiting for OS integration and/or intel driver workaround

                    • 22. Re: I211/I217-V Windows 10 LACP teaming fails
                      HHawk79

                      Sheesh Intel is also going downhill rapidly.

                       

                      Still no possibility to create a team with Intel PRO/1000 PT Dual Port Server Adapter. They don't even care about support.


                      And I was told nonsense a few months ago here:Question about teaming in Windows 10?
                      This was on my home machine.

                       

                      I use the Dual Port here for work, but without teaming, I think it's time to move on to a more reliable brand for our networking needs.

                      • 23. Re: I211/I217-V Windows 10 LACP teaming fails
                        Carl_Wilson

                        Nomgle is correct.  The only driver packages that are certified for use on Windows 10 are the ones outlined in the post above (for teaming, once the OS is patched to support it).

                         

                        And this makes sense.  The Ethernet Controller on the Intel(r) PRO/1000 PT Dual Port Server Adapter card you are using is built using the Intel(r) 82571EB Gigabit Ethernet Controller (Intel® 82571EB Gigabit Ethernet Controller Specifications), which launched in summer of 2005 and has already announced EOL.  The last Microsoft certified driver for that card was for Windows 7/Windows Server 2008 R2.  After those OS releases, Microsoft no longer provides WHQL driver certification for Intel's publically released drivers for any new operating systems (due to a lack of features required for WHQL certification).  This means that the driver moves from an Intel supported/released driver (from the Intel web site) to what is known as 'inbox driver' - meaning the driver is included native "in the box" of the Operating System (with the driver support goes through the OS vendors at this stage).

                         

                        Since Windows 8.1/Windows Server 2012 and beyond - the driver for any products based on the 82571EB are only inbox.  Unfortunately, MS does not have native LBFO support for their client OSes, therefore Teaming on any 'inbox only' driver is not possible.  For Windows 8/Windows Server 2012, Intel did release a driver on our public download site for those customers requiring teaming, however these drivers were not WHQL certified.  For Windows 10, the silicon was just too old to take this extra step.

                         

                        Due to the age of the controller (10+ years old now), and the lack of silicon features required to receive WHQL certification - Intel's driver support team can no longer even work on new OS support for this silicon (or the card).  My recommendation is use a card or controller that is on the Windows 10 support list to take advantage of the features you are looking for.  We do support teaming in Windows 10 Client with the silicon listed in Nomgle's post.


                        * Disclaimer.  I am an Intel employee, and own the silicon that is on the Intel(r) PRO/1000 PT Dual Port Server Adapter.  In fact, I owned it before it launched. 

                        • 24. Re: I211/I217-V Windows 10 LACP teaming fails
                          Nomgle

                          Thanks for the update Carl.

                           

                          I updated a few of my machines to the latest build of Windows 10 today - Version 1522 Build 10586.3 ... and it broke my working Team.

                           

                          For some reason the "Upgrade" process replaced some of my drivers with the Microsoft Inbox versions ! Once I'd got my Intel RST and Intel ProSet and Creative Audio drivers installed again, I got the teaming options back in Device Manager.

                          But after creating a Team, it only shows in Device Manager - it does not show in Network and Sharing Centre (ie, Windows 10 doesn't even recognise it as a network device). So no Teams at all now.

                           

                          I'll also point out that Windows 10 replacing my Network drivers left me with ZERO connectivity until I reinstalled ProSet - so if you're doing this on a Remote machine, you'll be screwed after the upgrade completes.

                          • 25. Re: I211/I217-V Windows 10 LACP teaming fails
                            mimi74

                            Got Windows 10 64b 1511 10586.3

                            Today, I've tried to install a teaming on my Intel(R) Gigabit ET Dual Port Server Adapter, I haven't the option to active the teaming

                            Then tried another network card Intel(R) Ethernet Server Adapter I350-T2 (suposed to work), I have the option button, but always greyed out, can't active

                            It was working fine with Win7, Win8, Win8.1

                            I'm very desapointed by the Intel drivers

                            • 26. Re: I211/I217-V Windows 10 LACP teaming fails
                              VirtualPanther

                              Oh, man... I was hoping it was some odd bug on my machine. Prior to this latest "November Threshold" Win 10 update, my Ethernet Server Adapter I350-T4 was working great. I used LACP to my switch with four Cat-6 cables and was loving life. Now I have four separate NIC channels, my surveillance software is confused by my machine having four different IPs and nothing works...

                              • 27. Re: I211/I217-V Windows 10 LACP teaming fails
                                Carl_Wilson

                                Nomgle , When you upgrade to a new Operating System such as Windows 10, your drivers will up 'updated' by the OS install to what the OS has certified as current (in other words, what it will support).  Unfortunately, this means that the hardware you were using before becomes subject to the OS WHQL certifications required for that version of the OS.  Thus, the loss of teaming.  (This again is due to the fact that inherently, the OS does not support Teaming, and the controller silicon on the adapter you used before does not have WHQL certifications for that OS.)  IN this instance, a PROSet reinstall still will not allow for teaming to setup (it requires a device to initial the team that the OS will support as WHQL certified).  To support teaming using Intel hardware under Windows 10, you will need a device that has a certified driver for Windows 10 (see my post above for why).


                                mimi74, you are in the same boat with the Intel(r) Gigabit ET Dual Port Server Adapter, which is based on the 82576EB controller which launched in Q2'08.  Like the 82571EB controller, it also does not have Windows 10 driver from Intel (only Inbox from Windows 10).  The last 'Retail' driver available for that controller is Windows 8 and Server 2012.  Windows 8.1 and Windows 2012 R2 and beyond are inbox only support.  The Intel(r) Ethernet Server Adapter I350-T2 should work with Teaming etc., assuming you have the most current driver.

                                 

                                VirtualPanther and mimi74, you should also be able to download our latest driver from the Intel support site for Windows 10 for the I350-based cards.  This also should allow you to create a team from the Windows device manager (there is no longer a separate PROSet application as it is integrated into Device Manager).  Once you create a team you will be able to have the 1 IP address you need for your application and switch.  My guess is when you upgraded the Inbox Driver that is native to the OS removed your teaming settings.  Installing the Windows 10 driver from our web site should allow you to reconfigure the team you need.

                                • 28. Re: I211/I217-V Windows 10 LACP teaming fails
                                  VirtualPanther

                                  So... The only download I have for the I350-T4 card for Win 10 x64 is here: Download Network Adapter Driver for Windows® 10

                                  I downloaded it, right after installing the dreaded Win 10 v1511 threshold update. It is PROWinx64.exe and it installs in a similar fashion as before, but teaming is disabled, with pretty much the same note as on the download page: doesn't work on Win 10. I do not see a way to create a team to test if it will function and my previously created and working teaming for this card on Win 10 was destroyed by the threshold update. I do not see any other driver available anywhere else. I am more than willing to try something, if you know where I can get it. In response to my support ticket with Intel Networking, the answer was to blame Windows 10, with a suggestion to contact Microsoft

                                  • 29. Re: I211/I217-V Windows 10 LACP teaming fails
                                    mimi74

                                    Then I've tried another network card Intel(R) Ethernet Server Adapter I350-T2 (suposed to work), I have the teaming option button, but always greyed out, can't active

                                    It was working fine with Win7, Win8, Win8.1 !


                                    Perhaps I've forget to explain with the last drivers 20.4.1

                                    1 2 3 4 Previous Next