You might be (almost) at TOPE. If I ping 195.85.182.16 it reports 187ms to
195ms time from San Jose to there. You could compare the time reported from
ping to the time the tracert lives.
I don't get outside of my company with tracert. I'll check from home. Both
home and work can access the TOPE site.
I believe the networks can distinguish the type of data packet and of course
the IP of the source. They probably let ping through so that they can do
fundamental checks. They may still block a http packet. I would have thought
the most common thing they block is mail - smtp. I know very little about
what the hackers do though.
-jeff
----Original Message Follows----
From: Moose <olymoose@xxxxxxxxxxxxxxx>
The other reason I believe it is address blocking is that I can still
connect using Compuserve. Same computer, same DSL connection, same URL
or IP entered. So if I approach using my own "name", I am rejected, If I
approach cloaked in a Compuserve "name", I am accepted. And who said the
old stories like Cyrano aren't relevant in today's technical world?
I suspect a sysop in the Netherlands got some trouble from folks in
certain address blocks and simply blocked access from whole address
blocks, so folks with SBC and Verizon as ISPs can't get through.
Moose
C:\>tracert www.tope.nl
Tracing route to www.tope.nl [195.85.182.16]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 71.141.24.49
2 9 ms 9 ms 9 ms 71.141.31.254
3 9 ms 9 ms 9 ms dist2-vlan60.snfc21.pbi.net
[216.102.187.131]
4 8 ms 9 ms 9 ms bb2-10g2-0.snfcca.sbcglobal.net
[216.102.176.226]
5 9 ms 9 ms 10 ms bb1-p3-0.snfcca.sbcglobal.net
[151.164.190.185]
6 9 ms 9 ms 9 ms core1-p14-1.crsfca.sbcglobal.net
[151.164.242.65]
7 25 ms 26 ms 26 ms bb2-p13-0.sttlwa.sbcglobal.net
[151.164.241.57]
8 26 ms 26 ms 26 ms bb1-p14-0.sttlwa.sbcglobal.net
[151.164.240.173]
9 26 ms 26 ms 26 ms ex1-p4-0.pxsewa.sbcglobal.net
[151.164.41.201]
10 27 ms 27 ms 26 ms above-sbc-oc12.sea4.above.net
[151.164.89.90]
11 29 ms 29 ms 28 ms so-3-2-0.mpr3.sjc2.us.above.net
[64.125.28.182]
12 29 ms 28 ms 43 ms so-0-0-0.mpr4.sjc2.us.above.net
[64.125.30.2]
13 75 ms 75 ms 74 ms so-2-2-0.cr1.dfw2.us.above.net
[64.125.29.46]
14 75 ms 74 ms 75 ms so-0-0-0.cr2.dfw2.us.above.net
[64.125.28.210]
15 94 ms 94 ms 95 ms so-2-1-0.cr2.dca2.us.above.net
[64.125.29.14]
16 166 ms 191 ms 166 ms so-6-0-0.cr2.lhr3.uk.above.net
[64.125.27.166]
17 179 ms 179 ms 178 ms so-7-0-0.mpr1.ams5.nl.above.net
[64.125.27.178]
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 ^C
C:\>tracert 195.85.182.16
Tracing route to wc-16.r-195-85-182.essentkabel.com [195.85.182.16]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 71.141.24.49
2 9 ms 9 ms 8 ms 71.141.31.254
3 10 ms 9 ms 8 ms dist2-vlan60.snfc21.pbi.net
[216.102.187.131]
4 10 ms 9 ms 9 ms bb2-10g2-0.snfcca.sbcglobal.net
[216.102.176.226]
5 9 ms 9 ms 9 ms bb1-p3-0.snfcca.sbcglobal.net
[151.164.190.185]
6 9 ms 9 ms 10 ms core1-p14-1.crsfca.sbcglobal.net
[151.164.242.65]
7 26 ms 26 ms 26 ms bb2-p13-0.sttlwa.sbcglobal.net
[151.164.241.57]
8 26 ms 26 ms 26 ms bb1-p14-0.sttlwa.sbcglobal.net
[151.164.240.173]
9 26 ms 26 ms 26 ms ex1-p4-0.pxsewa.sbcglobal.net
[151.164.41.201]
10 27 ms 27 ms 27 ms above-sbc-oc12.sea4.above.net
[151.164.89.90]
11 29 ms 29 ms 29 ms so-3-2-0.mpr3.sjc2.us.above.net
[64.125.28.182]
12 29 ms 28 ms 28 ms so-0-0-0.mpr4.sjc2.us.above.net
[64.125.30.2]
13 74 ms 74 ms 75 ms so-2-2-0.cr1.dfw2.us.above.net
[64.125.29.46]
14 74 ms 74 ms 75 ms so-0-0-0.cr2.dfw2.us.above.net
[64.125.28.210]
15 94 ms 95 ms 94 ms so-2-1-0.cr2.dca2.us.above.net
[64.125.29.14]
16 166 ms 166 ms 166 ms so-6-0-0.cr2.lhr3.uk.above.net
[64.125.27.166]
17 178 ms 178 ms 178 ms so-7-0-0.mpr1.ams5.nl.above.net
[64.125.27.178]
18 * * * Request timed out.
19 * ^C
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|