No network access via Ethernet. Suspected hardware issue but unsure how to fix.

Tomtaylr

Commendable
Jul 9, 2016
2
0
1,510
Over the past few days I have been mostly unable to get Internet access on my PC via Ethernet or my edemax wifi adapter. There are no issues with the router as it works with several other devices and I have tried swapping out Ethernet cables etc.

The Ethernet connection is both receiving and sending packets but it has no connection to ipv4 or ipv6. When running the troubleshooter it identifies no problems and just says there are no issues but that there is no network available. It did work for a very short while this morning when I first started my PC but soon stopped.

The wifi adapter identifies a series of connections and appears to connect but then is unable to load websites and then suddenly cannot identify any connections. It works sometimes after restarting.

I have repeatedly tried to hard reboot and tried common suggestions like disable/enable adapters and disabling ipv6 but nothing has worked so far.

Since the only thing that seemed to have worked for a short while was it being off overnight and the fact that it is the only device playing up I think that it may be a hardware issue but I don't know what it could be and how it could be fixed.

I hope this isn't too much of a repost as I have read through countless posts with similar issues but nothing has worked so far for me. Thanks in advance for any advice.

Specs:

Windows 10 Home 64-bit

AMD FX-8350

ASUS M5A97 LE R2.0
 
Solution
OK, so a 169. address means it can't get an address. Power cycle your router, and run and then disable/enable your adapter.

if that does not work reset your winsock: netsh winsock reset

Reboot and see if you have an address. Any other devices on the network connected without issue?

Tomtaylr

Commendable
Jul 9, 2016
2
0
1,510



Here is the ipconfig, the WiFi adapter is kind of working but I'm mostly concerned with the ethernet issues.

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tom-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 74-DA-38-33-A5-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : AC-9E-17-EC-F5-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a9f3:4196:7c96:e209%8(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.226.9(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 0.0.0.0
DHCPv6 IAID . . . . . . . . . . . : 229416471
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-65-89-43-AC-9E-17-EC-F5-AB
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:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 150Mbps Wireless 802.11b/g/n Nano USB Adapter
Physical Address. . . . . . . . . : 74-DA-38-33-A5-25
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{46270573-F08B-46FA-99F5-7C546309FBAE}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 

01111111

Respectable
Jun 7, 2016
179
0
1,860
OK, so a 169. address means it can't get an address. Power cycle your router, and run and then disable/enable your adapter.

if that does not work reset your winsock: netsh winsock reset

Reboot and see if you have an address. Any other devices on the network connected without issue?
 
Solution