Server Shutsdown Unexpectedly Right After NIC Error
Almost every day around 5AM (give or take a few minutes) my server gets the following error twic at the same time on one of its NIC's:
EVENT ID 4: "Broadcom BCM5708C: The network link is down. Check to make sure the network cable is properly connected."
Aftr this error the server seems to shutdown unexpectedly and reboot. 30 second after the NIC error I get:
EVENT ID 1101: "Audit events have been dropped by the transport. The real time backup file was corrup de to improper shutdown.
I am not sure when the server physically shutsdown.
This is on a SBS 2008 server that is attached to an ISA 2006 server for its outside access. This happens almost every day at 5AM for the past few weeks.
Also the NIC in question is the secondary NIC that is being used for Hyper-V external netwok. The main NIC for this server that has the static IP address is an Intel NIC and has no errors.
EVENT ID 4: "Broadcom BCM5708C: The network link is down. Check to make sure the network cable is properly connected."
Aftr this error the server seems to shutdown unexpectedly and reboot. 30 second after the NIC error I get:
EVENT ID 1101: "Audit events have been dropped by the transport. The real time backup file was corrup de to improper shutdown.
I am not sure when the server physically shutsdown.
This is on a SBS 2008 server that is attached to an ISA 2006 server for its outside access. This happens almost every day at 5AM for the past few weeks.
Also the NIC in question is the secondary NIC that is being used for Hyper-V external netwok. The main NIC for this server that has the static IP address is an Intel NIC and has no errors.
Cliff Galiher
Did you install the Hyper-V role on your SBS box? That'll definitely break things!
Absolutely. Hyper-v on SBS2008 is not a supported configuration as memory serves.
Aye, its not. But sometimes you can get away with some configurations even when they aren't supported. Installing Hyper-V is *NOT* one of those cases. It definitely actively breaks things.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Russianblue,
Thanks! I'll give it a try. I have been running Hyper-V on SBS like this for almost two years and didn't have an issue until now. No changes to the environment since except windows updates.
I'll let you know how your remedy pans out.
Thanks! I'll give it a try. I have been running Hyper-V on SBS like this for almost two years and didn't have an issue until now. No changes to the environment since except windows updates.
I'll let you know how your remedy pans out.