18 replies to this topic

[damian]

At first i thought OCC was down, but then after using the dfeojm (Down for everyone or just me) i guess i really cant get into the site.

If i use a proxy i can access it just fine though.

[Nerm]

Do you get an error message or just a blank page?

[wevsspot]

Are you trying to access from a work pc (i.e. company pc), school pc or a personal pc on your own network?

From the command prompt can you ping www.overclockersclub.com, and if so does the ping command go through or timeout?

[damian]

@Nerm - I get an error

The connection has timed out
The server at www.overclockersclub.com is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

@Wevsspot - On my own network. CMD Result - Request timed out (over and over again)


PS. Even if i disable my firewall, i still cant access the site

Edited by damian, 25 May 2011 - 07:23 AM.

[wevsspot]

Damian,

From command prompt run a trace route;

"tracert www.overclockersclub.com" without the quotations of course...............

Let see if we can determine at what hop it's failing.

[damian]

Alright, here we go.


1 * * * Request timed out.
2 14 ms 10 ms 9 ms gig2-1-5.lardtxhe-rtr1.stx.rr.com [24.170.64.41]

3 37 ms 19 ms 21 ms gig4-0-0.dllatxl3-rtr1.texas.rr.com [72.179.205.
116]
4 20 ms 21 ms 21 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
5 23 ms 21 ms 22 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
6 117 ms 214 ms 214 ms te9-4.mpd01.dfw03.atlas.cogentco.com [154.54.11.
49]
7 20 ms 21 ms 21 ms te2-4.mpd01.dfw01.atlas.cogentco.com [154.54.6.6
5]
8 34 ms 34 ms 31 ms te0-2-0-1.mpd22.mci01.atlas.cogentco.com [154.54
.5.158]
9 43 ms 44 ms 43 ms te0-1-0-2.mpd22.ord01.atlas.cogentco.com [154.54
.3.201]
10 46 ms 46 ms 47 ms te3-2.ccr01.sbn01.atlas.cogentco.com [154.54.25.
61]
11 50 ms 50 ms 50 ms te3-3.ccr01.ind01.atlas.cogentco.com [154.54.3.3
0]
12 56 ms 57 ms 74 ms te3-1.ccr01.cmh02.atlas.cogentco.com [154.54.24.
254]
13 59 ms 59 ms 63 ms 38.104.22.78
14 56 ms 53 ms 53 ms ten7-2.core-2.xlhost.com [206.222.25.134]
15 53 ms 54 ms 53 ms 9e.19.de.static.xlhost.com [206.222.25.158]
16 56 ms 53 ms 53 ms aa.84.b6.static.xlhost.com [207.182.132.170]

Trace complete.

[wevsspot]

are you behind a router or connected directly to a modem?

[wevsspot]

Either way, the first hop should be going from your PC to your router or modem. In your case it's timing out for some reason. Try a tracert again, but this time trace to something like www.google.com

[wevsspot]

Frankly, I think you've got a nasty intercepting your outbound traffic between your pc and the router or modem..........................

[wormy]

Do you use fasterfox? if so disable it when coming to OCC and see if that works. I had that problem once before and it was because of faster fox trying to many connections and the server not responding or rejecting because of that.

Edited by wormy, 25 May 2011 - 02:22 PM.

[damian]

I dont have that addon.

Any other ideas :/

[bishop245]

I agree with Wev I think you have something blocking you on your router or modem since you haven't said which you were behind. Did you try the tracert www.google.com like Wev asked, and did the first hop time out like here? Do you have access to your router setup, and does anybody else that may be blocking you on purpose? The are lots of other questions I am sure, but I aint that great with networking. If you answer a few of the newer questions it would help us help you.