[SOLVED] Ethernet cable connected router to pc but no internet

[jaguarx21]

I have multiple wired connections and wireless connections. This pc however does not work for ethernet all of a sudden.
This ethernet cable works fine as well as I connected it to my laptop and worked fine.
I've tried netsh winsock reset. netsh int ip reset
Ipconfig/flushdns , /release , renew
When I renew my ipconfig, it times out to DHCP connection
I've also downloaded and reinstalled network adapter (Intel(R) Ethernet Connection (2) I219-V) multiple times.
I've just tried reinstalling windows through media creation tool and still no ethernet connection.
I'm on my USB wireless adapter right now but would like to switch back to my ethernet.
Thanks for help in advance.

Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-U3EFEFO
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hitronhub.home

Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : C6-A8-1D-00-D5-0F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : C6-A8-1D-00-DD-0F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
Physical Address. . . . . . . . . : E0-D5-5E-48-99-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd00:fc:8ddd:4861:a884:5c98:827f:a407(Preferred)
IPv6 Address. . . . . . . . . . . : fd00:fc:8ddd:4862:a884:5c98:827f:a407(Preferred)
Temporary IPv6 Address. . . . . . : fd00:fc:8ddd:4861:2586:6244:5d05:e1a(Preferred)
Temporary IPv6 Address. . . . . . : fd00:fc:8ddd:4862:2586:6244:5d05:e1a(Preferred)
Link-local IPv6 Address . . . . . : fe80::a884:5c98:827f:a407%6(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.164.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 216061278
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-8E-CA-7A-E0-D5-5E-48-99-0B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : hitronhub.home
Description . . . . . . . . . . . : D-Link DWA-182 Wireless AC Dual Band USB Adapter
Physical Address. . . . . . . . . : C4-A8-1D-00-D5-0F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd00:fc:8ddd:4862:482:45ef:9402:e90b(Preferred)
Temporary IPv6 Address. . . . . . : fd00:fc:8ddd:4862:98c6:4358:ad82:7b9f(Preferred)
Link-local IPv6 Address . . . . . : fe80::482:45ef:9402:e90b%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.29(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : December 20, 2019 11:27:55 AM
Lease Expires . . . . . . . . . . : December 27, 2019 11:27:54 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 130328605
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-8E-CA-7A-E0-D5-5E-48-99-0B
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[kanewolf]

Always start with a short, new 100% copper, cat5e cable from your PC directly to the router. No wall plates, no flat cables, no handmade cables. You have to eliminate the physical infrastructure first.

 

[SamirD]

Try booting a linux livecd and see if that recognizes the nic. If so, then it's a software issue in windows. If not, then I would try a different nic--even a cheap usb one will be a good test.

 

[tingety]

Most Mobo's have lights to indicate the flow of 'packets'. When you plug in the cable, do you see anything light up? (assuming you have lights on your NIC)

If they don't light up at all, that could indicate a problem with the NIC itself. I'd try what @SamirD posted above with trying using a Live boot of Linux and it's integrated drivers to see if it is simply a driver initialisation issue in Windows itself.

If Linux also doesn't recognise anything and you see no lights, good chance that NIC is dead. If you have a spare PCI/PCI-E slot you could get a replacement, they're rather cheap. If not, a USB one can do.

 

[Momosh]

I am in a similar predicament. I am running Windows 10 64-bit on a PC with an Asus Rampage V Extreme mobo. As from yesterday, the ethernet connection lapsed into "unidentified network" status. Thank God, I still have a WiFi connection. I have updated the drivers for the NIC, uninstalled, and reinstalled them, played around with the system configuration, reset the modem, all to no avail. Currently, I have connected my third cable. Lights come on at the computer end with all three cables. I have run diagnostics tests with the Intel PROSet Adapter Configuration Utility. Cables usually give positive results. This third and fresh cable certainly does. Hardware tests always give positive results. Whereas, connectivity tests fail with "Connection Status: Failed" and "Cable Link Status: Failed - This device requires a restart". I have booted from a Ubuntu Linux USB (try only, without install). Ubuntu pretended to recognize a "Wired Network" (but no WiFi), reflected decent-looking IP addresses, however Firefox failed to load any Web pages nor was there any other sign of connectivity. Apparently, there was no actual Internet connection under Ubuntu. Or was it my unfamiliarity with that operating system? Please take it from there...

 

[SamirD]

I am in a similar predicament. I am running Windows 10 64-bit on a PC with an Asus Rampage V Extreme mobo. As from yesterday, the ethernet connection lapsed into "unidentified network" status. Thank God, I still have a WiFi connection. I have updated the drivers for the NIC, uninstalled, and reinstalled them, played around with the system configuration, reset the modem, all to no avail. Currently, I have connected my third cable. Lights come on at the computer end with all three cables. I have run diagnostics tests with the Intel PROSet Adapter Configuration Utility. Cables usually give positive results. This third and fresh cable certainly does. Hardware tests always give positive results. Whereas, connectivity tests fail with "Connection Status: Failed" and "Cable Link Status: Failed - This device requires a restart". I have booted from a Ubuntu Linux USB (try only, without install). Ubuntu pretended to recognize a "Wired Network" (but no WiFi), reflected decent-looking IP addresses, however Firefox failed to load any Web pages nor was there any other sign of connectivity. Apparently, there was no actual Internet connection under Ubuntu. Or was it my unfamiliarity with that operating system? Please take it from there...

You really should start your own thread and hopefully a mod will split off your post into its own thread.

You've done a good job of doing some diagnostics. I would say that your nic is fine but just that version of a linux livecd didn't recognize it well. Try another livecd and see if that's any better. I recommend TENS as it is designed to work with a broad range of hardware:
https://www.tens.af.mil/download.htm

 

[Momosh]

You really should start your own thread and hopefully a mod will split off your post into its own thread.

You've done a good job of doing some diagnostics. I would say that your nic is fine but just that version of a linux livecd didn't recognize it well. Try another livecd and see if that's any better. I recommend TENS as it is designed to work with a broad range of hardware:
https://www.tens.af.mil/download.htm

I have downloaded and booted from TENS. The situation is akin to Ubuntu. TENS appears to detect the wired network with a "connection established" message. Network inquiry displays that the computer IP, default gateway, and DNS addresses are the same as under Windows. However, under TENS, there is no actual connectivity. Firefox fails to load any Web pages. If I refresh the so-called wired connection, or switch it off and on again, TENS gives up the pretense and refuses to reconnect.
Moreover, TENS fails to recognize any WiFi networks although they are actually available.
I have noted that the DNS addresses are funny. There are three of them, none resembling anything I may have configured. I have switched to Google Public DNS servers. But the ethernet connection is still elusive.
On a sideline, twice I have rolled back the system drive from image backups, going back to times before the commencement of the "unidentified network" troubles. The "unidentified network" blues still plagued the system as regressed.
There is still an orange glow at the computer end of the network cable. However, I am inclined to accept that this is a hardware issue.
I wonder what my betters think.

 

[SamirD]

Yeah, if it's dead in TENS then I think it's "Dead Jim". Especially if you remove the cable and the nic light is still on.

I'd just get a 2.5Gps usb 3.0 nic and enjoy the easy upgrade.

 

[Momosh]

Yeah, if it's dead in TENS then I think it's "Dead Jim". Especially if you remove the cable and the nic light is still on.

I'd just get a 2.5Gps usb 3.0 nic and enjoy the easy upgrade.

I plugged in the cheapest USB to Ethernet adapter I could lay my hands on. It works like a charm. Soon, I will buy something better as suggested.
Thank you.