Ethernet cable looping between identifying and disconnected

Christopher Briner

Reputable
Jul 23, 2015
1
0
4,510
Hi, I've been looking everywhere for an answer but haven't seen a solid answer as to how to fix this, I've tried :

Reinstalling windows 8.1
Setting up a static ip address for ethernet (Still goes to the loop and has a 169.xx.xx.xx) apipa
Editing my registry to disable ip autoconfiguration
unplugging computer and battery.
release renew ip
this is my ip config what is bolded is what is most concerning


C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SSDAminescent
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : attlocal.net

Wireless LAN adapter Local Area Connection* 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 30-3A-64-35-04-9F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 30-3A-64-35-04-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : C4-54-44-8A-F4-53
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b46f:5d8a:1e18:89e7%3(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.137.231(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 63198276
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-55-88-40-C4-54-44-8A-F4-53

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 . : attlocal.net
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3160
Physical Address. . . . . . . . . : 30-3A-64-35-04-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.65(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, July 23, 2015 9:19:27 PM
Lease Expires . . . . . . . . . . : Friday, July 24, 2015 9:19:28 PM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

C:\WINDOWS\system32>
C:\WINDOWS\system32>

I have been working on this for 3 days now, any help or information or suggestions you can provide are greatly appreciated
 
Solution
Well, an APIPA address only appears when the device can not, for whatever reason, connect to your DHCP server. Have you tried testing the cable/port to make sure it actually works? It sounds incredibly simple, but I've known many techs (including myself) who have gotten lost trying to find a more "advanced" solution because they completely forgot to cover the basics first. Any of the following works to test this out:
1) Try a different cable. If a different cable works, then you have a bad cable.
2) Plug the same cable into a different port on your device. It's possible that your device's port is bad
3) Plug the same cable into a different computer and see if it works. If a different computer works on the same port, your computer may...
Well, an APIPA address only appears when the device can not, for whatever reason, connect to your DHCP server. Have you tried testing the cable/port to make sure it actually works? It sounds incredibly simple, but I've known many techs (including myself) who have gotten lost trying to find a more "advanced" solution because they completely forgot to cover the basics first. Any of the following works to test this out:
1) Try a different cable. If a different cable works, then you have a bad cable.
2) Plug the same cable into a different port on your device. It's possible that your device's port is bad
3) Plug the same cable into a different computer and see if it works. If a different computer works on the same port, your computer may have a bad NIC

You mentioned that you are reinstalling your OS. Do you have your device drivers installed for your NIC? If not you may need to download them on a different computer, put them on a flash drive and install them on the computer that way.

Other than that, it looks like you have wireless. I've known some computers to have a conflict between wireless and wired Ethernet. Try turning off the wireless and see if something changes.
 
Solution