What's taking so long to resolve?

[DrBaker]

Greetings!

I have a really strange problem with my computer.
Essentially, it appears to be taking anywhere from 10 to 25 seconds (and sometimes it times out) to resolve a webpage.

For example, when I go to www.google.com, or www.techsupportalert.com, it hangs at the "Connected to URL..." or the "Waiting for URL to reply..." status bar message in whatever browser I use (tried IE9 and Firefox 8.0.1)

When it finally "resolves" or connects or completes the handshake (don't know the technical term), it seems to load the webpage fairly quickly. For example, Youtube videos will stream properly once they finally start downloading. I can download at over 15 Mbps, and the ping time on speedtest.shaw.ca is 46ms... But it takes literally half a minute to actually make that initial connection to start the speedtest...

Sites like Paypal don't even work, I think it's a security measure on their servers which protects against timeout attacks (totally winging this guess, so if that doesn't make sense to you, it's probably because it doesn't make sense at all)...

Now...

Details: What changed?
Shaw came and upgraded the Internet and installed a new cable modem/wireless router. Ever since, this has been happening.

It ONLY happens on my Windows 7 x64 system which is plugged in with a hard wire. I also tried a USB wireless dongle, and the same symptoms occurred.

My Android phone, my iPod touch, a friend's iPad, my laptop, and my other Windows XP computer all work blazingly fast, just like you'd expect them to.

It's only my PC. Tried booting up in Safe mode and had the same problem.

Just grasping at straws here looking for anywhere to even begin looking. Even some software that could diagnose the hangup...

Thank you very much for reading

[kendall.a]

I am no expert in this area, but since it appears tied to your Windows 7 computer, I wonder if it's not a dns issue?

I would download DNS Benchmark and run it. It can be found here:

http://www.grc.com/dns/benchmark.htm

Please read the entire page for directions and suggestions. I'm curious to hear your results.

[Remah]

I agree with Kendall. You have a DNS configuration problem because of the new router. You will probably have to update your laptop DNS configuration to point to the router as your DNS resolver.

Check out this article How to change DNS server

[Concerned User]

This might be a stupid question,but here goes:

Since you're on Windows 64 bit, could there be some kind of problem with the network/router/any other drivers? Do you have a Windows 7 32 bit installation to check out the net connection?

[DrBaker]

Originally Posted by kendall

... I would download DNS Benchmark and run it. ... I'm curious to hear your results.

Interestingly, although I'm not sure what unit these results are actually measured in (I'm going to assume it's seconds), the #'s seem quite low... Certainly not indicative of having to wait more than 10-15 seconds...

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

64. 59.184. 15 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.012 | 0.015 | 0.023 | 0.002 | 100.0 |
+ Uncached Name | 0.039 | 0.114 | 0.377 | 0.077 | 100.0 |
+ DotCom Lookup | 0.053 | 0.060 | 0.073 | 0.004 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
nsc2.ar.ed.shawcable.net
Shaw Communications


64. 59.184. 13 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.013 | 0.017 | 0.025 | 0.003 | 100.0 |
+ Uncached Name | 0.039 | 0.108 | 0.254 | 0.068 | 100.0 |
+ DotCom Lookup | 0.050 | 0.060 | 0.076 | 0.005 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
nsc1.ar.ed.shawcable.net
Shaw Communications


64. 59.190.242 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.014 | 0.017 | 0.025 | 0.002 | 100.0 |
+ Uncached Name | 0.045 | 0.118 | 0.299 | 0.069 | 100.0 |
+ DotCom Lookup | 0.054 | 0.062 | 0.079 | 0.006 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
nsc1.we.ed.shawcable.net
Shaw Communications


66. 93. 87. 2 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.030 | 0.033 | 0.039 | 0.002 | 100.0 |
- Uncached Name | 0.032 | 0.109 | 0.257 | 0.066 | 100.0 |
- DotCom Lookup | 0.036 | 0.130 | 0.357 | 0.072 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
dns.sea1.speakeasy.net
Speakeasy


24.113. 32. 30 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.031 | 0.035 | 0.046 | 0.003 | 100.0 |
- Uncached Name | 0.035 | 0.093 | 0.241 | 0.062 | 100.0 |
- DotCom Lookup | 0.037 | 0.095 | 0.294 | 0.058 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
ns2.wavecable.com
Wave Broadband


216.231. 41. 2 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.029 | 0.035 | 0.043 | 0.003 | 100.0 |
- Uncached Name | 0.034 | 0.118 | 0.523 | 0.089 | 100.0 |
- DotCom Lookup | 0.036 | 0.116 | 0.228 | 0.052 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
ns-legacy.speakeasy.net
Speakeasy


24.113. 32. 29 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.033 | 0.036 | 0.044 | 0.003 | 100.0 |
- Uncached Name | 0.037 | 0.105 | 0.331 | 0.068 | 100.0 |
- DotCom Lookup | 0.037 | 0.099 | 0.222 | 0.059 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
ns1.wavecable.com
Wave Broadband


8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.038 | 0.042 | 0.056 | 0.004 | 100.0 |
- Uncached Name | 0.041 | 0.102 | 0.318 | 0.069 | 100.0 |
- DotCom Lookup | 0.060 | 0.116 | 0.226 | 0.042 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
google-public-dns-b.google.com
Google Incorporated


8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.038 | 0.043 | 0.051 | 0.003 | 100.0 |
- Uncached Name | 0.040 | 0.106 | 0.374 | 0.078 | 100.0 |
- DotCom Lookup | 0.063 | 0.115 | 0.221 | 0.047 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
google-public-dns-a.google.com
Google Incorporated


156.154. 71. 22 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.049 | 0.053 | 0.064 | 0.003 | 100.0 |
- Uncached Name | 0.051 | 0.119 | 0.343 | 0.071 | 100.0 |
- DotCom Lookup | 0.051 | 0.098 | 0.137 | 0.027 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
··· no official Internet DNS name ···
NEUSTAR

[kendall.a]

The top 2 are the fastest dns servers for you. The remainder of that website should tell you how to change your dns settings for your computer.

I would suggest starting with your computer. Let us know what happens. If that doesn't work or show a marked improvement, then you'll have to change the router dns settings.

[Remah]

Originally Posted by Concerned User

This might be a stupid question,but here goes:

Since you're on Windows 64 bit, could there be some kind of problem with the network/router/any other drivers? Do you have a Windows 7 32 bit installation to check out the net connection?

It is unlikely as the problem began with the new router install.

Originally Posted by DrBaker

Greetings!

Details: What changed?
Shaw came and upgraded the Internet and installed a new cable modem/wireless router. Ever since, this has been happening.

It ONLY happens on my Windows 7 x64 system which is plugged in with a hard wire. I also tried a USB wireless dongle, and the same symptoms occurred.

My Android phone, my iPod touch, a friend's iPad, my laptop, and my other Windows XP computer all work blazingly fast, just like you'd expect them to.

It's only my PC. Tried booting up in Safe mode and had the same problem

The most likely reason is that the Windows 7 PC DNS is configured differently to the other devices which do not appear to use the router as DNS resolver. There are several possible causes including the following:
The DNS caches on the Windows 7 PC might need to be cleared so there are no leftover issues from the old DNS configuration.
If the PC DNS was using the old router as the DNS resolver then the old router address might be different to the new one. Changing the Windows DNS resolver to match the router IP should fix it.
If the router DNS resolver is configured incorrectly pointing it to Shaw's DNS resolvers should fix it.
If the router DNS resolving software has a problem then the configuration may be correct but the router firmware needs an upgrade/reinstall.

Whatever the cause of the problem it is worth having diversity in the DNS resolvers:
At least one from your ISP.
At least one public resolver not from your ISP e.g. Google.

[DrBaker]

The most likely reason is that the Windows 7 PC DNS is configured differently to the other devices which do not appear to use the router as DNS resolver.

All devices in the house were using "default" DNS settings, including my problem PC.
--

The DNS caches on the Windows 7 PC might need to be cleared so there are no leftover issues from the old DNS configuration.

Tried this via an "ipconfig /flushdns" instruction
--

If the PC DNS was using the old router as the DNS resolver then the old router address might be different to the new one. Changing the Windows DNS resolver to match the router IP should fix it.

Not applicable as I didn't have it set up that way.
--

If the router DNS resolver is configured incorrectly pointing it to Shaw's DNS resolvers should fix it.
If the router DNS resolving software has a problem then the configuration may be correct but the router firmware needs an upgrade/reinstall.

The router isn't likely the issue because my PC is the only one having issues.
--

Whatever the cause of the problem it is worth having diversity in the DNS resolvers:
At least one from your ISP.
At least one public resolver not from your ISP e.g. Google.

Thanks for the idea. I tried this, and it didn't fix it. I tried using only Google DNS, and it didn't fix it. I tried setting to 192.168.0.1, and it didn't work at all. I tried stuffing a peanut butter and jam sandwhich in the little Ethernet Port at the back of the computer, and it seemed to help. Not with the PC problem, but with my frustration levels.

Thank you for all the ideas, however I still haven't beat this... I even tried plugging my old router in to the new modem, and then connecting my PC to that router.. Same problem.

[Remah]

Originally Posted by DrBaker

All devices in the house were using "default" DNS settings, including my problem PC.

I assume that you mean that your PC's TCP/IP v4 properties are set to:
"Obtain DNS server address automatically"

Originally Posted by DrBaker

I tried using only Google DNS, and it didn't fix it. I tried setting to 192.168.0.1, and it didn't work at all.

I assume that 192.168.0.1 is your router IP address.

You've said that you used a wireless adapter so it is unlikely to be a driver issue with two different adapters.

If you've made not changes to your Firewall or other network security software (e.g. anti-virus) they are unlikely to be the source.

Here's a couple more options.

1. Run CCleaner and clear the:
Windows DNS cache
each web browser's Internet cache

2. In your web browser did you try to enter a valid IP address for a site was previously slow to load e.g. 72.52.134.16 for this site. If IP address is slow to find then it is not just a DNS issue.

It gets more complicated after this. There are utilities that automate testing but off-hand I can't remember any names.

Manual checks (like 2. above) can be done using command line utilities that include PING, IPCONFIG, NSLOOKUP and TRACERT.

Here's some examples checking there is no problem reaching the DNS server. If there is no problem then try some manual DNS queries using NSLOOKUP.

D:\Users\XXXX>PING 64.59.184.15

Pinging 64.59.184.15 with 32 bytes of data:
Reply from 64.59.184.15: bytes=32 time=213ms TTL=52
Reply from 64.59.184.15: bytes=32 time=214ms TTL=52
Reply from 64.59.184.15: bytes=32 time=213ms TTL=52
Reply from 64.59.184.15: bytes=32 time=214ms TTL=52

Ping statistics for 64.59.184.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 214ms, Average = 213ms

D:\Users\XXXX>nslookup 64.59.184.15
Server: ns1.acld.clix.net.nz
Address: 203.97.78.43

Name: nsc2.ar.ed.shawcable.net
Address: 64.59.184.15

D:\Users\XXXX>tracert 64.59.184.15

Tracing route to nsc2.ar.ed.shawcable.net [64.59.184.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms MYROUTER [192.168.1.1]
2 * * * Request timed out.
3 12 ms 18 ms 11 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101
.61.124]
4 18 ms 19 ms 18 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 20 ms 29 ms 22 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
50.251]
6 21 ms 18 ms 21 ms 203.167.233.10
7 149 ms 146 ms 147 ms i-0-0-4-1.tlot-core01.bx.reach.com [202.84.142.1
06]
8 157 ms 158 ms 167 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.140.9
0]
9 155 ms 157 ms 156 ms i-3-2.paix01.bi.reach.com [202.84.251.38]
10 191 ms 194 ms 191 ms 198.32.176.46
11 211 ms 202 ms 203 ms 66.163.69.193
12 208 ms 207 ms 207 ms 66.163.78.13
13 212 ms 212 ms 212 ms nsc2.ar.ed.shawcable.net [64.59.184.15]

Trace complete.

Manual DNS query for Youtube

D:\Users\MA>nslookup youtube.com
Server: ns1.acld.clix.net.nz
Address: 203.97.78.43

Non-authoritative answer:
Name: youtube.com
Addresses: 74.125.237.101
74.125.237.102
74.125.237.103
74.125.237.104
74.125.237.105
74.125.237.106
74.125.237.107
74.125.237.108
74.125.237.109
74.125.237.110
74.125.237.111
74.125.237.96
74.125.237.97
74.125.237.98
74.125.237.99
74.125.237.100

[crank]

This is a long shot, but is it possible you have a proxy setting turned on somewhere, maybe HotShield or something?

Try going to http://www.iptools.com/ , look to upper-right where your IP from your ISP will be displayed, and see if all your PCs say the same thing