Tech Support Guy banner
Status
Not open for further replies.

Intermittent DNS Issues

5K views 35 replies 3 participants last post by  noahlh 
#1 ·
Equipment:
  • My Router: Nighthawk(R) X4S R7800
  • Issue persists on multiple client machines (Desktop PC, Asus Zenbook, Android Phone)
  • Started after I reset my router.
  • I have tried setting DNS Servers to 8.8.8.8 and 8.8.4.4. as well as 1.1.1.1 1.0.0.1 in both local adapter settings and router settings.
  • I have tried ipconfig /release /flush & /renew
  • I have tried "netsh winsock reset" & "netsh int ipv4 reset"

I downloaded Minitoolbox.exe from http://download.bleepingcomputer.com/farbar/MiniToolBox.exe

running it produced this output:

MiniToolBox by Farbar Version: 17-06-2016
Ran by noahl (administrator) on 01-04-2020 at 21:24:04
Running from "C:\Users\noahl\Downloads"
Microsoft Windows 10 Pro (X64)
Model: To Be Filled By O.E.M. Manufacturer: To Be Filled By O.E.M.
Boot Mode: Normal
***************************************************************************

========================= Flush DNS: ===================================

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

========================= IE Proxy Settings: ==============================

Proxy is not enabled.
ProxyServer: 125.99.100.193:53826

"Reset IE Proxy Settings": IE Proxy Settings were reset.

========================= FF Proxy Settings: ==============================

"Reset FF Proxy Settings": Firefox Proxy settings were reset.

========================= Hosts content: =================================
========================= IP Configuration: ================================

VirtualBox Host-Only Ethernet Adapter = VirtualBox Host-Only Network (Connected)
TRENDnet TEW-809UB AC1900 Wireless USB Adapter = Wi-Fi 2 (Connected)
Xbox Wireless Adapter for Windows = Local Area Connection (Connected)
ExpressVPN TAP Adapter = Ethernet 2 (Hardware not present)
Intel(R) I211 Gigabit Network Connection = Ethernet (Media disconnected)

# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset

popd
# End of IPv4 configuration

