Site not loading

[El Jacko]

For some strange reason, none of the Learnnavi sites (with the exception of the Wiki) will load properly on my home network. Currently, the only way I can get round it is via a US-based proxy server.

Anyone else having this?

[G.Sully]

Here its normal

Maybe its your flash player of your navigator

[El Jacko]

Tried both of those, still no luck. I think its the network, nothing on my home internet (i.e. phones, consoles, etc) will connect to LN.

[Kerame Pxel Nume]

Tried both of those, still no luck. I think its the network, nothing on my home internet (i.e. phones, consoles, etc) will connect to LN.

Did you check the following:

• Do the hostnames resolve properly? If not: Check DNS settings of your router and all connected machines
• Do the LN hosts answer to ICMP Echo aka ping?
• If ping doesn't work test using traceroute if the problem is somewhere between your ISP and LN
• Last but not least check if there are any proxy servers inbetween, which could be borked

[kxanì tsamsiyu]

Yes i was going to recommend doing these.

• Do the hostnames resolve properly? If not: Check DNS settings of your router and all connected machines
  
• Do the LN hosts answer to ICMP Echo aka ping?

sorry i cant help more but im pretty tired, my minds wandering.

[Hikyuuri]

I would try a ping and a trace route.

If you don't know how to do these, heres what you do:

