Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

All connections over Ethernet won't work but WiFi works fine


  • Please log in to reply
5 replies to this topic

#1 Tennessee_Jed

Tennessee_Jed

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:17 AM

Posted 17 December 2017 - 07:32 AM

So here is my story. A couple days ago I awoke to having no internet access over any devices connected through Ethernet or Wifi. My first thought was it was just a fluke and to power cycle my router and modem. After doing so I still got nothing. Called up my ISP thinking that the internet might be down due to a winter storm we had that night. They said that it wasn't. They sent signals to my modem and everything appeared to be working properly.

My equipment then:

Arris SB6141
Asus RT-AC3200

So I decided to make a run to Best Buy (not my first choice but convenient) to pick up a new cable modem. Purchased a Arris SB6190. Got it home, called up ISP (Spectrum) and had them provision it. Everything went smooth. Well now I was getting internet but only over WiFi. So now I'm thinking that my router bit the dust. Took another trip to Best Buy and purchased a Linksys EA9500 router. Got home, hooked it all up, same exact thing. Wifi works but everything connected through Ethernet has no connection.

Here is my IPConfig:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-7HQ2CMF
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 70-85-C2-0A-10-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c4c8:3703:cba:b6%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.0.182(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 275809730
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-76-DC-58-70-85-C2-0A-10-CC
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 Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 76-19-F8-10-77-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : neo.rr.com
Description . . . . . . . . . . . : Realtek 8812AE Wireless LAN 802.11ac PCI-E NIC
Physical Address. . . . . . . . . : 74-19-F8-10-77-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


I've been pulling my hair out over this and I can't seem to figure it out. I've tried netsh winsock reset and all the other release and renew commands to no avail. I really hope that someone can help me out. I know that the 169.254 indicates that my router isn't handing out the IP so I checked and DHCP is definitely enabled. I'm at my wits end here so any help is MUCH appreciated.



BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 23,989 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:17 AM

Posted 17 December 2017 - 08:43 AM

I would try the following in order.

 

Replace the Ethernet cable if you have one available.

 

Do a power cycle. Remove the power. Hold the power button down for 30 seconds. Replace your power and boot. This has actually brought back Ethernet for some people.

 

Uninstall and Reinstall your Wifi driver.



#3 Tennessee_Jed

Tennessee_Jed
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:17 AM

Posted 17 December 2017 - 09:51 AM

Unfortunately I've tried all of that. When the devices are connected directly to the modem with their respective Ethernet cables they function properly. But when connected to the router I get 169.254.x.x address. All known working cables. Even went as far to buy a new router but the problem still persists. I also uninstalled and reinstalled my NIC driver. I've talked to a few techs and they are just as stumped as I am.

 

But thank you very much for your reply it is much appreciated.



#4 JohnC_21

JohnC_21

  • Members
  • 23,989 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:17 AM

Posted 17 December 2017 - 10:02 AM

You cloned the mac address of the computer in the router, correct? I would have to assume you did if Wifi works. Can you connect via Ethernet when using a static IP. It's really strange that Wifi works but Ethernet does not.



#5 Kilroy

Kilroy

  • BC Advisor
  • 3,391 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:01:17 AM

Posted 18 December 2017 - 04:39 PM

If you're getting a 169.254.x.x address you have a DHCP issue.  I'd check the DHCP setting on the router.



#6 Tennessee_Jed

Tennessee_Jed
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:17 AM

Posted 20 December 2017 - 03:09 PM

UPDATE:

 

Turns out they were bad Ethernet cables. Replaced all cables with new ones and everything is working correctly.

 

Thanks everyone for your replies!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users