CHR1S Posted December 14, 2010 Posted December 14, 2010 I have an Intel 82564 (Intel Pro/1000 EB) network card in my server that recently updated its drivers from MS and got the self disabling bug. So I have now updated to the latest version from the Intel website (9.13.41.0) and it no longer disables itself but is stuck at 100Mb instead of 1Gb! Anyone know what I can do please?
CHR1S Posted December 14, 2010 Author Posted December 14, 2010 The plot thickens - Intel® PRO/1000 EB Network Connection with I/... Smart Speed has downgraded the link speed from the maximum advertised.
CHR1S Posted January 13, 2011 Author Posted January 13, 2011 can you not force it to 1gb I have no idea how you do this as there are no options for it in the driver.
oxide54 Posted January 13, 2011 Posted January 13, 2011 Switches are managed by the LEA your running 32bit windows 2003 ? can you tell me the pnp device ID?
CHR1S Posted January 13, 2011 Author Posted January 13, 2011 Yes Server 2003 R2 32bit PCI\VEN_8086&DEV_1096&SUBSYS_34848086&REV_01\6&748A419&0&01100010
oxide54 Posted January 13, 2011 Posted January 13, 2011 try this one, I pulled it of our SCCM/MDT/WDS driver collection, it should support that device ID and works okay for us. YMMV http://www.oriel.w-sussex.sch.uk/temp/intel.zip 1
CHR1S Posted January 13, 2011 Author Posted January 13, 2011 Thanks Oxide, I will give it a go after the kids have gone home. I have also logged a call with the LEA about the possibility of them forcing the port for me.
CHR1S Posted January 13, 2011 Author Posted January 13, 2011 Yay I have fixed it! Firstly a big DUUUUURRRR to me, as the Intel configuration bits of the driver only work when your actually at the server (and for very good reason too) and I was connecting remotely. And the problem? A damaged patch cable, swapped it to a new one and Bobs your mothers brother!
oxide54 Posted January 13, 2011 Posted January 13, 2011 Yay I have fixed it! Firstly a big DUUUUURRRR to me, as the Intel configuration bits of the driver only work when your actually at the server (and for very good reason too) and I was connecting remotely. And the problem? A damaged patch cable, swapped it to a new one and Bobs your mothers brother! sounds about right,! its easy to miss the simple things sometimes, especially with thousands of screaming kids and teacher which aren't much better! glad its sorted 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now