Problems getting on the site

[Brettfan]

Hello Mods,

Need some assistance here.

For over a week I've been unable to access the site via my computer. No problem getting on with my phone.

My husband is a computer genius and spent the better part of Sunday and part of yesterday trying to figure out the problem. The only thing he could come up with is that you're (the site) blocking my IP address.

Is there anyway you could check that? I am logged on through a dummy IP just to figure this out.

If you think that's the problem please PM me then I'll give you my IP address.

Thanks SO Much,
Melissa

 

[Champs96ws]

You will need to do a traceroute from the pc in question

http://www.mediacollege.com/internet/troubleshooter/traceroute.html

That will tell you where it's being blocked. most likely your isp.

 

[Brettfan]

Thanks, ill pass this info on to my husband and see where it gets us. I'm thinking that he's already tried this but ill see what he says.

Thanks again,
Melissa

 

[Champs96ws]

Let me know either way, if all else fails. PM me your IP and I will contact our host.

 

[Brettfan]

Here is a trace of the ip that does not work:
Tracing route to thebenchtrading.com [74.204.167.43]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 33 ms 34 ms 9 ms 10.5.25.94
4 12 ms 11 ms 11 ms 10.20.12.21
5 32 ms 18 ms 32 ms 216.55.10.61
6 14 ms 41 ms 13 ms ae1d0.mcr1.chicago-il.us.xo.net [216.156.1.81]
7 19 ms 24 ms 20 ms vb1700.rar3.chicago-il.us.xo.net [216.156.0.161]
8 14 ms 15 ms 31 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194]
9 35 ms 36 ms 49 ms te0-7-0-8.ccr21.ord03.atlas.cogentco.com [154.54.10.181]
10 35 ms 34 ms 32 ms te0-4-0-1.mpd22.ord01.atlas.cogentco.com [154.54.25.69]
11 31 ms 31 ms 61 ms te0-2-0-1.mpd22.dca01.atlas.cogentco.com [154.54.40.241]
12 67 ms 40 ms 38 ms te0-2-0-1.mpd22.iad02.atlas.cogentco.com [154.54.5.42]
13 205 ms 31 ms 35 ms te1-8.ccr02.iad01.atlas.cogentco.com [154.54.31.174]
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.

Here is a trace of the one that works:
Tracing route to thebenchtrading.com [74.204.167.43]
over a maximum of 30 hops:

1 * * * Request timed out.
2 33 ms 31 ms 38 ms iptfarma-mr1-sw0-vla3.conc.aol.com [64.12.120.30]
3 33 ms 35 ms 31 ms cam1-mtc-ae0.net.aol.com [172.20.201.11]
4 33 ms 35 ms 36 ms dar1-mtc-ae1.atdn.net [66.185.144.45]
5 35 ms 34 ms 35 ms pop1-ash-xe-4-3-0.atdn.net [66.185.151.101]
6 36 ms 34 ms 54 ms cogent-pop1-ash.atdn.net [66.185.141.206]
7 43 ms 207 ms 199 ms te2-7.ccr02.iad01.atlas.cogentco.com [154.54.31.214]
8 53 ms 34 ms 35 ms 38.104.206.226
9 152 ms 50 ms 98 ms aggr-sw2.iad.defenderhosting.com [69.65.112.94]
10 34 ms 34 ms 35 ms eqashhspc44.iad.keepitsecure.net [74.200.88.2]
11 37 ms 35 ms 38 ms thebenchtrading.com [74.204.167.43]

Trace complete.

Let us know what you think. We can provide you the IP we normally use in an email if you want it.

Thanks

 

[Champs96ws]

Contact your ISP. The signal is timing out in THEIR network before it reaches our host.

Explain to them you did a traceroute and give them a copy if requested.