1 29 30 31 32 33 Previous Next 604 Replies Latest reply on Nov 22, 2017 5:39 AM by johnkristian Go to original post
      • 450. Re: I211/I217-V Windows 10 LACP teaming fails
        jdijulio

        This comment (#188, not sure why this post from today somehow got ordered way back there):

         

        "The solution is clearly not in Intel's hands and Carl is probably as upset as all of us. Teaming and advanced network features has been removed by Microsoft's policy and they're now restricting third-parties to add them back. We should really start a new thread on Microsoft's support forum and hope for a rollback..."

         

        is false.

         

        Microsoft didn't remove anything. Client SKUs have never supported native LBFO. Only server SKUs have supported it. UI bugs gave the appearance it was working, but technically speaking it never was. Microsoft has since fixed that. Please review this post if you want to learn more:

         

        Re: I211/I217-V Windows 10 LACP teaming fails

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

          OK, lets clear a few things up.  Lets start with Windows Release Basics.

           

          Windows 10 Version 1507 (build 10.0.10240), codenamed "Threshold 1"

          Windows 10 Version 1511 (build 10.0.10586), codenamed "Threshold 2"

          Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393), codenamed "Redstone 1"

          Windows 10 Creators Update[202] or Windows 10 Version 1703, codenamed "Redstone 2"

           

          1) MS Windows 10 Redstone 1 is where the fix was rolled out by Microsoft was for Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393).  Versions prior to 1607 do not have the hot-fix available.  Versions after 1511 are "Redstone 2" which is in Beta has not been released yet.

          2) Beta releases of operating systems are not tested and validated on posted drivers on the web.  If you install the v22.0.1 driver package on releases after Windows 10, version 1607 you will need to escalate any bugs directly to Microsoft.

          3) All the issues I see above on these threads are related to a Beta version of Windows 10.  propergol , deecol

          4) Famaku , you are on Windows 10 version 10240 ("Threshold 1").  MS did not port the Hot Fix for that OS to TH1.  Please upgrade to RS1

          5) I don't know about this one MassimoS..  You might want to make sure that your system has all available updates from MS.  If that doesn't fix the issue, then the Intel support team will need to look into it. 

           

          That's the best I can do.  My recommendation is to move the request to a new thread for those systems that are RS1 that have all the correct patches installed (please verify they were successful).  That way, it can be addressed as a new issue (which it will be) vs. the OS limitation that this string is about.

          5 of 5 people found this helpful
          • 452. Re: I211/I217-V Windows 10 LACP teaming fails
            jdijulio

            Thanks Carl_Wilson!

             

            Can you clear up my question about the download links. Should we expect it to be available here:

             

            Download Intel® Network Adapter Driver for Windows® 10

             

            Just seemed to me a download link labeled under "Intel® Network Adapter Driver for Windows® 10" would have the latest and greatest available. Maybe it will just take a few days for all the cross-linking to happen on the back end?

             

            Also, to any users that start a new thread regarding an issue specifically impacting Windows 10 RS1, maybe post a quick link to any new posts here (for those of us watching this thread, in case they need help moving to a new discussion that may be relevant to them)?

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

              Look under OS Independent.   They put all the OSes into 1 download.  I flagged this to the driver team.

              • 454. Re: I211/I217-V Windows 10 LACP teaming fails
                deecol

                So then I have to assume that teaming isn't working on any win10 version 1607 above build 14393. Which would be any Preview release slow or fast ring.

                Please post here anyone that has teaming working on a Preview release and which build you are on.

                • 455. Re: I211/I217-V Windows 10 LACP teaming fails
                  propergol

                  @Carl_Wilson : so MS Windows 10 Redstone 1 is the only Windows version that supports teaming?

                  This version is 6 month old! And why would Microsoft have then released in fast or slow ring versions of Windows WITHOUT this mysterious "patch" allowing your drivers to work? Knowing that Intel was in contact with Microsoft regarding this teaming issue...

                   

                  An other thing I don't catch : so Windows 10 was ready to support Intel's teaming 6 month ago already??? I though that was the opposite : Intel's drivers were waiting for Microsoft to update Windows 10 to supports teaming...

                  • 456. Re: I211/I217-V Windows 10 LACP teaming fails
                    MassimoS

                    @Carl_Wilson,

                    I'm on release system, no beta, fully updated.

                    How can I involve the intel support in the correct way?

                     

                    I have one not on your points:

                    Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393), codenamed "Redstone 1"

                     

                    is NOT beta.

                    "

                    Version 1607 (Anniversary Update)

                    Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393), codenamed "Redstone 1", is the second major update to Windows 10 and the first of the 4 major updates planned under the Redstone codenames. It carries the build number 10.0.14393 and version 1607. The first preview was released on December 16, 2015. It was released to the public on August 2, 2016. The Redstone 1 release of Windows 10 is supported for users of the Current Branch (CB) and Current Branch for Business (CBB).

                    "

                    It has been released to public via windows update (no Beta updates) and is the supported version.

                     

                    Hoping this helps.

                     

                    The beta is Redstone 2

                    • 457. Re: I211/I217-V Windows 10 LACP teaming fails
                      desty

                      Thanks Carl_Wilson!

                      Half a year ago I bought a Tp-Link switch with Link Aggregation and Intel PRO/1000 PT Ethernet adapter.

                      I wanted to boost my local network speed but I saw that is impossible because I installed Windows 10 1607 update. I was looking for information about my problem but have not found anything. Then I found that forum. I would to thank you for your work. I force installed latest update v22.0.1 for my adapter and now I can create TEAMs and VLANs. I am very happy, that now i can continue my project! In future I will buy two next adapters for server and for second PC. Thanks!

                      P.S.

                      Sorry for my English i am only fifteen year old student from Poland.

                       

                      1 of 1 people found this helpful
                      • 458. Re: I211/I217-V Windows 10 LACP teaming fails
                        welcomesorrow

                        From discussions of this thread, I got an impression that the OS side was more to be blamed for the issue of teaming under Windows 10. If so, will the Dec. patch from Microsoft enable teaming using NICs from other vendors?

                        • 459. Re: I211/I217-V Windows 10 LACP teaming fails
                          chrullrich

                          welcomesorrow wrote:

                           

                          From discussions of this thread, I got an impression that the OS side was more to be blamed for the issue of teaming under Windows 10. If so, will the Dec. patch from Microsoft enable teaming using NICs from other vendors?

                          Hardware vendors were always able to provide teaming/VLAN on Windows 10, all through this whole affair. However, at least in Intel's case, installing the teaming driver would render about one in ten systems unusable (and unrecoverable short of reinstallation!). They had to wait until Microsoft fixed that bug before they could release drivers that touched this part of the system.

                           

                          Intel unfortunately never went into details about what the issue was, but I can understand that.

                           

                          Other vendors may well have had the same reason not to release updated drivers. After all, their teaming solutions for client OS versions are, and always have been, independent of the OS support (or lack of it). If that is true, there may well be updates forthcoming from those others as well.

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

                            The issue was related to the proper setup/teardown of the mini-port driver.  Its a core OS function that all networking vendors use to setup these types of functions.

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

                              Yes.  Its built into the OS.

                              • 462. Re: I211/I217-V Windows 10 LACP teaming fails
                                John.Maduro

                                Oh I'd love to hear your guide how you "forced" to install it. I have no clue!

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

                                  desty The Intel(r) PRO/1000 PT is based on the 82572EI Gigabit Ethernet Controller.  The last OS that is supported with our 'Retails Drivers' (downloaded from the Intel download center) is Windows 7.

                                   

                                  Driver Support Matrices: Microsoft® Windows® Native and Retail (again, there is an error in the matrix where the 82583V shows a retail driver for Windows 10.  It does not have one, only an inbox driver from the OS.)

                                  • 464. Re: I211/I217-V Windows 10 LACP teaming fails
                                    chrullrich

                                    John.Maduro wrote:

                                     

                                    Oh I'd love to hear your guide how you "forced" to install it. I have no clue!

                                    • Right-click the device in Device Manager, then select "Update Driver Software".
                                    • Click "Browse my computer for driver software".
                                    • Click "Let me pick from a list [...]".
                                    • Click "Have Disk ..."
                                    • Browse to the directory where you extracted the drivers; for Windows 10 x64, then go to PRO1000\Winx64\NDIS65 (for x86, it's Win32 in the middle).
                                    • Select any of the .inf files, it does not matter which, then click Open.
                                    • Uncheck "Show compatible hardware".
                                    • Pick whichever device you think is close enough to yours that it might work.
                                    • Click "Next".

                                     

                                    Good luck.

                                    1 of 1 people found this helpful
                                    1 29 30 31 32 33 Previous Next