Got a difficult large network issue, wireless on new ProCurve setup

So...symptom kept lingering, wiring guys came back, redid, verified. Still playing "whack a mole" here...occasional interrupts, we find a noisy port, kill it, network returns...

..started noticing more random ports. They'll be at 10 megs, noisy broadcast. We find relatively new PC, but in sleep mode. Wake it up, renegotiates at 1000.
...came on this post today..
https://supportforums.cisco.com/dis...17-lm-nic-causes-broadcast-storm-and-high-cpu

BOOM! There it is!

Ugh, what a stupid thing for so much hassle. Glad to hear you got it sorted out.
 
ugghhh - Of course I have 31 endpoints with this nic at one location. Haven't had any issues yet that I'm aware of but might as well make sure they are all updated!

Thanks for the heads up and glad you found the resolution!
 
Yeah...that link at Cisco points to other brands too...it's not just Lenovo, likely it will be many different brands and models of computers made in the past 2 years and moving forward..that have that Intel NIC. The article points to another thread with HP Elites that have it too.
And it doesn't talk about what driver version..so we don't know which old version to ensure is not being used.
 
I'm finding mostly in dell optiplex's. I just downloaded the new driver release 3 days ago. Existing drivers are dated 2014 and that article is from 2 years ago so I can only assume it won't be a bad thing to update.
 
I'm seeing some of these adapters on a lot of Lenovo systems too. Stonecat, you've come to the forum for help on your problem, solved it yourself anyways, found a problem that a bunch of us probably didn't know we had, told us how to solve that too. One stand up guy :D

Motorbiking time is almost here and I still owe you beersteakskis!
 
Any RMM tool should be able to run a procedure to identify the NIC hardware in the endpoint and if there is a match, call a link to the updated driver, download it and silently install it. How it ID's the hardware would be up to you but could be something as simple as a powershell command using get-wmiobject.
 
So, interestingly.... today I brought two new Lenovo Miny i5 systems down to a small client of mine. They use an older version of QuickBooks POS (version 10). So I got the systems with Windows 7 downgrade. The owner had mentioned before he would really like Windows 10 but wasn't sure if POS10 would run on it. So I thought, why not, I'll upgrade one of these Tiny's and see if she opens up. So I did, and the program fired right up without errors. OK, let's give it a shot!

Get both of the machines setup with LOB apps, install them over their lunch break... setup email, yada yada. Everything is great. They open up QB POS. Opens up right away. Click a button.... DERP. Sits there. Thinks. Thinks more. About 5 minutes later it responds. Yuck.

Roll back to Windows 7 thinking, stupid me, was worth a shot any ways. Open up QB POS, same ****. Now I'm thinking what in the royal F*#$%& is going on here? I'm deploying a grand total of 2 machines and wasting lots of time. OK, check device manager quick? Oh?? Intel i217! Of course it has that, I just upgraded the drivers on at least 5 machines the night before after reading this thread!!! I didn't even think to take note of the machine type.

Yep, new driver, fixed it. Upgraded to Windows 10 as I'm just super curious now... works fine. BLAAAH!!!
 
I updated drivers on 37 machines after StoneCat's findings. Wasn't having any issues with them (that I know of) but figured I'd take care of it now before it became a problem.
 
Man, my first few years I would ride any day there wasn't snow on the ground. Now I'm 29, and already old man-ing it. Pretty much nice weather only. I think its because my current bike is in really great condition, so I'm sort of afraid to get it wet. It's not an expensive bike either, I'm just a big wuss!

After this debacle I may just start using snappy driver installer on all new machines. I have another Lenovo Tiny that's going out to a new restaurant this morning, it's already in the box but I will be updating the driver first thing when I'm on site.
 
After this debacle I may just start using snappy driver installer on all new machines. I have another Lenovo Tiny that's going out to a new restaurant this morning, it's already in the box but I will be updating the driver first thing when I'm on site.


Lenovo's built in tools...they'll sniff 'n check online and pull down/install new ones.
 
Back
Top