the only person in the world who can't see

...this website. I believe that is me.

www.oaktecstore.com - can everyone pull up this website but me?

I've had the most frustrating chat session with Roadrunner. I seem to be the only person that cannot see this website. They can, other friends can, my clients can. I cannot, and haven't ever been able to (for at least 5 days, eliminating a server problem in my mind - especially since others can see it, and I have no problem pinging using dnsstuff.com either. I am pinging the right IP from my machine, but getting no response. Since dns stuff can ping, then this discredits roadrunners claim that perhaps they have their server set to not respond to ping)

I've cleared my cache, flushed my dns, disabled my firewall, connected the cable modem directly to the PC (to see if the problem was with the router). None of which cured the problem. The only thing Roadrunner have come up with is that "I need to contact a technician for repairs to my PC". They suggested the problem is spyware or virus, or problem with IE. I have scanned for viruses, spyware, and I restored the defaults in IE - even though I get the same problem with firefox. And my laptop can pull it up when connected to other networks, just not on my home connection. So I don't believe it's anything to do with my PC.

I think the problem is that the connection with that particular website is timing out. I figured that out by doing a tracert - but they (roadrunner) had no clue what to advise since the "problem is outside of their network".

Very Helpful.

Here's the tracert

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\unclechris>tracert www.oaktecstore.com

Tracing route to www.oaktecstore.com [67.15.74.129]
over a maximum of 30 hops:

1 7 ms 8 ms 8 ms 10.42.64.1
2 8 ms 6 ms 7 ms srp2-0.dytnoh1-rtr1.woh.rr.com [24.29.161.145]
3 21 ms 9 ms 9 ms son0-0-3.mtgmoh1-rtr0.columbus.rr.com [65.25.128
.241]
4 17 ms 17 ms 17 ms son0-1-3.ncntoh1-rtr0.neo.rr.com [65.25.128.245]

5 31 ms 28 ms 28 ms so-2-0-0-0.gar1.Chicago1.Level3.net [67.72.120.5
]
6 27 ms 27 ms 28 ms ae-13-51.car3.Chicago1.Level3.net [4.68.101.7]
7 27 ms 27 ms 28 ms ge-2-1-0.r02.chcgil06.us.bb.verio.net [129.250.9
.117]
8 27 ms 27 ms 28 ms p16-1-0-1.r20.chcgil06.us.bb.verio.net [129.250.
2.54]
9 59 ms 58 ms 57 ms p16-0-1-2.r20.dllstx09.us.bb.verio.net [129.250.
2.26]
10 66 ms 65 ms 65 ms p16-5-0-0.r02.hstntx01.us.bb.verio.net [129.250.
5.41]
11 68 ms 70 ms 67 ms ge-7.ev1.hstntx01.us.bb.verio.net [129.250.10.23
0]
12 69 ms 70 ms 69 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
13 69 ms 69 ms 70 ms gphou-66-98-240-107.ev1.net [66.98.240.107]
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 * *

Again, this is the ONLY website I'm having trouble with. Weird. Can anybody offer any suggestions on how to resolve this?
HELP?!! ANYONE??!!!
 
Doesn't work for me on Verizon DSL, in Texas

I have to say, that is the craziest route I have ever seen from here to Houston:

3 21 ms 18 ms 17 ms 130.81.36.52
4 17 ms 17 ms 17 ms 130.81.20.60
5 21 ms 18 ms 19 ms 130.81.19.13
6 42 ms 51 ms 41 ms 130.81.19.21
7 61 ms 59 ms 60 ms 130.81.19.34
8 60 ms 60 ms 59 ms 130.81.10.90
9 61 ms 61 ms 60 ms 130.81.15.42
10 75 ms 60 ms 60 ms so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]

11 75 ms 62 ms 61 ms so-4-0-0.mpr2.iad1.us.above.net [64.125.29.133]

12 75 ms 63 ms 61 ms so-6-0-0.cr2.dca2.us.above.net [64.125.27.210]
13 75 ms 61 ms 61 ms so-0-0-0.cr1.dca2.us.above.net [64.125.29.121]
14 71 ms 71 ms 72 ms so-5-1-0.mpr2.atl6.us.above.net [64.125.29.37]
15 72 ms 72 ms 72 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
16 109 ms 134 ms 203 ms so-4-0-0.mpr2.iah1.us.above.net [64.125.29.70]
17 70 ms 57 ms 56 ms t289.216-200-251-162.iah1.us.above.net [216.200
251.162]
18 67 ms 56 ms 56 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
19 70 ms 57 ms 57 ms gphou-66-98-240-107.ev1.net [66.98.240.107]
20 * *

Compared to a trace to ev1.net:

4 17 ms 16 ms 15 ms 130.81.20.62
5 22 ms 17 ms 18 ms so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.175]
6 32 ms 20 ms 17 ms dllstx9lcx1-pos1-0.wcg.net [64.200.105.109]
7 31 ms 17 ms 17 ms dllstx1wcx3-pos12-0.wcg.net [64.200.232.209]
8 38 ms 21 ms 21 ms hstntx1wcx3-pos1-0-oc192.wcg.net [64.200.210.66]

9 37 ms 21 ms 21 ms hstntx1wcx1-pos9-0-oc48.wcg.net [65.77.93.213]
10 24 ms 24 ms 24 ms everyones-internet-hstntx1wcx1-gige1-0.wcg.net [
65.77.93.54]
11 38 ms 25 ms 25 ms ivhou-207-218-223-66.ev1.net [207.218.223.66]
12 28 ms 25 ms 25 ms ev1s-216-88-76-23.ev1servers.net [216.88.76.23]

