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...
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.
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.1
Wireless 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.1
Tunnel 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)?Browse shows "resolving host" in lower left and then gives message
DNS_PROBE_FINISHED_BAD_CONFIG
Turn wifi back on I still get "resolving host" quite a bit but I connect. Also lots of blinking on LAN LED
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.