1 of 1 people found this helpful
Hmm - run NICINFO.EXE on one of those machines. My guess is that the resulting text-file will be markedly devoid of useful information (it's what we'd use to identify the NIC and then associate this to a driver.
You can find NICINFO.EXE here:
Just copy it to your client, and run it - it'll create a file called DOSNIC.INI
For instance, in my case, it spews out:
Now - from what I remember, NVIDIA's NIC aren't "normal" NIC's for some obscure reason -- meaning that our detection tool can't/doesn't detect them, which is down to whatever NVIDIA has done to them. If NICINFO.EXE can't detect them (i.e. their OEM codes) you're pretty much stuck (short of contacting HP/NVIDIA and getting them to fix the Firmware or whatever it is they need to do).
And without the PCI-identifiers, we've got no driver to match...
LANDesk EMEA Technical Lead
Sorry I should have also stated that I had run NICINFO and no results came back.
I even tried the manual method of specifying the drivers to the Vendor/Dev ID, but my guess is that would still only work if NICINFO could at least pull the info out.
Yeah - you're pretty much up the creek without a paddle then.
This is something that's caused most of us involved with OSD considerable amounts of facedesk'ing here. We've no idea what NVIDIA is doing to their NIC's to obscure this data away (let alone why) - but they're the only ones who can fix it. They're hiding (I guess) the OEM-information for their NIC's in some majorly non-standard place ... and until they fix that, we won't be able to detect them :(.
I believe we're trying to get ahold of an NVIDIA-NIC based system to see if we can work around this somehow, but this is somewhat a hazy memory on my side (so regard it little more as speculation at best). Doubt we've found 'til now where on earth that data's hiding (let alone why it isn't where all the other vendors put it...) on NVIDIA-based NIC's.
LANDesk EMEA Technical Lead.
Maybe we will have to convince our customer to purchase them with the Broadcom or Intel NIC then.... Thanks for the quick response.
From personal experience - I've had the least problems with 3COM and Intel NIC's - so I tend to favour them myself.
This is purely subjective (based on personal experience as it is), so take it with a pinch of salt as YMMV (Your Mileage May Vary :).
LANDesk EMEA Technical lead
What's happen if you try Defcon or check it with WMI script?
devcon.exe find * | find "NVID"
I found another tool here: http://www.nu2.nu/download.php?sFile=pciscan110.zip
Nachricht geändert durch ahe
I now have the same problem using Toshiba's M10. THe NIC is an Intel 82567LM Gig Network adaptor.