Can't access enworld from home

[Matafuego]

Hello guys:

I don't know what is going on.
Whenever I want to access enworld from my home connection it just doesn't work. It timesout, and tells me that I can't access the page.
At work, on the other hand, it works perfectly.

I think my work connection and my home connection have different ISP providers. Could my ISP be the problem?
Could it be some sort of DNS problem?

Can anybody help me with this?

Thanks a lot!

Lucas

 

[IronWolf]

I assume all other web browsing on your home connection is working fine?

If so, open up a command prompt (go to Start, then Run and type cmd and hit enter). Once the command prompt is open type this:


ping www.enworld.org


then hit enter.

Do you get replies back or timeouts? Does it resolve to an IP address when you ping? If it does, what IP does it resolve to?

 

[Artur Hawkwing]

I have a similar issue both at home and at work on occasion. Doesn't always timeout, but it can take as long as 45 seconds for a page to load. If it times out, just refreshing the browser usually results in the desired page.

I'd also look at what kind of connections you have. Even the difference in 'basic' cable modem at home and 'basic' office cable modem (like with my situation) can be vast.

I've also noticed that sometimes my browser acts like a goober if I've been running a lot of Flash stuff. A restart of the machine usually deals with that.

Not sure if any of that helps, but, at least you know you aren't alone.

 

[LightPhoenix]

ping EN World: Your Daily RPG Magazine: Your Daily RPG Magazine

I'm guessing the board automatically adds the name of website, but that should be:

ping www.enworld.org

 

[IronWolf]

I'm guessing the board automatically adds the name of website, but that should be:

ping www.enworld.org

Doh! Thanks for catching that! Silly auto-parser!

 

[Matafuego]

I assume all other web browsing on your home connection is working fine?

If so, open up a command prompt (go to Start, then Run and type cmd and hit enter). Once the command prompt is open type this:


ping www.enworld.org


then hit enter.

Do you get replies back or timeouts? Does it resolve to an IP address when you ping? If it does, what IP does it resolve to?

My internet connection works perfectly. Enworld is the only site (that I know of) that I cannot access.

Ping gives me timeout, but it's resolving against the same address than it is at work ( 68.68.204.20) so DNS seems to be working fine.

Rebooting / Restarting / Killing my chrome/ie/ff won't help either.

I'm really lost here

Thank you very much for your ideas though

Should I contact my ISP and let them know this?
The weird thing is I do not know what the problem might be, I'm completely lost.

 

[IronWolf]

My internet connection works perfectly. Enworld is the only site (that I know of) that I cannot access.

Ping gives me timeout, but it's resolving against the same address than it is at work ( 68.68.204.20) so DNS seems to be working fine.

Rebooting / Restarting / Killing my chrome/ie/ff won't help either.

I'm really lost here

Thank you very much for your ideas though

Cool! Thanks for the additional information.

Should I contact my ISP and let them know this?
The weird thing is I do not know what the problem might be, I'm completely lost.

Do one more thing. Again from a command prompt, do:

tracert www.enworld.org

You will likely see some timeouts at the end of that command. I am most interested in the couple of entries before you see the timeouts. It will help tell us how far the traffic is getting before it disappears and possibly help identify where the problem is.

 

[Matafuego]

This is what I get:

Tracing route to EN World: Your Daily RPG Magazine: Your Daily RPG Magazine [68.68.204.20]
over a maximum of 30 hops:

1 10 ms 8 ms 10 ms cpe-190-55-124-1.telecentro-reversos.com.ar [190.55.124.1]
2 10 ms 9 ms 7 ms cpe-200-115-195-209.telecentro-reversos.com.ar [200.115.195.209]
3 * 30 ms * te4-4.baires3.bai.seabone.net [195.22.220.33]
4 146 ms 141 ms 143 ms te4-5.ccr01.mia03.atlas.cogentco.com [154.54.11.37]
5 150 ms 152 ms 152 ms te4-1.mag01.mia03.atlas.cogentco.com [154.54.47.182]
6 149 ms 172 ms 182 ms 38.104.94.2
7 903 ms 779 ms 607 ms FL-216.137.76.208-usmetrocom.com [208.76.137.216]
8 434 ms 390 ms 388 ms 63-247-144-153.t3com.net [63.247.144.153]
9 534 ms 825 ms 954 ms ftmy-core-sw1-vl2.t3com.net [63.247.144.10]
10 872 ms 719 ms 641 ms ftmy-ip-colo-01-g02.t3com.net [63.247.144.38]
11 * * * Request timed out.

And it's all timeouts from there

Thanks!

 

[IronWolf]

This is what I get:

Tracing route to EN World: Your Daily RPG Magazine: Your Daily RPG Magazine [68.68.204.20]
over a maximum of 30 hops:

1 10 ms 8 ms 10 ms cpe-190-55-124-1.telecentro-reversos.com.ar [190.55.124.1]
2 10 ms 9 ms 7 ms cpe-200-115-195-209.telecentro-reversos.com.ar [200.115.195.209]
3 * 30 ms * te4-4.baires3.bai.seabone.net [195.22.220.33]
4 146 ms 141 ms 143 ms te4-5.ccr01.mia03.atlas.cogentco.com [154.54.11.37]
5 150 ms 152 ms 152 ms te4-1.mag01.mia03.atlas.cogentco.com [154.54.47.182]
6 149 ms 172 ms 182 ms 38.104.94.2
7 903 ms 779 ms 607 ms FL-216.137.76.208-usmetrocom.com [208.76.137.216]
8 434 ms 390 ms 388 ms 63-247-144-153.t3com.net [63.247.144.153]
9 534 ms 825 ms 954 ms ftmy-core-sw1-vl2.t3com.net [63.247.144.10]
10 872 ms 719 ms 641 ms ftmy-ip-colo-01-g02.t3com.net [63.247.144.38]
11 * * * Request timed out.

And it's all timeouts from there

You're *almost* there - two more hops and you'd be set.

I suspect cyberstreet has implemented some overly aggressive filtering. I saw them do this before when I used to help out on the admin side of things.

Let's summon [MENTION=1]Morrus[/MENTION] and [MENTION=52905]darjr[/MENTION] and see if one of them can get cyberstreet to see if they are blocking traffic again. Could one of you guys check this out? Matafuego has his packets dropping quite near cyberstreet's network. We saw this a few years ago and it was indeed that cyberstreet was blocking traffic. The above tracert might be useful to cyberstreet if you want to provide it to them.

 

[darjr]

Looks like some issue at t3com from enworlds network perspective. I'll let cyberstreet know.