thanks a million for your quick reply, but I have to admit that I am somewhat stumbled about Intel's bugfixing policy...
You state that the bug has been reported formally ok and is therefore known about by your company and your development engineers.
I think that the severity of this bug: basically slowing down GbE devices to 100MBit IMHO deserves the highest bug priority, so I am completely lacking understanding why this bug does not make it on the list of bugs to be fixed in the next release.
What makes you so sure that this issue only affects "old" devices? Can we somehow increase the pressure to have this taken seriously, assigned a higher priority and be fixed (e.g. by complaining with motherboard or computer manufacturers)?
Base line: What can we do that this regression bug gets the level of attention that it deserves and will finally be fixed in an upcoming "e1e" version?
Looking forward to your comments...
Thanks again & best regards,
I'm having this exact same problem as well. The PC is a HP DC7700 Convertible Minitower, the NIC is a "Intel(R) 82566DM Gigabit Network Connection" [sic] according to Windows. Intels automatic driver update utility detects it as "Intel(R) 82566 based Network Controller(OEM)".
During autonegotiation "PROSet" shows 1gbps for a few seconds then drop to 100mbit. If I force 1gbit I get no network connection.
Windows 7 64-bit Ultimate SP1, PROSet 126.96.36.199, driver 188.8.131.52.
The PC is connected to a Linksys E3000 router which also indicates a 100mbit link. Other devices in the network connect to the router at 1gbps without issues. I've used the exact same cables to connect another 1gbit devices as well.
Please let me know if there is anything I can provide to help resolving this issue!
sorry for being such a pain in the neck, but let me restate that in my opinion, this issue is critical and MUST definitely be fixed in recent versions of the driver.
Is there any way to escalate this issue? Can you please give us (the people participating in this thread) the contact information of your manager and/or the person in charge of deciding about which bugs to be fixed in future releases?
Thanks & best regards,
My college's desktop infrastructure strategy will depend heavily on what happens here. I would like to consider staying with the current strategy of using fat desktop client up to 5-6 years. The college is already influenced by the current trends of migrating to VDI or Ipads and Intel's ability to fix this currently issue will have a major impact on the decision making. Though I have nothing against alternative desktop infrastructures the real ROI doesn't come close to our traditional model for a business of our type and size.
Systems with these NIC's are entering their second life as we speak, buyers expect a system with a gigabit connection that simply works...
Tested with version PROSet 17.1 on both Windows Server 2003 SP2 and Windows XP x64 SP2 and found this issue to be present still...
Plus when using the 17.1 drivers at the auto negotiated 100Mbps Full Duplex I have the impression that the NIC is really slow in initiation, for example DHCP takes a dozen of seconds to obtain an address.
(When using static IP's there is no delay)
When using PROSet 13/14 I experience massive packet loss at gigabit speeds, only on these NIC's, other systems run fine at the same 1000Mbps speed, replacing cabling and switches doesn't make a difference.
I remember PROSet 13/14 running fine for many months at gigabit speeds but somehow that is not true anymore... do these NIC's electrically get worn out after time ?
I think I'm going to add a plug in adapter for now until some positive driver news appears...
RE: I remember PROSet 13/14 running fine for many months at gigabit speeds but somehow that is not true anymore... do these NIC's electrically get worn out after time ?
A physical failure is possible, but I suspect some change in the registry or OS update would be a more likely culprit.
No driver update news yet.
I am having same problem with 822566mm only auto negotiating at 100MB/s. I have followed the advice here and downed graded driver software and installed the 184.108.40.206 package (driver 220.127.116.11) but there was no difference - still 100MB/s. Does anyone have any ideas.
Have a Toshiba M9 running Windows 7 64-bit.