13 39 ms 25 ms 24 ms www.ev1.net [216.88.76.7]

Trace complete.
 
Works fine for me too from Portugal.


1 <1 ms <1 ms <1 ms ------------
2 1 ms 1 ms 1 ms -------------
3 8 ms 7 ms 7 ms -------------
4 21 ms 20 ms 20 ms dial-b1-170-170.telepac.pt [194.65.170.170]
5 22 ms 22 ms 21 ms dial-b1-170-113.telepac.pt [194.65.170.113]
6 20 ms 20 ms 20 ms dial-b1-169-102.telepac.pt [194.65.169.102]
7 20 ms 20 ms 20 ms 213.13.135.173
8 20 ms 20 ms 20 ms 213.13.135.222
9 21 ms 20 ms 20 ms lis1-br1-po-2-2.cprm.net [195.8.0.249]
10 21 ms 20 ms 24 ms lis2-cr1-gi-9-0.cprm.net [195.8.0.173]
11 76 ms 64 ms 68 ms lon1-cr1-po-1-0.cprm.net [195.8.0.162]
12 72 ms 82 ms 75 ms ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
13 53 ms 54 ms 53 ms pos3-0.mpr1.lhr1.uk.above.net [208.184.231.69]
14 55 ms 55 ms 54 ms so-4-1-0.cr1.lhr3.uk.above.net [208.184.231.174]

15 127 ms 126 ms 126 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
16 138 ms 138 ms 138 ms so-4-1-0.mpr2.atl6.us.above.net [64.125.29.41]
17 138 ms 141 ms 158 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
18 150 ms 149 ms 149 ms so-3-1-0.mpr2.iah1.us.above.net [64.125.29.62]
19 160 ms 160 ms 160 ms t289.216-200-251-162.iah1.us.above.net [216.200.
251.162]
20 160 ms 160 ms 160 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
21 160 ms 161 ms 161 ms gphou-66-98-240-107.ev1.net [66.98.240.107]
22 167 ms 163 ms 163 ms oaktecstore.com [67.15.74.129]

Trace complete.
 
Fine for me from the UK;

Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
1 2 2 1 1.0 ms
[10.200.2.13] [Internal] 64 [??] [Router did not respond]
2 4 4 1 1.5 ms [+0ms]
[10.200.1.2] [Internal] 0 miles [+0] 253 [??] [Router did not respond]
3 7 7 5 5.9 ms [+4ms]
[10.200.1.3] [Internal] 0 miles [+0] 253 [??] [Router did not respond]
4 14 17 15 14 ms [+8ms]
63.150.224.113 kcm-edge-12.inet.qwest.net. 0 miles [+0] 253 US [Router did not respond]
5 14 16 15 14 ms [+0ms]
205.171.29.141 kcm-core-01.inet.qwest.net. 0 miles [+0] 251 US Unix: 12:20:05.308
6 54 52 25 24 ms [+10ms]
67.14.2.10 dal-core-02.inet.qwest.net. 0 miles [+0] 249 US [Router did not respond]
7 24 27 25 24 ms [+0ms]
205.171.25.50 dal-brdr-02.inet.qwest.net. 0 miles [+0] 249 US [Router did not respond]
8 25 28 26 25 ms [+0ms]
129.250.9.81 p4-1-0-0.r00.dllstx09.us.bb.verio.net. 0 miles [+0] 248 US [Router did not respond]
9 25 38 37 25 ms [+0ms]
129.250.3.20 p16-1-0-0.r20.dllstx09.us.bb.verio.net. 0 miles [+0] 248 US [Router did not respond]
10 33 33 32 32 ms [+7ms]
129.250.5.41 p16-5-0-0.r02.hstntx01.us.bb.verio.net. 0 miles [+0] 246 US Unix: 12:20:06. 32
11 33 36 35 33 ms [+1ms]
129.250.10.230 ge-7.ev1.hstntx01.us.bb.verio.net. 0 miles [+0] 244 US [Router did not respond]
12 36 39 44 33 ms [+0ms]
66.98.241.28 gphou-66-98-241-28.ev1.net. 0 miles [+0] 243 US [Router did not respond]
13 40 41 41 33 ms [+0ms]
66.98.240.107 gphou-66-98-240-107.ev1.net. 0 miles [+0] 53 US [Router did not respond]
14 34 34 33 33 ms [+0ms]
67.15.74.129
[Reached Destination]oaktecstore.com. 0 miles [+0] 52 US [Router did not respond]
15
 
hmm - so I'm not the only one. Stephen, where would you even begin to resolve an issue like this? My ISP says it's out of their control. If it's not in their control, who IS in control?
 
unclechris,

I have not seen such an issue, it seems like it could be some sort of high restrictive firewall on the server itself(I know it is not the datacenter, as I know other people in the same datacenter).
 
you mean on the server the website resides on, within the datacenter? (i.e. you're saying you just don't believe it's the actual datacenter at fault, right? just some firewall settings, perhaps, on that particular server?)
 
Correct, I think it must be something on the server itself.

As I know other servers in the datacenter are working properly.
 
I cant seem to see anything either!! been on computer so long. Could someone tell me where do you click to start a new thread after you register? Sorry this isnt in response to your question.
 
Back
Top