|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
Can anyone point me to a thread concerning an issue with the Intel Pro 1000
Dual Lan Modules not coming up after a reboot? Surely others have this same issue. Its incredibly consistent. If I reboot any of my box's with the Intel Lan Chipset on a high broadcast segment of the LAN, the card doesn't seem to work until I disable and enable the adapter. Then its fine until the next boot. I am on a Windows 2003 Server, and for sure this issue became more prevalent with the application of R2. It went from happening 1 in 5 boots, to 9 out of 10 boots. It seems like this is an Intel driver problem to me, as the card itself is fine internally. By that I mean it shows up from an IP config and responds to pings on the loopback. It just can't get out of the box. Maybe it failed to negotiate the speed or detect the link or something in time? Short of fixing this, does anyone know of a way to delay the startup of the driver? Seems like if I could delay the start of the driver a few seconds after boot up until the OS calmed down, it would work as well. I say this because if I start the OS with the driver disabled, then enable it once the OS has started, it seems to work fine also. Thanks to anyone who has a few moments to respond. authorwjf |
![]() |
| Tags |
| 1000, intel, kickstart, pro, reboot |
| Thread Tools | |
| Display Modes | |
|
|