Hp Nc373i Driver Windows 2003 Download WORK
Bartolome Moosavi
We are having some intermittent network issue with this server 2008 R2. I have checked all the possible issues and rectified it. Now the only thing I can think of is updating the network adapter driver.
What roles are on the server?
What does DNS point to?
Did you do an actual upgrade of the 2003 to 2008r2? If so, are you sure you're at 2008r2 and not 2008 32bit as you can't in place upgrade a 32 bit os to a 64 bit one.
For the VPN users, do they connect through IP or DNS name?
If they connect through DNS name, can they still connect through IP?
SPP is only for servers with active support and I don't think they ever put gen5 drivers in there.
Over this weekend I did a p2v of an HP BL460c (g1) server running Windows 2003 64bit. The physical box has the HP insight and management agents and according software. After the P2V it still had the NC373i multifunction drivers hidden. I ran the devmgt hidden =1 command but they did now show up hidden in the device manager. I then downloaded the devcon tool and they are there displayed when i run the list all command. When i run the command to have devcon remove them it says failed. I do not want these drivers on there and these drivers retain my old ip address info on there, so when i change the virtual nic address, it says they are still being used by another device driver. Ideally i want to remove these as i want to make sure that this won't cause an issue down the road.
I didn't put that VM into production as there was other hp software on there and i ran out of time, i had to get the physcial box back into production. This coming weekend i'm planning on putting a new p2v vm into production of this server. I was going to remove the drivers ahead of time before the conversion but if i remove the NIC drivers how can i get the vm to my esx hosts? the simpliest solution would be to just remove the drivers after the p2v.
Yes, I have already ran that command and selected "View hiddent devices" and it does not list these drivers or adapters in the device manager. It displays them when i use the devcon tool but it fails to remove them. Thanks though!
I can't really come up with a common thread to figure out which driver/firmware update would have caused this problem. I've tried rolling back or re-updating the drivers for some of the devices (i.e. HP NC373i) and it made no difference. I'll attach a grainy screenshot of a smattering of the components exhibiting the issues and would love to hear some of your suggestions for chasing this down.
UPDATE 2: Although the issue I found (linked in the first UPDATE) was caused by something similar, this did not end up being my exact issue. All of the components listed in Device Manager with the yellow caution sign display the message "Windows cannot initialize the device driver for this hardware (Code 37)". No amount of uninstalling/reinstalling of drivers makes a bit of difference. I beginning to think that this hardware is literally trashed from these firmware updates. I'm quite desperate at this point, so feel free to throw any ideas my way.
UPDATE 3: This server appears to be trashed. I did a full motherboard swap figuring that I had a bad firmware flash or something and I see the exact same components exhibiting issues with the new board. I force applied the latest HP SPP drivers and there was no change. If no one else has any ideas, I guess I'm out of luck.
I'd recommend using the HP Service Pack for ProLiant DVD (and the Smart Update Manager) to install system drivers, or just cherry-pick and download components directly from the support site for your OS...
Otherwise, the firmware probably trashed the drivers on the server. You can attempt to uninstall/reinstall using the server DVD media (use the "Have Disk..." option) or do a repair install which will reset everything.
EDIT - May 2014 ... many years later. Microsoft have recently released a KB article Windows stops responding if SMB v1 protocol is used to access shared files that is targeted at Server 2008, which documents that the problem can occur "occurs because of a deadlock in the Mrxsmb10.sys driver.", and a hotfix is provided. The problem hasn't re-materialized here, so I won't be applying - however the detail sounds like the experience I've had above. I'm including it in the answer should it be useful for anyone else.
The specifications define how to build Windows-compatible devices, systems, and filter drivers across all Windows Platforms. They were developed in collaboration with partners, and focus on ensuring compatibility, interoperability, security, and reliability.
Something else: I have a problem with DISM. Whenever I mount a wim, inject drivers or do something else, I cannot dismount the image unless I restart my PC. Can it be Antivirus or something else? I believe I had the problem only asking for injected drivers.
THANKS! We have an HP c7000 chassis with HP BL460C G7 blades using the HP NC553i FlexFabric network adapters. I was able to use drvload to install the be2nd62.inf driver for Windows 2008 R2 (Same kernel used for WinPE) and the network started working in MDT. After finding the right drive I added it the the driver section of the MDT share and now it works automatically.
The following is a recent article which at the bottom includes an option to try to use the cciss driver. Although for RHEL, looks to me it might also work on other distros including openSUSE.
Unsupported, but if it works, why not?
FreeBSD will take advantage of Physical Address Extensions (PAE)support on CPUs that support this feature. The default kernelsupports memory up to 24 gigabytes, but device drivers will usebounce buffers to access I/O buffers in memory above 4 gigabytes. Acustom kernel with the PAE feature enabled will avoidthe use of bounce buffers, but disables a few incompatible devicedrivers. This feature places constraints on other features ofFreeBSD which may be used; consult the pae(4) manual page for more details.
Where possible, the drivers applicable to each device or classof devices is listed. If the driver in question has a manual pagein the FreeBSD base distribution (most should), it is referencedhere. Information on specific models of supported devices,controllers, etc. can be found in the manual pages.
Note:
The device lists in this document are being generated automaticallyfrom FreeBSD manual pages. This means that some devices, which aresupported by multiple drivers, may appear multiple times.
This driver also supports target mode for Fibre Channel cards.This support may be enabled by setting the desired role of the corevia the LSI Logic firmware utility that establishes what roles thecard can take on - no separate compilation is required.
With all supported SCSI controllers, full support is providedfor SCSI-I, SCSI-II, and SCSI-III peripherals, including harddisks, optical disks, tape drives (including DAT, 8mm Exabyte,Mammoth, and DLT), medium changers, processor target devices andCD-ROM drives. WORM devices that support CD-ROM commands aresupported for read-only access by the CD-ROM drivers (such ascd(4) ). WORM/CD-R/CD-RW writing support is provided bycdrecord(1) , which is a part of the sysutils/cdrtools port inthe Ports Collection.
Most adapters in the Intel Ethernet 700 Series withSFP+/SFP28/QSFP+ cages have firmware that requires that Intelqualified modules are used; these qualified modules are listedbelow. This qualification check cannot be disabled by thedriver.
The sis(4) driver supports Silicon Integrated Systems SiS 900 andSiS 7016 based Fast Ethernet adapters and embedded controllers, aswell as Fast Ethernet adapters based on the National SemiconductorDP83815 (MacPhyter) and DP83816 chips. Supported adaptersinclude:
[amd64, i386] Lucent Technologies WaveLAN/IEEE 802.11b wirelessnetwork adapters and workalikes using the Lucent Hermes, IntersilPRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and SymbolSpectrum24 chipsets (wi(4)driver)
The snd_hda(4) driver supports more than two hundred differentcontrollers and CODECs. There is no sense to list all of them here,as in most cases specific CODEC configuration and wiring are moreimportant then type of the CODEC itself.
If the driver listed is not the right version or operating system, search our driver archive for the correct version. Enter HP ProLiant DL180 G6 into the search box above and then submit. In the results, choose the best match for your PC and operating system.
Once you have downloaded your new driver, you'll need to install it. In Windows, use a built-in utility called Device Manager, which allows you to see all of the devices recognized by your system, and the drivers associated with them.
The DriverIdentifier is a tool that analyzes the system drivers on your computer. The utility reports if any new drivers are available, and provides the download files for the driver updates so you can install them quickly and easily.
dd2b598166