1 17 18 19 20 21 Previous Next 590 Replies Latest reply on Jun 19, 2017 2:37 AM by johnkristian Go to original post
      • 270. Re: I211/I217-V Windows 10 LACP teaming fails
        jdijulio

        Holy Cats!

         

        Latest Update on the Microsoft thread (NIC Teaming failed (Build 10568) Windows 10):

         

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

         

        I can go into some detail, however not much due to confidentially.

        I can confirm we we are working closely with Intel in regards to issues they have encountered with their ANS software that enables VLAN tagging and NIC teaming. My understanding after discussion with the product group last week is that all the outstanding issues that had been filed with us have been resolved at this time and we are waiting to hear back further regarding testing/validation to ensure no other bugs are blocking Intel regarding their ANS solution.

         

        I hope this helps.

         


        Adam Rudell | Windows Networking Beta | Microsoft Corporation

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

         

        Perhaps now that Microsoft has finally buttoned up all the tickets Intel has opened with them, and the ball finally appears to be back in Intel's court, the end of our long national nightmare drawing to a close...? At least we can hope, I suppose.


        Given the word from Microsoft, now would be a fantastic time for an update from our buddy,

        Carl_Wilson,

         

        PS: Maybe even 'ol RocketTech, given the last few posts (Re: I211/I217-V Windows 10 LACP teaming fails  and Re: I211/I217-V Windows 10 LACP teaming fails ) highlighting Microsoft's "right-from-the-horses-mouth" position on native LBFO on Windows Client SKUs - coupled with the latest note from Microsoft that they, as of last week, have finally been able to close out all open tickets that Intel had opened with them - can now finally be satisfied that this isn't all Intel's doing. And that, just maybe, Microsoft has had some culpability in the delays here. Fancy that.

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

          Thanks for tagging me on the thread so it proactively pinged me.  I admit I haven't looked in a few days.

           

          Let me check with the team and get back with you.

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

            Is that a dim light I see at the end of the tunnel?

            • 273. Re: I211/I217-V Windows 10 LACP teaming fails
              jdijulio

              Thanks Carl_Wilson,

               

              Sounds like Microsoft is willing to play ball with you guys on this, so hoping this can get banged out in short order!

               

              Joey

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

                The good news.  I've checked with the Windows driver development team here.  The comment from Adam (MS Networking Beta) is accurate.  I can confirm that our testing with the latest RS2 Beta shows no blocking issues with Teaming and VLAN setup/tear-down with our existing driver (internally enabled for testing of the features).  Therefore, once RS2 is released it can be re-enabled for that Windows release.

                 

                The not as good news, it doesn't help with the existing releases.  We are working with MS to determine if there is something they can do to help re-enable the capability in the current shipping releases.  If there is a patch to the OS that applies the RS2 changes to the previous releases, we can do a very fast point release since only the driver needs to code changes (only turning the capability back on).

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

                  Carl_Wilson,

                   

                  Hmmm... Everything I'm seeing indicates Redstone 2 isn't coming out until aroudn the same time of new Surface Pro hardware comes out (Spring 2017 at earliest).

                   

                  It also seems a little squirrely to have a drive that works on a specific "build" of Windows 10 verses just plain old "Windows 10". Would the driver check to make sure that the user had a certain patch level, and dynamically allow (or disallow) creation of VLAN/Teams at runtime?

                   

                  Definitely let us know what you hear back on backporting those patches to current Windows Builds. I'm going to ask about this on the Microsoft forum as well.

                   

                  Thanks Carl!

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

                    Carl_Wilson,

                     

                    Redstone 2 is already out as the insider build 14915. I have it running on one test system. How about releasing the drivers for us testers running Redstone 2.

                    I will report my findings on this forum with wireshark endpoint tests.

                    PM me if you have to.

                    • 277. Re: I211/I217-V Windows 10 LACP teaming fails
                      jdijulio

                      You know Carl_Wilson, thinking through this a bit further now... If the driver could simply do a Windows version check at installation (or, at runtime) and dynamically enable or disable based on the patch level... You could essentially do your point release now, with a high degree of confidence that it will be disabled for who it needs to be disabled for, and enabled for who it needs to be enabled for... Right?

                       

                      Then if down the road MS backports the fix via a KB patch, you could simply do the same thing (another point release) to have it verify that patch is installed before allowing the feature to be visible.
                      gets you guys COMPLETELY out of the position to be a roadblock. You're driver works, right now. All you are waiting on is RS2 to be released, at which point the driver automatically works as expected with no further work for you guys to do.

                       

                       

                      Eh, eh, eh...?

                       

                       

                      • 278. Re: I211/I217-V Windows 10 LACP teaming fails
                        Ryme

                        Eagerly awaiting a fix on this issue which I just discovered after a motherboard upgrade. Following

                        • 279. Re: I211/I217-V Windows 10 LACP teaming fails
                          Memories4Life

                          I been watching this thread since it started a yr back reading between the lines here.... Intel have 10GB Nic's coming to the market and M$ breaks teaming over a year ago do you really think these guys (Intel & M$) are going to fix this ahead of forth coming profits? I been waiting for OVER a year now so you may as well wait for Jesus to fall from the sky. Dont see this happening anytime soon if at all.

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

                            like the biblical reference. lol.

                            The release of the 10Gb hardware should not be a deterrence since that will take a while to propagate. Bringing back teaming will just be a gateway to the next generation of NIC's. 10Gb Ethernet adapters and fiber has been around for a while and prices have come way down. The real issue with 10Gb for me is the availability and prices of switches and routers. Intel does not make those. I do think there is some pushback from MS. That is obvious since nothing is done with the solution in hand. There is way more going on behind the scene than we know on this issue or it would have been done already.

                            • 281. Re: I211/I217-V Windows 10 LACP teaming fails
                              johnkristian

                              Answer on the MSFT thread:

                              Working with the PG as well from my end to see if we can get the fixes ported to the previous builds. I will keep you posted on any updates.


                              Adam Rudell | Windows Networking Beta | Microsoft Corporation

                               

                              This might look promising!

                              • 282. Re: I211/I217-V Windows 10 LACP teaming fails
                                CS_5

                                Looking forward to a possible resolution, was shocked and disappointed that nic teaming was not supported after my recent build. Following the issue.

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

                                  LFBO still not enabled in preview edition 14936, not that I expected it would be. But at least MS fixed the network sharing/discovery issue.

                                  So its been a few weeks since any news from Intel. Where's the beef?

                                  • 284. Re: I211/I217-V Windows 10 LACP teaming fails
                                    VinnieI

                                    I finally gave up and bought a 1u server with quad nics. Server 2012 R2 - No problem teaming....

                                     

                                    This is disgusting. Cutting out a long-running feature to sway people towards enterprise equipment and licensing. Not even saying anything about it in the open is what really aggravates me.

                                    1 17 18 19 20 21 Previous Next