Windows IP Configuration

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

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
Physical Address. . . . . . . . . : 70-85-C2-FC-42-96
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-17
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.173.205(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #5
Physical Address. . . . . . . . . : 3E-8C-F8-FE-12-BD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 14:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #6
Physical Address. . . . . . . . . : 3C-8C-F8-FE-12-BD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TRENDnet TEW-809UB AC1900 Wireless USB Adapter
Physical Address. . . . . . . . . : 3C-8C-F8-FE-12-BD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, April 1, 2020 9:19:57 PM
Lease Expires . . . . . . . . . . : Thursday, April 2, 2020 9:19:59 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Ping request could not find host google.com. Please check the name and try again.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Name: yahoo.com
Addresses: 2001:4998:44:41d::3
2001:4998:44:41d::4
2001:4998:58:1836::11
2001:4998:c:1023::5
2001:4998:c:1023::4
2001:4998:58:1836::10
98.137.246.7
72.30.35.10
72.30.35.9
98.138.219.231
98.137.246.8
98.138.219.232

Pinging yahoo.com [98.137.246.7] with 32 bytes of data:
Reply from 98.137.246.7: bytes=32 time=28ms TTL=53
Reply from 98.137.246.7: bytes=32 time=19ms TTL=53

Ping statistics for 98.137.246.7:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 28ms, Average = 23ms

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
11...70 85 c2 fc 42 96 ......Intel(R) I211 Gigabit Network Connection
23...0a 00 27 00 00 17 ......VirtualBox Host-Only Ethernet Adapter
8...3e 8c f8 fe 12 bd ......Microsoft Wi-Fi Direct Virtual Adapter #5
14...3c 8c f8 fe 12 bd ......Microsoft Wi-Fi Direct Virtual Adapter #6
24...3c 8c f8 fe 12 bd ......TRENDnet TEW-809UB AC1900 Wireless USB Adapter
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 36
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
169.254.0.0 255.255.0.0 On-link 169.254.173.205 281
169.254.173.205 255.255.255.255 On-link 169.254.173.205 281
169.254.255.255 255.255.255.255 On-link 169.254.173.205 281
192.168.1.0 255.255.255.0 On-link 192.168.1.2 291
192.168.1.2 255.255.255.255 On-link 192.168.1.2 291
192.168.1.255 255.255.255.255 On-link 192.168.1.2 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 169.254.173.205 281
224.0.0.0 240.0.0.0 On-link 192.168.1.2 291
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 169.254.173.205 281
255.255.255.255 255.255.255.255 On-link 192.168.1.2 291
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 331 ::1/128 On-link
1 331 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\napinsp.dll [54784] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\pnrpnsp.dll [70656] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [70656] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\winrnr.dll [23552] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\NLAapi.dll [70144] (Microsoft Corporation)
Catalog5 07 C:\Windows\SysWOW64\wshbth.dll [50688] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 11 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 12 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 13 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
Catalog9 14 C:\Windows\SysWOW64\mswsock.dll [324920] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\napinsp.dll [68096] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\pnrpnsp.dll [86528] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [86528] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\winrnr.dll [31232] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\NLAapi.dll [93184] (Microsoft Corporation)
x64-Catalog5 07 C:\Windows\System32\wshbth.dll [64000] (Microsoft Corporation)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 11 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 12 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 13 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
x64-Catalog9 14 C:\Windows\System32\mswsock.dll [407544] (Microsoft Corporation)
 
See less See more
#2 ·
First thing to do is reset your network. Meaning to unplug the modem and the router. After 30 seconds or so plug in the modem. After it "settles" plug in the router. Let it "settle" and try again. If you actually have a modem/router combo and no router than just do the reset with the modem/router.

Theory: with all the extra people at home using the internet your neighborhood (or wider area) is particularly hard hit.

DNS requests timing out and half the 4 pings to yahoo.com failing are data supporting this theory.

Half the pings to 127.0.0.1 failing are data that says maybe there is something wrong with the PC. But other devices with the symptoms indicate this is data to be ignored.

Do you have any other data to indicate the validity or falsity (is that a word?) of my theory? Data could include pings to various sites by various devices, web sites that are "working" with a sudden "not connected" type message, neighbors anecdotal reports of good or poor service.
 
#3 ·
I didn't do a good job of providing all the relevant information in the OP.

I am in an apartment building that provides internet for free, so I don't have a cable modem, I only have a router. I had zero issues before I reset the router. I only had to reset the router because I was attempting to chance the password, but it didn't save properly to my clipboard so I was locked out.

I can connect my devices to a nearby xfinity wifi hotspot and everything works perfectly, so it's not my PC. Given that I had no issues before resetting my router, I don't believe there's a building-wide issue with the internet. I believe it is a problem with my router configuration.

More on the router:

When I reset the router it runs a setup "wizard" that tries to detect settings. At one point it asks me if I can turn off the wifi for the gateway on the network. If I can, it tells me to not click "finish" until I'm connected to the router, but as soon as I connect to the router the browser navigates to a different page. If I tell it I can't turn off the wifi this page never is presented and the wizard ends by showing me my SSIDs and Passwords.

Sometimes when I fiddle with settings in the router menu the router will send me to a page on "routerlogin.net" which of course rarely works.

I've tried disabling DHCP and moving to a static IP. I've tried entering DNS servers (8.8.8.8 and 8.8.4.4) directly on the router, on my adapter, on both....nothing seems to help.

On my router home page it almost always says "Internet Status: Good" even when there's no working DNS.
 
#4 ·
Apparently you reset the router to factory defaults; not the simple reset I inferred from your post. By the way, I have no trust in those wizards; much prefer to configure myself.

My guess, given your new information, is that your router defaults to the same LAN IP range (e.g., 192.168.0.x or 192.168.1.x) as the apartment's router. Check what WAN IP it got or connect a PC directly to the apartment's connection.

If both routers are using the same LAN IP the result is almost always that internet access through the second router (that is, yours) is non-existent or pretty unreliable. A fix would be to change yours to 192.168.3.x). I suggest that because nobody uses it except some people who have daisy-chained routers--it's a good reminder.
 
#8 ·
Scanning the network using the SoftPerfect Network Scanner I can see my router at 192.168.0.106. I used to be able to see the gateway at 192.168.0.1 and bring up a login prompt http requesting that address, but can't seem to see it at the moment.

My router is typically accessible via http at 192.168.1.1, and it is a DHCP server for 192.168.1.2 through 192.168.1.254

I just set my LAN to 192.168.3.2 through 254, so I will see how that goes.

I'm so annoyed by my router's GUI at this point I'm considering flashing DD-WRT, but a bricked router would be awful right now.
 
#11 ·
Here are the tracert results:

C:\Windows\system32>tracert 92.242.140.2

Tracing route to 92.242.140.2 over a maximum of 30 hops

