So, the other day, my Gigabyte p35-dq6’s onboard LAN stopped working. At first, it told me there was a cable disconnected, even though this wasn’t the case(I checked the cables, they work with other computers). Then, after a reboot, the computer couldn’t detect a network adapter at all.

So, after some frustration, I went and bought a cheap 10/100 NIC, and installed it. Windows Vista detected it, and I installed the driver. However, it gives me the same “Cable Disconnected” error.

I’m using a Linksys wireless router. It’s working fine for 1 wireless computer, and 1 wired computer. It has lights that indicate which of the 4 wired ports have computers connected. When I connect my computer to the cheap NIC and boot up, the light on the router for my computer shows green, as if it were connected. Then, once the Windows boot-up screen comes up, the light abruptly turns off, and doesn’t come on again. The computer insists that there is a cable unplugged.

This mobo was working fine for 4 months. Does anyone have any ideas? It has also just started to do something else weird: when I turn off the computer in Vista, the OS shuts down, and some of the internal fans turn off… But the system doesn’t power down all the way. I have to hold the power button to shut down completely.

Any ideas? Please? I REALLY don’t want to RMA this thing, or pay another $250 for a new mobo when I already paid for one…

if your loosing both onboard as well as an addon card, I am willing to bet an OS problem.

Did you try going into device manager and disabling the onboard from there? Or disable it in the bios? Sometimes things are finicky, might be on the new one you installed, it could be seeing the old one, and that could be causing probs with the new one.

Click Start/Windows
In the search box type: CMD
When the dialog pops up, type: netsh winsock reset
press the enter key
restart your comp


That should restart the communications stack.

^ yeah, I have seen that before...I had a small app/script to do it....but thats even better

Scotteq: That didn't work.

I'm going to ry installing a wireless network card. However, I'm pretty sure it won't work. When that fails, maybe I'll try installing XP. Vista sucks ass anyways...

your system is going into sleep mode dumbass.

Well... Given that the other two devices you have aren't working, it's probably safe to say that your prediction will come true, and your wireless NIC will fail as well.

The next suspect would be your firewall software. But since you don't seem to want to pursue this further, Good Luck with that OS reinstall.

Are you overclocking? If you are, try seeing if you run at default speed if your onboard LAN port will start working. Of course you could also make sure the LAN port hasn't disabled itselft somehow in the BIOS while your at it. I have seen aggressive overclocking cause onboard devices and/or PCI adapter to stop working, especially if the PCI and PCI-E buses aren't locked at 33.33 and 100 respectively.

Ive had a similar problem before and it was the router, make sure to try plugging into different ports in the back of the router and resetting the router. try a different cable.

Did you try a different cable?
Did you try a different port on your router?

Skittle:

No, dumbass, it is not. I am specifically SHUTTING DOWN, not going into sleep mode. It worked just fine for 4 months SHUTTING DOWN, that way. Now suddenly, the same command to shut down doesn't turn off the power to all components.

Scotteq: Yea, the wireless NIC isn't working either. Installing XP is going to have to wait, because it's freaking expensive.

I've tried different cables, reset the router, etc... Nothing. The router detects the computer, until Vista boots up. Then, there seems to be no connectivity. Ugh.

I'm not overclocking.

Thats actually the first time I've heard of that happening in Vista. I've seen it happen dozens of times with XP. By the sounds of that issue and the hanging up on shut down it sounds like you've managed to corrupt your OS. You can waste your money on XP but there's no reason to believe whether it will affect if this will happen again or not.

While I do suspect some sort of OS problem, I'm nto so sure. I use Norton Ghost, and I backed up my C drive as soon as I got things working the way I wanted them back in September. I've restored that a couple of times now, but it doesn't fix the problem.

Y'know, sometimes I feel like there's something about *me* that makes my home-built computers come up with the most bizarre and untraceable errors imaginable. It's like the gods are conspiring to make sure that whatever money I save by building one myself is wasted in replacing inexplicably malfunctioning parts.

Maybe my house was built on an indian burial ground.