Odd ethernet problem

[klemenko1v1]

Hi!

Today I got my friends computer in for fixing. Let me explain: when you turn on the computer ethernet doesnt work until you replug the cable a dozen times(then it lights up) sounds like pc is turning of ethernet. Friend already tried an ethernet card a new tp link one... Same issue. I tried to reinstall windows, change all drivers, checked bios and reenter dnses and ips manually... Still thr same issue.

Any ideas?

Thanks in Advance!

EDIT: Solution

Even when I changed the router issue continued... Because I have 3 more pcs on the same network and they all have a static ip there was an ip conflict... I simply assigned a new static ip to the pc(on the router AND on pc) and it worked!

Thanks for all the help!

 

[RealBeast]

A bad cable or bad LAN port on the switch or router could be the issue. Have you checked them?

 

[klemenko1v1]

A bad cable or bad LAN port on the switch or router could be the issue. Have you checked them?

Yes I´ve tried with another cable, router, even with another network
Issue persists

 

[RealBeast]

And you have already done a clean reinstall of Windows, replaced the Ethernet adapter, and you still have to plug in the cable multiple times for it to function?

 

[jsmithepa]

Something simpler: Shine a light in there, there is a dust ball in the RJ45.

 

[klemenko1v1]

@RealBeast

Yes that is correct

@jsmithepa

First i am sorry for downvoting as i trued to figure out how to quote on mobile and as you can see it didnt work. Regarding your advice... I am sure ther is no dust in a the jack, cable or the pci slot where another network card is connected

 

[RealBeast]

That really only leaves another basic part like the motherboard -- I would try the Ethernet card in another machine to insure it works, and I expect that it will.

You could also try the Ethernet card in another slot on the motherboard since the onboard Ethernet failed a PCIe slot could also have failed. And also check that the built in Ethernet port is disabled in the bios.

 

[cdheer]

I have actually seen this very problem (well, very similar anyway) and it was a power supply issue. A bad/failing power supply can cause all sorts of weirdo problems.