Re: OT: Dontronics Web Site




Cam wrote:

>Tracing route to dontronics.com [209.9.226.66]
>over a maximum of 30 hops:

...
> 10 0.so-6-1-0.BR1.LAX7.ALTER.NET [152.63.113.1]
> 11 204.255.168.30
> 12 tbr2-p012101.la2ca.ip.att.net [12.123.29.6]
> 13 tbr2-cl2.sl9mo.ip.att.net [12.122.10.13]
> 14 tbr1-cl2.sl9mo.ip.att.net [12.122.9.141]
> 15 tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
> 16 gar1-p300.ascva.ip.att.net [12.123.8.49]
> 17 att-peer.er1.iad1.ptptech.net [209.9.224.154]
> 18 Request timed out.
> ...
> 30 Request timed out.
>
>Trace complete.

Here is what I get:

tracert dontronics.com

...
6 att-level3-oc48.SanJose1.Level3.net [209.0.227.30]
7 tbr1-p012201.sffca.ip.att.net [12.123.13.189]
8 tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]
9 tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
10 gar1-p300.ascva.ip.att.net [12.123.8.49]
11 att-peer.er1.iad1.ptptech.net [209.9.224.154]
12 titan.genwebhost.com [209.9.226.66]

Trace complete.

So, comparing the two, I see:

YOU > 16 gar1-p300.ascva.ip.att.net [12.123.8.49]
ME | 10 gar1-p300.ascva.ip.att.net [12.123.8.49]

YOU > 17 att-peer.er1.iad1.ptptech.net [209.9.224.154]
ME | 11 att-peer.er1.iad1.ptptech.net [209.9.224.154]

YOU > 18 Request timed out.
ME | 12 titan.genwebhost.com [209.9.226.66]

So why can I get from 209.9.224.154 to 209.9.226.66 and you can't?

Would you be so kind as to ping 209.9.224.154 and 209.9.226.66 and
report the results?

Lets look at possible blocking:

Your NNTP-Posting-Host is 59.167.68.200,
which is ppp68-200.lns1.mel2.internode.on.net.
I am assuming that this is #1 on your tracert.

#2 on your tracert is 150.101.212.16,
which is loop0.lns1.mel2.internode.on.net

Let's look at them all at http://www.spamcop.net/

150.101.212.16 not listed in bl.spamcop.net
150.101.212.16 not listed in dnsbl.njabl.org
150.101.212.16 not listed in dnsbl.njabl.org
150.101.212.16 not listed in cbl.abuseat.org
150.101.212.16 not listed in dnsbl.sorbs.net
150.101.212.16 not listed in relays.ordb.org.

59.167.68.200 not listed in bl.spamcop.net
59.167.68.200 not listed in dnsbl.njabl.org
59.167.68.200 not listed in dnsbl.njabl.org
59.167.68.200 not listed in cbl.abuseat.org
59.167.68.200 not listed in dnsbl.sorbs.net
59.167.68.200 not listed in relays.ordb.org.

209.9.224.154 not listed in bl.spamcop.net
209.9.224.154 not listed in dnsbl.njabl.org
209.9.224.154 not listed in dnsbl.njabl.org
209.9.224.154 not listed in cbl.abuseat.org
209.9.224.154 not listed in dnsbl.sorbs.net
209.9.224.154 not listed in relays.ordb.org.

209.9.226.66 not listed in bl.spamcop.net
209.9.226.66 not listed in dnsbl.njabl.org
209.9.226.66 not listed in dnsbl.njabl.org
209.9.226.66 not listed in cbl.abuseat.org
209.9.226.66 not listed in dnsbl.sorbs.net
209.9.226.66 not listed in relays.ordb.org.

OK, so nobody on either end is on a common block list.

I am stumped.



.

Relevant Pages

  • Re: Access to two websites
    ... Tracert logs as below ... Tracing route to steelbeasts.com ... over a maximum of 30 hops: ... Trace complete. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: tracert not working
    ... tracert www.yahoo.com ... Tracing route to www.yahoo.akadns.net ... Trace complete. ... |> | same with the ping command also. ...
    (microsoft.public.windowsxp.general)
  • Re: Trouble Reaching Web Sites
    ... A Tracert to www.tennessean.com results in the "Destination Net ... Unreachable" after hitting about 10 hops. ... Here are ping and tracert results to pcworld.com. ... the traceroute is finished when you see "Trace complete". ...
    (comp.dcom.xdsl)
  • Trouble Reaching Web Sites
    ... Here are ping and tracert results to pcworld.com. ... over a maximum of 30 hops: ... the traceroute is finished when you see "Trace complete". ...
    (comp.dcom.xdsl)
  • Re: Strange Multi-homed Traceroute/Ping failure for some IPs on some routes
    ... Tracing route to 83.111.196.57 over a maximum of 30 hops ... Trace complete. ... My ISP dont want to believe its their fault. ...
    (comp.os.linux.networking)
Loading