Stalling Internet. Can ping 8.8.8.8 but not www.google.com

Factual Questions
1

The Internet on my Win 7 PC keeps stalling, as if it’s waiting for something to time out before loading a site. Once sites start to load, it’s ok for a little while, then it’s back to stalling again.

It’s not a whole-house or router issue. Other PCs on the network have no problem, and I have no problem connecting/streaming from other PCs on the network (from the problem PC).

It’s not browser-related. It happens on Firefox, Chrome and Explorer.

MalwareBytes and MSSE scans are clean.

No triangles in device manager.

I have a virtual machine on the problem PC, but the problem does not affect the virtual machine — just the host computer (the problem also exists when the virtual machine is not running).

When the Internet stalls, I can open two command-prompt windows. In one I ping www.google.com (or other website), on the other I ping 8.8.8.8. The window pinging Google hangs for a while, then returns pings as normal. The window pinging the DNS server returns ping results right away.

In Local Area Connection properties,IPv6 is unchecked. IPv4 uses the 8.8.8.8 and 8.8.4.4 DNS servers (I’ve also tried it with “obtain DNS server address automatically”).

I tried ipconfig with /flushdns, /release and /renew, but the problem persists.

I’m out of ideas to diagnose or fix. Where do I check next?

2

Is this the only computer on your network that cannot use IPv6?

3

That you can ping by number but not by name points to a DNS issue. Run IPCONFIG with the /ALL switch and post the results.

4

By any chance, do you have multiple gateways configured? The delay might be coming from the machine trying to send out dns and arp type stuff out through the wrong gateway and having those timeout before it tries the correct gateway.

5

I believe the other computers use IPv6 by default. The problem I’m having existed when the machine had IPv6 enabled. In Googling for possible causes/fixes, I saw a few suggestions that it might cause trouble, hence I unchecked it. I haven’t re-checked it yet. Again, the problem predated my unchecking the box.

Here are the results of ipconfig /all. I’m just outside my are of tech knowledge (not that it’s all that broad in the first place), so don’t know what to look for within. It does seem to include multiple gateways, but I don’t know how to check for a conflict.

(I can’t figure out how to get the results to display readably. I’ve spent time replacing paragraph marks with line breaks, adding spacing, etc., but I can’t get each line separately. If anyone knows how to do this I’ll repost in a better format)



Windows IP Configuration   

Host Name . . . . . . . . . . . . : Yask   

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-V
   Physical Address. . . . . . . . . : BC-EE-7B-98-BC-C4
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.98(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, February 21, 2018 11:59:34 AM
   Lease Expires . . . . . . . . . . : Friday, February 23, 2018 10:51:24 AM
   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

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-A3-9A-C4-D4
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c40b:aa67:20dc:7b1b%24(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.61.10.6(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Lease Obtained. . . . . . . . . . : Thursday, February 22, 2018 1:59:22 PM
   Lease Expires . . . . . . . . . . : Friday, February 22, 2019 1:59:22 PM
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 10.61.10.5
   DHCPv6 IAID . . . . . . . . . . . : 503381923
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-BB-89-91-90-E6-BA-0E-72-69

   DNS Servers . . . . . . . . . . . : 209.222.18.222
                                       209.222.18.218
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 0A-00-27-00-00-14
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::49a1:553:4995:9646%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 587726887
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-BB-89-91-90-E6-BA-0E-72-69

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
	
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

Tunnel adapter isatap.{A39AC4D4-440D-439E-81B9-5BB4179F0834}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{BBBF4A82-2DBF-489F-9F16-B0FE0296ABC1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{D61F4B2D-4DF7-4479-897A-B2A8927C7201}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
6

Is the time and date setting correct for your timezone?

I know that sounds silly, but date/time settings are critical to the way some network protocols work - if they’re adrift, it can cause wildly intermittent packet loss.

7

I believe the clock, time and date settings are correct. We use this computer to set clocks, so I semi-regularly go to clock>internet time>set time.

(apologies if this is a double post. I know I typed it at least once but can’t see it posted here yet.)

8

It looks like you’re connected to a VPN. Does the problem happen both when you’re connected to the VPN and when you’re not?

The problem you had with linefeeds in the code block is a bug in this bulletin board’s software. It’s existed for a while now and is quite annoying.

9

(All these are as admin, of course.)

How fast are the following commands, in terms of response time?

ping www.google.com

(How fast does the name resolves, not the actual ping time.)

nslookup www.google.com

They should be nearly instantaneous.

To clear dns cache:

ipconfig /flushdns

And then there’s stuff to reset winsock and other stuff:

netsh int ipv4 reset

netsh int ip reset c:\resetlog.txt

(You’ll have to reconfig stuff after this. Use /? for more parameters if you have more than 1 interface, etc.)

Guess how I know this right now, guess.

10

The problem is independent of using the VPN. It does not run at startup per its settings, but I haven’t dug deeper to see if it’s doing anything anyway (it’s a paid Private Internet Access subscription). The problem occurs after a restart and well before I start PIA or connect to its servers.

Of course it’s not acting up now that I’m trying to test things (I think intermittent computer problems are quantumly entangled with intermittent noises in a car). But I do know that other ipconfig /flushdns etc. commands were run with a basic command prompt, not one started as admin.
Before I run the rest commands, what am I going to have to reconfigure? Is there a way to save current settings, or am I resetting because one of those settings is out of whack?

My guess as to why you know this right now:
It was the duck, in the ballroom, with a netsock.

11

When the VPN isn’t running, is the adapter labeled “Tap Windows Adapter V9” still there?

On my system, when I start my VPN I get a new adapter that shows up, but this adapter goes away once I shut down the VPN (we use Barracuda where I work, so the details my my VPN will be different than yours). If your VPN adapter is hanging around for some reason, your computer might be trying to send dns requests through it.

What happens if you ping 209.222.18.222 or 209.222.18.218?

12

I think your problem is linked to the TAP-Windows adapter. Neither DNS address responds for me. Can you disable it entirely?

13

I think the TAP-Windows Adapter V9 is the VPN. When I exited from the VPN (disconnected and selected exit on the system tray icon), it changed to “network cable unplugged” and had a red x next to it. When I restarted the VPN client, the x disappeared, and the unplugged message with to enabled, Identifyng and such. To get it to x-out and say the cable is unplugged, all I need to do is disconnect the VPN from their menu.
Again, it’s hard to say with an intermittent problem, but it seemed as if they fared better than pings to Google or a written domain. Here’s a sample of the results:

I’ll repeat it when the issue is more pronounced.