Question Locked

Computer won't boot if network cable is connected.

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is very weird and the first time I encountered it. Computer wasn't booting up, I thought it was the PSU but it wasn't. I did more troubleshooting, and after a long process, i found out that it was the network cable!

Computer won't turn on if the network cable was connected but once you disconnect it, it will boot up. So to turn on the computer I discoonect the network cable and then connect it once it starts booting up.

DOes anybody have a solution for this? or has anybody encountered the same problem?

HELP!!

14 replies

by oldbaritone

and make sure the NIC is not an active boot device.

My first guess would be that the NIC is trying to retrieve a boot image from the network, and there isn't one. When the network cable is unplugged, it "knows" it can't boot from network and moves to the next available device.

If you can't disable network boot, make sure it's at the bottom of the Boot Device list, below the internal Hard Drive and CD drive.

by ervee04

I checked that too! and network boot is not even enabled, I have hard drive and CD only

by oldbaritone

OK, at this point, I'm grasping at straws, but here's a couple more things that have stung me in the past:

DHCP - do you have more than one device active on the network issuing DHCP addresses? That's a no-no, but if a user brought in their own (unauthorized) router, they may have botched the setup.

PCI Interrupt chain - Try telling BIOS to reset and rebuild the PCI interrupt chain. It's an option in setup. Maybe there's a conflict.

Switch the cards around. I have one machine that if the NIC is in the slot next to the video, everything works fine, but if it's in any other slot, the machine hangs. So try just rearranging the cards and try to find a combination that works.

Try a different make/model of NIC. Some cards "don't work and play well with others." Try an add-in NIC and disable the on-board NIC, and see if that works.

After that, I'm about out of suggestions, so maybe the "plug the network in after it boots" may be the only viable work-around.

Good luck.

by oldbaritone

under Network Adapter, not in the Boot section.

PM me if you want.

by greyit

Shouldn't PXE automatically abort after a timeout, and the BIOS switch to the next in line for booting ?

by ormzen

I have the exact same problem, and have been asking some friends around. One said 'google it', and all I found was this forum.

Another said that it could be some ground faulting in the network cable and could be solved by buying a new one.

This is not yet confirmed though.

Ideas on this?

by ervee04

but it didn't work. I still haven't found a solution for it. For now whenever I restart we unplug the network cable and the plug it back in once its booted.

by ormzen

I tried to unplug the network cable in the other end. Still attached to the computer. I could boot, so it's not a faulty grounding.

I called my internet providers to see if they had encounter anything like this before, but they hadn't. Even though they could ensure it had nothing to do with my modem. He thought though, that it could be something with my network-card - somthing that it can't handle all the traffic at once during startup. Plausible?

by peconet tietokoneet

Depending on the age of the system in question,
a BIOS update would/should/could help you out of your issue.
:)

This discussion is closed to new replies.