Troubleshooting a network controller?

[Heiski]

So, I have an old, pre-built system (Not actually mine, I use different PC), and it has suddently stopped connecting to Internet vie ethernet. It's not a software problem, since it doesn't work on ubuntu ether (Main OS is Vista, I'm testing with ubuntu from usb drive).

 

PROBLEM:

When In windows Vista, it says Unknown network and Limited connection (That's hopefully the translation...), Ubuntu just tries to connect, and after some time, says that I'm disconnected.

 

 

WHAT I HAVE TRIED:

I have tried using an ethernet cable that I know works, nothing. Lights on the ethernet socet on motherboard works fine, though. And as I've said, tried to use ubuntu from usb flash drive. Oh, and I've updated chipset and network controller drivers for windows, didn't work. I also, while in ubuntu, shared my phone's internet connection via usb, and it connected just fine. My phone is using wifi, from same router that the PC does not want to connect vie ethernet.

 

It is an pre-built old PC, so I don't have, for example, the mobo model (It's some old ASRock board).

Network controller is NVIDIA MCP51 Ethernet Controller, also some nVidia chipset. CPU is core 2 quad 8200

So, will I have to buy PCI controller or cant this still be somehow fixed? Or would seperate controller even work?

 

And sorry if I made some wierd mistakes, english is not my native language

 

[kewiha]

I'd look at the router. Blinking lights on the port is a good sign. I've had improperly wired ethernet cables (coloured wires aren't in correct order) work on some devices but not others. Try another cable with the colours arranged on both ends in the "B" config. If it's not too much trouble I might factory reset the router and re-enter your settings. If you're using long cables, or switches, try connecting as direcly as possible to your router.

 

Failed NICs are pretty uncommon, I'd guess it's something upstream causing the problem.

[Heiski]

Sorry, haven't been able to answer for a while... Anyway, I tried with bolt A and B type cables, no change. I also reset the router, still nothing. Oh, and I also disconnected everything else from the router, so that should not be problem ether. Windows is able yo ping to itself, but the weird thing is, that when I checked ipconfig from that pc, it showed ipv4 address that was not starting with 192... like everything else in the network, and when I tried to ping that ip but changing the last number to 1, it said that it couldn't find that host and proceeded to ping itself. I don't think that the fault is in router, since I'm using it right now, on a different pc. I guess some old ethernet card isn't expensive, so I could just buy one and try that...

[Blebekblebek]

if you unsure about cable, try to find ethernet cable from router/modem box that you have

it always bundled with 1 meter ethernet cable

 

check the IP setting and leave it auto if your network using DHCP

IP network isn't always start with 192, it depends on admin setting.

 

so in the end if onboard network is dead, you can add pci/usb lan adapter, just plug in and install the driver (if it's needed)

disable LAN Onboard from bios and you good to go.

[JaSoN_XzIoN]

.snip.

Have you tried uninstalling it from device manager and let it reinstall again? If that doesn't work try this command in an elevated cmd "netsh int ip reset"