NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
No Internet on LAN Ports WiFi fully connectivity
I am stumped. I have full internet connectivity via WiFi but “no internet” via the hard wired LAN ports. Here is the summary:
- Both the R7000 and R6800 were fully functioning routers
- Previously had internet service with ATT via fiber at Gb speed
- Moved and now have cable internet with Spectrum a 100 Mb speed (very sad)
- Laptop plugged directly into cable modem everything works fine no connectivity issues.
- Add either router R7000/R6800 and I get full connectivity via WiFi connections, but no connectivity via any of the 4 hardwired LAN ports. Browser indicates "DNS Probe Finished Bad Config" Error. Networking icon in low right shows “no internet". Troubleshooting in Windows Networking indicates issues with DNS Server.
- Appropriate LAN LEDs (those with connections) illuminate accurately in my case white. LEDs on laptop Ethernet adapter flash so the ports seem to be good. Would be strange is all 4 LAN ports on 2 different routers went bad.
- I can access the router via the LAN port at 192.168.1.1.
Troubleshooting actions:
- PC/Laptop connected directly to cable modem – no issues – full connectivity
- Added R7000 router - Wifi connection to internet works fine, no connectivity on LAN
- Swapped R7000 with R6800 - Wifi connection to internet works fine, no connectivity on LAN
- Reset (pushed and held reset switch) for both R7000 and R6800 but no change from above behavior WiFi Good LAN bad
- Tried multiple Ethernet cables – no change
- Tried DNS settings on routers using both “get from ISP” as well as Google DNS 8.8.8.8, 8.8.4.4 – still doesn’t work.
I am truly baffled. The only change from two fully functioning routers to two routers with no LAN connectivity is that I switched ISPs from ATT to Spectrum (previously Charter). But connecting to the interent via direct connect to the modem on the modem's LAN port works just fine. I also don’t understand why I have no issues with these routers when connecting via WiFi and yet the hardwired LAN connection cannot seem to access the internet. Using Windows 10.
I appreciate any suggestions you might have.
Finally figurred it out - pretty simply. There was a non-valid hard-coded DNS address on the IPv4 Ehternet adapter. Everything cleared up when I removed it.
5 Replies
The easiest explanation (for wireless working and wired not working)
would be that your wireless devices/interfaces are configured to use
DHCP to get their network data, but the wired devices/interfaces are
configured with manual/static data which are incompatible with the
Netgear routers (wrong subnet, for example).
> [...] Using Windows 10.
Open a Command Prompt (CMD.EXE) window, type an "ipconfig" command
there, and copy+paste the results here. Or, compare the addresses used
by a wireless device with those used by a wired device.Here is the ipconfig data
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.C:\Users\Main>ipconfig
Windows IP Configuration
Ethernet adapter Ethernet:Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::45e7:c9b6:ba9b:4ac7%16
IPv4 Address. . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :Wireless LAN adapter Local Area Connection* 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::f8a6:f558:71a:4ca0%12
IPv4 Address. . . . . . . . . . . : 192.168.1.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:1464:38e5:3f57:fef9
Link-local IPv6 Address . . . . . : fe80::1464:38e5:3f57:fef9%7
Default Gateway . . . . . . . . . : ::C:\Users\Main>
C:\Users\Main>
C:\Users\Main>
> Ethernet adapter Ethernet:
>
> Connection-specific DNS Suffix . :
> Link-local IPv6 Address . . . . . : fe80::45e7:c9b6:ba9b:4ac7%16
> IPv4 Address. . . . . . . . . . . : 192.168.1.6
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
Looks ok to me.
> Wireless LAN adapter Wi-Fi:
>
> Connection-specific DNS Suffix . :
> Link-local IPv6 Address . . . . . : fe80::f8a6:f558:71a:4ca0%12
> IPv4 Address. . . . . . . . . . . : 192.168.1.8
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
Also ok, but if they'e both active at one time, then everyone could
get confused.
> The easiest explanation [...]
Clearly not what you're seeing. But one system with two interfaces
on the same subnet could be troublesome. What happens if you disable
the wireless interface (on the Windows system)?