![link to this post #](/images/board_posticon.gif)
is Pipex shit?
I do notice your DNS server is on a non-public subnet (10.0) (this may be your router/firewall, but they're usually 192.168).
Do a tracert to one of them and see where it fails.
I'm off for food.
( ,
Sat 18 Jun 2005, 1:02,
archived)
I do notice your DNS server is on a non-public subnet (10.0) (this may be your router/firewall, but they're usually 192.168).
Do a tracert to one of them and see where it fails.
I'm off for food.
![link to this post #](/images/board_posticon.gif)
And the tracert was
Sadly this doesn't mean a huge amount to me
( ,
Sat 18 Jun 2005, 1:07,
archived)
C:\tracert 38.116.157.195
Tracing route to 38.116.157.195 over a maximum of 30 hops
1 * * * Request timed out.
2 21 ms 23 ms 21 ms loopback1.ar1.gs1.systems.pipex.net [62.241.161.247]
3 22 ms 22 ms 21 ms ge-1-0-0.cr1.gs1.systems.pipex.net [62.241.161.94]
4 21 ms 20 ms 21 ms ldn-b1-geth6-0-12.telia.net [213.248.100.105]
5 21 ms 21 ms 21 ms ldn-bb2-pos1-2-0.telia.net [213.248.74.13]
6 95 ms 114 ms 114 ms nyk-bb2-pos7-0-0.telia.net [213.248.65.210]
7 100 ms 98 ms 98 ms ash-bb1-pos7-0-0-0.telia.net [213.248.80.138]
8 97 ms 97 ms 98 ms cogent-02016-ash-bb1.telia.net [213.248.88.42]
9 99 ms 98 ms 100 ms p11-0.core01.dca01.atlas.cogentco.com [154.54.2.201]
10 103 ms 106 ms 102 ms p4-0.core01.phl01.atlas.cogentco.com [66.28.4.18]
11 101 ms 118 ms 101 ms p5-0.core02.jfk02.atlas.cogentco.com [66.28.4.1]
12 123 ms 124 ms 124 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.86]
13 135 ms 136 ms 137 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
14 167 ms 170 ms 164 ms p5-0.core01.den01.atlas.cogentco.com [66.28.4.29]
15 149 ms 147 ms 147 ms p5-0.core01.den02.atlas.cogentco.com [66.28.4.42]
16 150 ms 151 ms 151 ms 38.116.157.195
Trace complete.
Sadly this doesn't mean a huge amount to me