LDS.org not working inside firewall

[rickk]

So do we (or the GSC via the firewall) have a way to track the traffic requests as a machine is trying to load www.lds.org? That might be very helpful if we can look at all of the DNS requests and see if any of those are timing out or getting bad IP addresses returned.

[russellhltn]

So do we (or the GSC via the firewall) have a way to track the traffic requests as a machine is trying to load http://www.lds.org? That might be very helpful if we can look at all of the DNS requests and see if any of those are timing out or getting bad IP addresses returned.

I'm pretty sure that the web browser has some tools for that, but that's a little over my head.

[rickk]

I'm pretty sure that the web browser has some tools for that, but that's a little over my head.

Mine too. I was hoping that maybe you had some more experience in that area. Sounds like google is my friend and I need to do some looking around.

[russellhltn]

I'd try encountering the error and then poking around. See if it will give up details.

[tlhackett]

Let's have those that are having problems do some troubleshooting. Post your results so that we can try to make sense of this.

If your site is affected, run a trace route and let it finish (ex: tracert http://www.lds.org and tracert lds.org) from both behind the firewall and from the modem. I believe it could take up to 30 hops before it finishes if requests time out. Correct me if I'm wrong. Are there any differences?

Try assigning our DNS servers statically in your computer (8.34.34.92 and 8.35.35.92) and clear the DNS cache (ipconfig /flushdns) and any cache and cookies in your browser. Can you get to lds.org connected directly to the modem? If you run a trace route again with this set up, is it any different than before?

[tlhackett]

I'm pretty sure that the web browser has some tools for that, but that's a little over my head.

Also if you have and know how to use any browser tools or extensions/plugins that could help, let us know what you come up with. I'm a GSC representative and we need as much help as we can get to diagnose the issue and what can be done to fix it.

[rickk]

I'm a GSC representative and we need as much help as we can get to diagnose the issue and what can be done to fix it.

So if the GSC is aware of this, does it still make sense for me to call in and enter a ticket? It sounds like I won't get a real resolution since you don't know what is happening yet.

I did run tracert from behind the firewall - haven't yet bypassed the modem. The route to www.lds.org gets to a comcast device and stalls. The others complete. I will put the results in another post...

Rick

[rickk]

Results of the tracert to www.lds.org:

Server: 10.68.76.63

Tracing route to e5298.g.akamaiedge.net [23.203.225.116]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.108.1
2 * * * Request timed out.
3 7 ms 9 ms 9 ms xe-0-2-3-0-sur03.vancouver.wa.bverton.comcast.net [68.85.150.33]
4 9 ms 16 ms 8 ms ae-2-0-sur04.vancouver.wa.bverton.comcast.net [68.87.222.166]
5 10 ms 10 ms 8 ms ae-51-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.161]
6 18 ms 13 ms 13 ms he-2-0-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.90.201]
7 29 ms 27 ms 29 ms he-0-12-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.86.230]
8 28 ms 27 ms 27 ms he-0-12-0-0-pe03.11greatoaks.ca.ibone.comcast.net [68.86.82.66]
9 28 ms 27 ms 27 ms 50-248-117-126-static.hfc.comcastbusiness.net [50.248.117.126]
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.

[rickk]

And to compare, the results going to cdol.lds.org:

Tracing route to cdol.lds.org [216.49.178.28]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.108.1
2 * * * Request timed out.
3 9 ms 9 ms 7 ms xe-0-2-3-0-sur03.vancouver.wa.bverton.comcast.net [68.85.150.33]
4 10 ms 9 ms 9 ms ae-2-0-sur04.vancouver.wa.bverton.comcast.net [68.87.222.166]
5 9 ms 13 ms 10 ms ae-51-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.161]
6 94 ms 16 ms 15 ms he-2-2-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.95.97]
7 28 ms 28 ms 26 ms he-0-14-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.202]
8 52 ms 51 ms 51 ms he-0-14-0-0-ar02.sandy.ut.utah.comcast.net [68.86.95.226]
9 53 ms 51 ms 51 ms te-0-7-0-7-sur01.orem.ut.utah.comcast.net [68.86.180.98]
10 49 ms 49 ms 49 ms 107-1-212-14-ip-static.hfc.comcastbusiness.net [107.1.212.14]
11 48 ms 45 ms 45 ms te-2-2-pvufw-a.ldschurch.org [216.49.191.53]
12 * * * Request timed out.
13 44 ms 43 ms 45 ms 216.49.178.28

Trace complete.

[rickk]

And www.foxnews.com:

Tracing route to a20.g.akamai.net [23.61.194.193]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.108.1
2 * * * Request timed out.
3 10 ms 8 ms 9 ms xe-0-2-3-0-sur04.vancouver.wa.bverton.comcast.net [68.85.150.37]
4 8 ms 9 ms 9 ms ae-51-0-ar03.troutdale.or.bverton.comcast.net [68.87.222.161]
5 17 ms 14 ms 17 ms he-2-2-0-0-10-cr01.seattle.wa.ibone.comcast.net [68.86.95.97]
6 28 ms 27 ms 27 ms he-0-14-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.202]
7 28 ms 27 ms 27 ms he-0-12-0-1-pe03.11greatoaks.ca.ibone.comcast.net [68.86.83.130]
8 28 ms 27 ms 27 ms 50-248-117-126-static.hfc.comcastbusiness.net [50.248.117.126]
9 29 ms 30 ms 28 ms a23-61-194-193.deploy.static.akamaitechnologies.com [23.61.194.193]

Trace complete.