Download Woes

Chris Maunder

Hey Jeff, Can you trying doing a tracert www.codeproject.com to see where the bottleneck is? (only worry about the nodes up until peer1. Everything after that will timeout on purpose)

cheers Chris Maunder

Jeff Bowman

Here's what I got:

C:\Users\Work>tracert www.codeproject.com

Tracing route to www.codeproject.com [76.74.234.210]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 66 ms 66 ms 86 ms br1.grn.acsalaska.net [209.193.63.232]
3 139 ms 140 ms 135 ms ae8-2000-mx1.grn.acsalaska.net [63.140.116.220]
4 182 ms 192 ms 186 ms ae10-r2.nwc.acsalaska.net [63.140.116.68]
5 92 ms 90 ms 90 ms ae9-r2.sea.acsalaska.net [63.140.116.225]
6 92 ms 90 ms 89 ms sea-b2-link.telia.net [213.248.86.126]
7 208 ms 218 ms 203 ms chi-b23-link.ip.twelve99.net [62.115.117.49]
8 175 ms 212 ms 150 ms aptumtech-svc072773-ic360373.c.telia.net [62.115.175.229]
9 204 ms 230 ms 245 ms et-3-0-2.tor-fr709-dis-1.peer1.net [216.187.88.61]
10 203 ms 202 ms 228 ms tor-fr402-xe3-1.peer1.net [216.187.113.86]
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.

This is from my ISP's network that can reach your server but can't download the file. I called them to discuss their other network that can't reach your server at all, and the tech asked me to bypass the WatchGuard router there, temporarily plug a laptop directly into their switch and manually assign an IP from the range they've allocated. If after that I still can't connect, he suggested the possibility that you may be blocking a range of IPs that includes their range. Do you

Chris Maunder · Tracing route to www.codeproject.com [76.74.234.210] over a maximum of 30 hops:

We can't test anything downstream. My guess: someone or something is blocking us. Do you have any ad blockers installed (or uBlock?) They play absolute havoc with sites.

cheers Chris Maunder

Jeff Bowman

Chris Maunder wrote:

We can't test anything downstream

Sure, I understand. But if your network admins were intentionally blocking an IP range—for whatever reason—wouldn't you be able to find that out? My network: I use ABP, but I turned it off for CP. Same result (the download starts fine but then incoming packets halt at about 10% complete). I don't use an ad blocker at the other network. This is really odd, because page loads are just fine. I can download files from other articles lickety-split. It's just this one file from this one article. Thanks, Jeff Bowman Fairbanks, Alaska

Jeff Bowman

Chris Maunder wrote:

We can't test anything downstream

p.s. Not sure what you mean by downstream in this context.

jeron1 · Tracing route to www.codeproject.com [76.74.234.210] over a maximum of 30 hops:

Jeff Bowman wrote:

WatchGuard router

Interesting...within the last week CodeProject is blocked at work by the WatchGuard router, they claim that it is being detected as a botnet. I'll have to work on the boss to make the exception. :(

"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle

Chris Maunder

Sorry: I meant anything outside of our systems we can't test. We can ping / tracert from us to your ISP but that probably won't tell us much. Sounds like there's a block in there somewhere

cheers Chris Maunder

Chris Maunder

:doh: We'll ask our IT guys to dig in and see who they need to slap to get this sorted.

cheers Chris Maunder

Jeff Bowman

Chris Maunder wrote:

Sounds like there's a block in there somewhere

Yes, you're correct. Our WatchGuard firewall appliance was incorrectly blocking the site. Thanks to @jeron1 for assisting with that. Download attempts for the article's source code are still timing out, though. It starts off like a bull, traffic slows down to fits and starts for a bit, and then everything goes quiet. Thanks, Jeff Bowman Fairbanks, Alaska

Jeff Bowman

This was exactly the issue. I'm not sure why I didn't think to check for it, so your suggestion was very timely. I added an exception for `*.codeproject.com` and all was well. Thanks, Jeff Bowman Fairbanks, Alaska

jeron1

:thumbsup: Good to hear!

"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle

jeron1

I'm not sure what happened, I've used this site for years at work, then all of the sudden nothing but connection timeouts... Maybe a WatchGuard update botched things up, the fact that someone else had a similar issue seems too coincidental.

"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle