Wibble_
asked on
Second network card "cannot start" W2k3R2Adv iSCSI - works fine after dis/enable
I'm booting windows 2k3 R2 Advanced by iSCSI from one network card (SAN side).
Windows fails to bring up the second card (Access &Â domain side) claiming the device cannot start, however if I disable and then enable the hardware it works fine.
The hardware I am using is an IBM HS20 blade, with a broadcom5704 chipset dual port network card. The units don't have iSCSI boot initiators, so I'm chain booting gPXE from PXE to boot windows by iSCSI from a SAN LUN.
I could do this as a startup script, which would then allow domain logins, but wouldn't allow things like package deployment, or group policy which runs in the boot sequence before this. Perhaps I could do something with the devcon command at bootexecute?
I'm using the most recent driver for this chipset from the broadcom site.
I've tried all relevant BIOS permutations
Thanks for looking :-). Any relevant ideas are welcome...
Windows fails to bring up the second card (Access &Â domain side) claiming the device cannot start, however if I disable and then enable the hardware it works fine.
The hardware I am using is an IBM HS20 blade, with a broadcom5704 chipset dual port network card. The units don't have iSCSI boot initiators, so I'm chain booting gPXE from PXE to boot windows by iSCSI from a SAN LUN.
I could do this as a startup script, which would then allow domain logins, but wouldn't allow things like package deployment, or group policy which runs in the boot sequence before this. Perhaps I could do something with the devcon command at bootexecute?
I'm using the most recent driver for this chipset from the broadcom site.
I've tried all relevant BIOS permutations
Thanks for looking :-). Any relevant ideas are welcome...
windows boot sequence AFAIK:
bootexecute (windows internal)
preparing network connections
apply computer settings (group policy)
install managed software packages
running startup scripts
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Get the latest drivers from IBM not from Broadcom.
Regards.