Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

trhacker

3 Posts

3905

December 1st, 2007 05:00

Windows 2003 won't boot after enabling teaming

Hello everybody,
I'm facing the same problem on 3 freshly installed Dell Servers (2 PowerEdge 2950 and 1 PowerEdge 1950).
After enabling teaming on the two onboard nics (Broadcom Nextreme II Gbit Eth), the system fails to reboot (hangs at Windows logo) and only starts in Safe Mode (without networking).
 
I tried a restore procedure on PowerEdge 1950.
1) Booted in safe mode, and disabled bacs teaming interface from Hardware Management.
2) After that, I've been able to succesfully boot in normal mode, then I deleted the teaming from the BACS application.
3) Downloaded and installed the latest Broadcom drivers and application from Dell site (Bcom_LAN_105_35_W2K3_A03.exe) and rebooted.
4) Installed Microsoft HotFix 912222 (Scalable Networking Pack release) for TOE functionality (not sure if needed but did it anyway) and reboot.
5) Created a new teaming interface and tested (OK) then rebooted.
 
Now I'm experiencing the following behaviour: most of the times the server starts correctly (with teaming enabled and working), sometimes it keeps hanging at Windows Logo.
 
What to do resolve this issue?
Thanks in advance for any suggestion
Gabriele

trhacker

3 Posts

December 6th, 2007 04:00

Now the issue seems to be resolved. I followed this procedure: - restored the server disabling the virtual teaming driver and the Packer scheduling driver (seemed not able to load at boot time). - restored/repaired the old broadcom drivers through the installer - updated Broadcom drivers and applications to the latest release - disabled Packet Scheduler on both the phisycal nterfaces - created a new team with only one adapter bounded to it - after several reboots, added the second interfaces to the team. Now all 3 servers are functioning properly, made several reboots, plus tested Teaming for network loss and everything is working fine. In the end, I think it all relied on Packet Scheduler (maybe I shouldn't have disabled the packet scheduler driver when restoring the server, but only the teaming driver), however...all well what ends well :)

Was this post helpful?

View All

No Events found!

Top