1. Open Command Prompt.  In Windows Vista and 7, type "cmd" (without the ") in the little search bar in the start menu and hit enter.  This will bring up the Command Prompt.  In XP, click start, all programs, accessories, and Command Prompt should be somewhere in there.
2. In the Command Prompt, type "Ping www.learnnavi.org" (again, without the ").  Hit enter.  It should attempt 4 pings.  If the pings are successful, it should appear something like this:

Spoiler

C:\Users\Alex>ping www.learnnavi.org

Pinging learnnavi.org [173.201.0.1] with 32 bytes of data:
Reply from 173.201.0.1: bytes=32 time=83ms TTL=44
Reply from 173.201.0.1: bytes=32 time=83ms TTL=44
Reply from 173.201.0.1: bytes=32 time=87ms TTL=44
Reply from 173.201.0.1: bytes=32 time=83ms TTL=44

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

If the pings fail, it will look something like this:

Spoiler

C:\Users\Alex>ping www.learnnavi.org

Pinging learnnavi.org [173.201.0.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.201.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

3.  If the Ping is successful, I'm not sure what the problem is.  If the Ping fails, continue to step 4.
4.  Type "tracert www.learnnavi.org" (again, without the ") and hit enter.  This will trace the route through the internet your computer uses to get to LearnNavi.org.  It will log every "hop" (internet device) that your connection goes through to get to the LearnNavi server.  It should look something like this:

Spoiler

Tracing route to LearnNavi.org [173.201.0.1] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  144.13.218.5
  2    <1 ms    <1 ms    <1 ms  144.13.105.77
  3     1 ms    <1 ms    <1 ms  144.13.105.52
  4     1 ms     1 ms    <1 ms  144.13.105.40
  5     1 ms     1 ms     1 ms  144.13.6.254
  6     8 ms     5 ms     5 ms  r-uwmadison-isp-xe-0-0-0-3937.wiscnet.net [140.189.8.93]
  7     8 ms     8 ms    11 ms  ge-2-0-0-2041.rtr.chin.net.internet2.edu [205.213.118.10]
  8    11 ms    11 ms    18 ms  te-8-1-100-10G.ar3.CHI2.gblx.net [64.208.110.37]
  9    17 ms    17 ms    78 ms  64.209.110.218
10    78 ms    78 ms    78 ms  64.209.110.218
11    82 ms    82 ms    82 ms  ip-208-109-112-153.ip.secureserver.net [208.109.112.153]
12    76 ms    82 ms    81 ms  ip-208-109-112-142.ip.secureserver.net [208.109.112.142]
13    75 ms    76 ms    76 ms  ip-216-69-188-77.ip.secureserver.net [216.69.188.77]
14    76 ms    75 ms   289 ms  ip-208-109-112-2.ip.secureserver.net [208.109.112.2]
15    82 ms    78 ms    77 ms  ip-216-69-188-126.ip.secureserver.net [216.69.188.126]
16    82 ms    82 ms    82 ms  p3nlhg39c072.shr.prod.phx3.secureserver.net [173.201.0.1]

Trace complete.

If it fails, it will look something like this:

Spoiler

Tracing route to LearnNavi.org [173.201.0.1] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  144.13.218.5
  2    <1 ms    <1 ms    <1 ms  144.13.105.77
  3     1 ms    <1 ms    <1 ms  144.13.105.52
  4     1 ms     1 ms    <1 ms  144.13.105.40
  5     1 ms     1 ms     1 ms  144.13.6.254
  6     8 ms     5 ms     5 ms  r-uwmadison-isp-xe-0-0-0-3937.wiscnet.net [140.189.8.93]
  7     8 ms     8 ms    11 ms  ge-2-0-0-2041.rtr.chin.net.internet2.edu [205.213.118.10]
  8    11 ms    11 ms    18 ms  te-8-1-100-10G.ar3.CHI2.gblx.net [64.208.110.37]
  9    17 ms    17 ms    78 ms  64.209.110.218
10    78 ms    78 ms    78 ms  64.209.110.218
11    82 ms    82 ms    82 ms  ip-208-109-112-153.ip.secureserver.net [208.109.112.153]
12    76 ms    82 ms    81 ms  ip-208-109-112-142.ip.secureserver.net [208.109.112.142]
13    75 ms    76 ms    76 ms  ip-216-69-188-77.ip.secureserver.net [216.69.188.77]
14    *              *            *   
15    *              *            *
16    *              *            *
---------------------------------
29    *              *            *
30    *              *            *

Trace complete.

If the trace route looks like the first one, then again, it should work as that shows that your computer is able to communicate with every internet device (hop) on its path to LearnNavi.org.  If it looks like the lower one (where after a certain device it starts to time out (thats what the * represents), you have a break somewhere in the communication path to the LearnNavi server.  Note that the "-------------------" line in the last test is to represent that the Trace Route will continue to produce "*" until it gets to hop 30.

Let us know what you learn from these tests so we can help you further.

[El Jacko]

Well, I've done the tests you said. Ping test failed spectacularly, but the traceroute managed to get somewhere.

Spoiler

Tracing route to learnnavi.org [173.201.0.1]
over a maximum of 30 hops:

1        4 ms        1 ms        1 ms    www.routerlogin.com [192.***.*.*]
2       21 ms      22 ms      21 ms    sgrs-lns-01-lo0.onetel.net.uk [212.67.121.44]
3       20 ms      22 ms      21 ms    212.67.125.252
4       22 ms      21 ms      22 ms    212.67.120.82
5          *            *            *       Request timed out.
6          *         30 ms         *       62.24.251.42
7          *            *            *       Request timed out

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

21        *             *            *       Request timed out
22        *             *        164 ms    p3nlhg39c072.shr.prod.phx3.secureserver.net  [173.201.0.1]

Trace complete.

[Kerame Pxel Nume]

Spoiler

Tracing route to learnnavi.org [173.201.0.1]
over a maximum of 30 hops:

1        4 ms        1 ms        1 ms    www.routerlogin.com [192.***.*.*]
2       21 ms      22 ms      21 ms    sgrs-lns-01-lo0.onetel.net.uk [212.67.121.44]
3       20 ms      22 ms      21 ms    212.67.125.252
4       22 ms      21 ms      22 ms    212.67.120.82
5          *            *            *       Request timed out.
6          *         30 ms         *       62.24.251.42
7          *            *            *       Request timed out

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

21        *             *            *       Request timed out
22        *             *        164 ms    p3nlhg39c072.shr.prod.phx3.secureserver.net  [173.201.0.1]

Trace complete.

That trace shows, that it's likely not a problem on your side. The packets drop two hops after your ISP's dial-in node, but apparently still within the ISPs network. There's one thing you could try: Reduce the MTU, it's somewhere on the advanced settings of the router. Try setting it to something like 1400. Then check packet filter (aka firewall) settings of the router, if nothing is blockes/filtered.

If nothing of that helps, the best course of action would be to contact the ISP, get through the level 1 support directly to the tech guys, and tell them, they got a problem with some of their routers.

[Hikyuuri]

Yeah, that appears to still be inside the ISPs network.  They may have a problem with one of their routers.

Did it ever work on your home connection?  Or has it always been like this?

[El Jacko]

Did it ever work on your home connection?  Or has it always been like this?

Used to work, packed up about 4 days ago.

[Hikyuuri]

I would give your ISP a call and explain the situation to them.  Explain to them that the webside used to work, but a few days ago something changed and prevents it from working.

Best of luck to you!