"Ethernet" doesn't have a valid IP configuration

[baileyboy125]

I know that this question has been asked many, many times, however nothing I have tried works. The computer is over 4 years old (custom built) and have not had many issues. This problem just started suddenly without warning. Wifi works completely fine, although this PC has really bad wireless connection so it is usually disabled (So there wont be any conflicting networks).

List of the things I have tried and their results:

*Used Command Prompt (Admin)
*netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

*netsh int ip reset

Resetting Interface, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Restart the computer to complete this action.

*netsh winsock reset catalog

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

*netsh int ipv4 reset reset.log

Resetting , failed.
Access is denied.

There's no user specified settings to be reset.

*netsh int ipv6 reset reset.log

Resetting Neighbor, OK!
Resetting Path, OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.

*Uninstalling, reinstalling network adapter driver
*Updating drivers

Driver Version: 10.3.723.2015

*Changing LAN cable
*Turning off firewall
*Reseting and restarting router, as well as trying other ports
*Disabling and reenabling the network
*Made sure to tick 'Obtain an IP address automatically' and 'Obtain DNS server address automatically' (Though I have also tried to use manual addresses and DNS servers)

*Automatic diagnostic tool

Details about network adapter diagnosis:

Network adapter Ethernet driver information:

Description...................................: Realtek PCIe GBE Family Controller
Manufacturer...............................: Realtek
Provider.......................................: Realtek
Version.........................................: 7.67.1226.2012
Inf File Name...............................: C:\WINDOWS\INF\oem23.inf
Inf File Date.................................: Wednesday, December 26, 2012 4:24:04 PM
Section Name..............................: RTL8168FB.ndi
Hardware ID................................: pci\ven_10ec&dev_8168&rev_09
Instance Status Flags..................: 0x180200a
Device Manager Status Code......: 0
IfType..........................................: 6
Physical Media Type...................: 14

*ipconfig /release

Windows IP Configuration

Ethernet adapter Ethernet:

Connection-specific DNS Suffix....:
Link-local IPv6 Address................: fe80::31bc:2242:7a0:2f33%4
Autoconfiguration IPv4 Address....: 169.254.47.51
Subnet Mask.................................: 255.255.0.0
Default Gateway............................:

Tunnel adapter isatap.{477FA4E6-8BA8-442D-88E0-3502B685D64F}:

Media State..................................: Media disconnected
Connection-specific DNS Suffix....:

*ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

*ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has timed out.

*ipconfig /all

Windows IP Configuration

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

Ethernet adapter Ethernet:

Connection-specific DNS Suffix.....:
Description....................................: Realtek PCIe GBE Family Controller
Physical Address...........................: 10-C3-7B-A2-6E-31
DHCP Enabled..............................: Yes
Autoconfiguration Enabled............: Yes
Link-local IPv6 Address.................: fe80::31bc:2242:7a0:2f33%4(Preferred)
Autoconfiguration IPv4 Address....: 169.254.47.51(Preferred)
Subnet Mask.................................: 255.255.0.0
Default Gateway............................:
DHCPv6 IAID................................: 336642939
DHCPv6 Client DUID.....................: 00-01-00-01-1C-2C-85-50-10-C3-7B-A2-6E-31
DNS Servers.................................: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip.......................: Enabled

Tunnel adapter isatap.{477FA4E6-8BA8-442D-88E0-3502B685D64F}:

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

 

[SkyNetRising]

No. That is not correct.
You would need to know dhcp configuration from your router.

Default gateway - is lan address of your router.
Your PC ip address must be in same subnet as router lan ip address. And they can not be the same.

You said - your wifi works. So disconnect wired connection, connect through wifi and write down ip config you get that way (output of ipconfig /all).

 

[baileyboy125]

This is the wifi:

Wireless LAN adapter Wi-Fi TP-Link:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Qualcomm Atheros AR9287 Wireless Network Adapter
Physical Address. . . . . . . . . : 14-CC-20-CE-C6-80
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6d62:aa4:414c:6aa2%2(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 17 March 2017 01:18:36 PM
Lease Expires . . . . . . . . . . : 18 March 2017 01:18:36 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 102026272
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-2C-85-50-10-C3-7B-A2-6E-31
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

and so I changed the ipv4 to this: https://gyazo.com/b61004d3a320609811cd7c265a71f7f5

Still does not work though.

 

[SkyNetRising]

Ping the router:

• ping 192.168.1.254

 

[baileyboy125]

Results:

C:\WINDOWS\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>

 

[baileyboy125]

Any ideas?

 

[SkyNetRising]

You need to eliminate all possible problems:
faulty cable;
faulty lan card;
corrupted lan drivers;
faulty router.

Do you have another pc to connect to ethernet cable, youre using?
Can you check dhcp server settings on your router?

Your router is not responding to ping, but I'm not sure you entered the right ipv4 config. So can't really assume it's routers fault.

 

[baileyboy125]

Drivers are fine, I LAN card is fine too. I did find that plugging the Ethernet cable into another PC produced the same results. This tells me the problem probably lies with the power-line adaptors.

 

[SkyNetRising]

It's the first time you have mentioned any power line adapters. Don't you think - that's an important detail?
Connect your pc directly to router with ethernet cable. Try with manual and automatic ip settings.

 

[baileyboy125]

Sorry I missed it out. Also it is impossible to connect the PC directly to the router. The router is downstairs and the PC is upstairs. The Ethernet has seemed to started to work again for some reason, though I fear it will just go down again like last time.