1 2 ms 2 ms 2 ms READYSHARE [192.168.3.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
#12 ·
Changed DNS on Router to 8.8.8.8 / 8.8.4.4 and ran tracert 92.242.140.2

C:\Windows\system32>tracert 92.242.140.2

Tracing route to 92.242.140.2 over a maximum of 30 hops

1 2 ms 2 ms 3 ms READYSHARE [192.168.3.1]
2 * 192.168.0.1 reports: Destination net unreachable.
 
#14 ·
I have progress!

I found a USB->Ethernet adapter and connected my laptop straight to the wall, and the internet works great, so the issue is purely with my router and its communication with the gateway.

From the laptop I ran tracert:

C:\WINDOWS\system32>tracert 92.242.140.2

Tracing route to unallocated.barefruit.co.uk [92.242.140.2]
over a maximum of 30 hops:

1 192.168.0.1 reports: Destination net unreachable.

Trace complete.

C:\WINDOWS\system32>tracert google.com

Tracing route to google.com [2607:f8b0:400a:804::200e]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 2601:602:9901:ba40:c2c5:22ff:fef7:28dd
2 10 ms 11 ms 9 ms 2001:558:4082:91::1
3 10 ms 9 ms 10 ms 2001:558:a2:6b::1
4 11 ms 14 ms 9 ms po-2-rur102.seattle.wa.seattle.comcast.net [2001:558:a0:3e::2]
5 23 ms 13 ms 10 ms 2001:558:a0:17e::1
6 * * * Request timed out.
7 15 ms * * be-2411-pe11.seattle.wa.ibone.comcast.net [2001:558:3:3b::2]
8 10 ms 11 ms 9 ms 2001:559:0:80::5f6
9 * * * Request timed out.
10 13 ms 11 ms 11 ms 2001:4860:0:1::2558
11 11 ms 9 ms 11 ms 2001:4860:0:5::2
12 9 ms 11 ms 10 ms 2001:4860::9:4001:383a
13 9 ms 13 ms 10 ms 2001:4860::9:4000:ea77
14 12 ms 13 ms 12 ms 2001:4860:0:1040::1
15 10 ms 10 ms 10 ms 2001:4860:0:1::ba5
16 11 ms 10 ms 9 ms sea09s17-in-x0e.1e100.net [2607:f8b0:400a:804::200e]

Trace complete.
 
#15 ·
Here is the output from ipconfig /all from the laptop ethernet adapter wired directly to the wall.

C:\WINDOWS\system32>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-E6-3D-40-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VirtualBox Host-Only Network 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-0D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek USB GbE Family Controller #2
Physical Address. . . . . . . . . : 00-E1-17-00-06-1D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:602:9900:e5f::baf0(Preferred)
Lease Obtained. . . . . . . . . . : Thursday, April 2, 2020 12:57:24 PM
Lease Expires . . . . . . . . . . : Thursday, April 9, 2020 12:57:24 PM
IPv6 Address. . . . . . . . . . . : 2601:602:9900:e5f:915e:8003:db0b:1f58(Preferred)
IPv6 Address. . . . . . . . . . . : 2601:602:9901:ba40:915e:8003:db0b:1f58(Preferred)
Temporary IPv6 Address. . . . . . : 2601:602:9900:e5f:84b1:8ff9:eee1:c93d(Preferred)
Temporary IPv6 Address. . . . . . : 2601:602:9901:ba40:84b1:8ff9:eee1:c93d(Preferred)
Link-local IPv6 Address . . . . . : fe80::915e:8003:db0b:1f58%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.39(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, April 2, 2020 1:09:28 PM
Lease Expires . . . . . . . . . . : Thursday, April 2, 2020 2:09:26 PM
Default Gateway . . . . . . . . . : fe80::c2c5:22ff:fef7:28dd%17
fe80::4a1d:70ff:fee2:55d%17
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 285270295
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-23-50-2E-94-65-9C-FA-96-0A
DNS Servers . . . . . . . . . . . : 2001:558:feed::1
2001:558:feed::2
75.75.75.75
75.75.76.76
2601:602:9900:e5f:4a1d:70ff:fee2:55d
2001:558:feed::1
2001:558:feed::2
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 5:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Private Internet Access Network Adapter
Physical Address. . . . . . . . . : 00-FF-D0-2B-FD-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
 
#16 ·
Well, the apartment complex is using LAN 192.168.0.x, so you definitely do not want to use that on your own router.

Otherwise, the mix of IPv4 and IPv6, especially with the IPv6 listed first for Gateway and DNS is beyond me. Meaning I don't know if that is perfectly good, problematic, or somewhere between. If/when you connect the router again see what the entire WAN IP configuration is (if you can get to the configuration/status pages).
 
#23 ·
I've been reluctant to suspect that your router is defective because I think that it is probably a good model. But I can't think of any other excuses.

You will have to make your own decision because I cannot be certain, but if it were me I'd be buying another router now (or asking for warranty service if it is new enough).

If you have an old router that still works as a router (but maybe the Wi-Fi is outdated or some other deficiency) I have another suggestion before buying.
 
#26 ·
Pretty sure that you reset the router to factory defaults. That should have fixed any software corruption so I doubt that any alternate firmware would help.

James's advice for a firmware update, if available, is excellent. Certainly try that before Tomato or DD-WRT.

But if we are correct about the router being defective it's most likely hardware.
 
#27 ·
More progress.

I put the router into "Access Point" mode, changed my adapter settings to work with IPv6, and manually entered DNS servers for IPv4 and IPv6 and I had some DNS issues at first, perhaps due to some caching, but I think it's stabilized!

Now, I don't know how to get my android devices going.

Not sure if my router is on the fritz or what, but it's probably worth grabbing another one off Amazon and seeing if a new one helps.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top