LAN network adapter randomly stopped working

Toggle sidebar Toggle sidebar
C

Corey_1

Reputable
Sep 14, 2015
5
0
4,510
My LAN network adapter stopped working suddenly last week. I hadn't made any changes to the computer that I can think of. I can still access the internet through wireless. I have looked at more than a dozen other posts with similar issues, but none of the solutions have helped. Please work with me to get this figured out.

The network shows up as "Unidentified Network - No Network Access". In status, there are some sent packets, but 0 received. I have disabled IPv6.

Below is my IP configuration.

Thank you in advance.

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Physical Address. . . . . . . . . : D4-3D-7E-BD-88-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.185.167(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection 5:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #4
Physical Address. . . . . . . . . : 60-6C-66-8E-68-5F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #3
Physical Address. . . . . . . . . : 60-6C-66-8E-68-5F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 2230
Physical Address. . . . . . . . . : 60-6C-66-8E-68-5E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.164(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, September 14, 2015 12:08:01 AM
Lease Expires . . . . . . . . . . : Tuesday, September 15, 2015 12:13:29 AM
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2
Physical Address. . . . . . . . . : 60-6C-66-8E-68-62
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
 
Solution
T
Hiya, Corey_1... I'm afraid I don't have an answer for you, BUT I did want you to know you're not alone. This *exact* same thing happened to me two days ago. The only thing I can think that changed was I installed a dozen or so "important" Windows 7 updates. Was that the case with you? Or maybe you have auto-update on?

I'm going to try uninstalling the updates one at a time later tonight, see if that does anything. Solidarity!

Someone in another thread also mentioned something about "An IP address in the range 169.254.xx.xx is called an APIPA address and its an internal auto assigned address," meaning the router is not providing one as it should? Maybe that's a clue (as my wired ethernet also has an IP in that range, like you)...
Sort by date Sort by votes
V

vesp3r

Distinguished
Dec 11, 2014
913
2
19,465
there usually isnt much that could go wrong with a network adapter. Its either your cable or your network configuration... or if you updated driver. If those arent the case then i would say its toasted. If you are on laptop it wouldnt be much of a loss since you got wireless. on other pc however you can always put another adapter and see if it works

And make sure you havent disabled the adapter
 
Upvote 0 Downvote
C

Corey_1

Reputable
Sep 14, 2015
5
0
4,510


Indeed I haven't disabled the adapter. I suppose I can try another adapter, but can anybody think of additional troubleshooting?
 
Upvote 0 Downvote
V

vesp3r

Distinguished
Dec 11, 2014
913
2
19,465
you can try the windows troubleshooter and it should give you some information... like "DNS not responding" or something else depending on your problem.
Still if you cant get another network adapter that fast you can always try system restore to a day that it worked
 
Upvote 0 Downvote
C

Corey_1

Reputable
Sep 14, 2015
5
0
4,510


Windows Network Diagnostics tells me only to "Investigate router or broadband modem issues", of which there are none that I can see, and I have no system restore points.
 
Upvote 0 Downvote
J

joseph p

Reputable
Aug 19, 2015
83
0
4,660
Try a static IP, I am no network genius but looking at your wireless ip config this should work. Perhaps if I am wrong someone with more knowledge can suggest static IP settings that should work.

IP 192.168.1.185
Subnet 255.255.255.0
Gateway 192.168.1.254
DNS 192.168.1.254
 
Upvote 0 Downvote
T

TheMook

Distinguished
Dec 17, 2011
6
0
18,520
Hiya, Corey_1... I'm afraid I don't have an answer for you, BUT I did want you to know you're not alone. This *exact* same thing happened to me two days ago. The only thing I can think that changed was I installed a dozen or so "important" Windows 7 updates. Was that the case with you? Or maybe you have auto-update on?

I'm going to try uninstalling the updates one at a time later tonight, see if that does anything. Solidarity!

Someone in another thread also mentioned something about "An IP address in the range 169.254.xx.xx is called an APIPA address and its an internal auto assigned address," meaning the router is not providing one as it should? Maybe that's a clue (as my wired ethernet also has an IP in that range, like you).

EDIT: Okay, I had run the Windows Diagnostic tool a couple of times this morning, it "reset the adapter" with no change. However, I just ran it a third time before I started uninstalling updates, and my wired connection is now running normally again.

The Windows Diagnostic Report said, "'Local Area Connection' doesn't have a valid IP configuration." I happened to have the cmd window "ipconfig" info still open from before, when it wasn't working, and can compare it to a new one, now that it is working.

Not Working:
Ethernet Adapter "Local Area Connection"
Autoconfiguration IPv4 Address: 169.254.blah.blah (not the real IP, obv)

Working:
Ethernet Adapter "Local Area Connection"
IPv4 Address: 192.168.blah.blah

As you can see, it certainly seems like an IP address issue. The timing on this sure sounds like something external (like a Windows Update) has changed something, since like you I have had this wired connection with no problems for 3+ years. I would really, really like to know why suddenly now it's having issues getting a proper IP.

Edit 2: I actually notice now that there seems to be a wave of questions about "local area connection doesn't have a valid ip configuration" all in the past week, both here and at other sites. Something is definitely up. :(
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom