4 Replies Latest reply on Nov 15, 2012 8:43 AM by Alex Beaudet

    82579LM - Windows 8 issue with ProSet and vlans with static addresses

    Alex Beaudet

      I am testing Windows 8 Enterprise 64 on an Intel DQ67SW motherboard.  It has an 82579LM network card which I've installed with the newer ProSet 17.4 for Windows 8 (64bit) (also tried 17.3 with same results).  Here is my problem : If I add a tagged VLAN and I set it with a static IPv4 address, the network card accepts it but keeps the "autoconfiguration IPv4 Address" (169.254.171.226) also and marks it has <prefered>. Hence the network card is useless and routes aren't being set properly.

       

       

      ipconfig /all  :

       

      Ethernet adapter Ethernet 2:

       

         Connection-specific DNS Suffix  . :

         Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection - VLAN : VLAN1000

         Physical Address. . . . . . . . . : 00-22-4D-6B-59-C5

         DHCP Enabled. . . . . . . . . . . : No

         Autoconfiguration Enabled . . . . : Yes

         Link-local IPv6 Address . . . . . : fe80::75e5:55c9:c10e:abe2%26(Preferred)

         IPv4 Address. . . . . . . . . . . : 10.0.10.5(Duplicate)

         Subnet Mask . . . . . . . . . . . : 255.255.0.0

        Autoconfiguration IPv4 Address. . : 169.254.171.226(Preferred)

         Subnet Mask . . . . . . . . . . . : 255.255.0.0

         Default Gateway . . . . . . . . . :

         DHCPv6 IAID . . . . . . . . . . . : 436216397

         DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-36-4E-E6-00-22-4D-6B-59-C5

       

         DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

                                             fec0:0:0:ffff::2%1

                                             fec0:0:0:ffff::3%1

         NetBIOS over Tcpip. . . . . . . . : Enabled

       

      Tunnel adapter Teredo Tunneling Pseudo-Interface:

       

         Media State . . . . . . . . . . . : Media disconnected

         Connection-specific DNS Suffix  . :

         Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

         Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

         DHCP Enabled. . . . . . . . . . . : No

         Autoconfiguration Enabled . . . . : Yes

       

      Tunnel adapter isatap.{CAAE7C0F-9462-45E9-9266-2E79108C7F24}:

       

         Media State . . . . . . . . . . . : Media disconnected

         Connection-specific DNS Suffix  . :

         Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3

         Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

         DHCP Enabled. . . . . . . . . . . : No

         Autoconfiguration Enabled . . . . : Yes

       

       

      any help? I've used ProSet drivers since forever on all past windows OS and that same problem never occured... so I guess it's a case of immature drivers?