Mobo won't boot with network cable in
Posted: Sun May 05, 2019 11:32 pm
Hi all,
I've had my rig since 2011, and as far as I can remember I've had this problem. I'd love to understand and/or solve it.
Intermittently, when I restart the computer it won't boot if the network cable is in. I get a single beep, it goes to the boot screen where it tells me to choose F2 for BIOS menu or F10 for boot menu, and that's that.
If I pull the network cable and restart, it gets to the second beep without a problem. That means it's booting successfully. I can then re-insert the network cable, and all is well.
I finally took a closer look here tonight. I thought it might be looking to boot from the network. But when this happened, I couldn't get anywhere with F2 or F10. I had to pull the network cable and restart, and then the keyboard worked and took me to the BIOS screen.
While it's true that network boot was enabled, it was number 3 or 4 on the list. Anyway, I disabled it, saved, and restarted. And...with network cable in, it beeped once and stopped there.
It's an Intel motherboard, DH55TC, with an Core i3-550 3.2 with good graphics processor for WMC duties built in. A single beep indicates that the BIOS is ready to accept keyboard input, but that doesn't appear to be the case. Nothing I do can get past that screen.
I started down this road because occasionally I'll boot an XBox extender and it won't be able to connect. The WMC rig is working fine otherwise. I have to restart it to get the extender to work, and when I restart it this happens--sometimes. Maybe half and half.
Thoughts?
I've had my rig since 2011, and as far as I can remember I've had this problem. I'd love to understand and/or solve it.
Intermittently, when I restart the computer it won't boot if the network cable is in. I get a single beep, it goes to the boot screen where it tells me to choose F2 for BIOS menu or F10 for boot menu, and that's that.
If I pull the network cable and restart, it gets to the second beep without a problem. That means it's booting successfully. I can then re-insert the network cable, and all is well.
I finally took a closer look here tonight. I thought it might be looking to boot from the network. But when this happened, I couldn't get anywhere with F2 or F10. I had to pull the network cable and restart, and then the keyboard worked and took me to the BIOS screen.
While it's true that network boot was enabled, it was number 3 or 4 on the list. Anyway, I disabled it, saved, and restarted. And...with network cable in, it beeped once and stopped there.
It's an Intel motherboard, DH55TC, with an Core i3-550 3.2 with good graphics processor for WMC duties built in. A single beep indicates that the BIOS is ready to accept keyboard input, but that doesn't appear to be the case. Nothing I do can get past that screen.
I started down this road because occasionally I'll boot an XBox extender and it won't be able to connect. The WMC rig is working fine otherwise. I have to restart it to get the extender to work, and when I restart it this happens--sometimes. Maybe half and half.
Thoughts?