From: "Frank Haber" 

There you go.

When OE couldn't get a rise out of you, I ICMP pinged the URL with no
response.  I believe even DNS411 com couldn't find a server that knew you.
I didn't have any NLS.net dotted IPs handy, so I stopped there.  After 5,
all was normal.

Here's my path today, for what it's worth...

TraceRoute - Tuesday, March 18, 2003 22:47:45 Generated by CyberKit Version 2.5
Copyright C 1996-2000 by Luc Neijens

Address: news.barkto.com
Number of Packets: 1
Packet size: 34
Trace Hop 2 through 31
Timeout: 4
Resolve Addresses: Yes
Don't Fragment: No

#2 ge6-0-0.core1.nyr.ny.rcn.net (208.59.251.194): TTL Exceeded, ttl=254, 21
ms
#3 pos0-0.core3.nyw.ny.rcn.net (207.172.19.25): TTL Exceeded, ttl=253, 12 ms
#4 ge5-0-0.border1.nyw.ny.rcn.net (207.172.15.84): TTL Exceeded, ttl=252, 9
ms
#5 500.POS1-3.GW8.NYC9.ALTER.NET (157.130.5.17): TTL Exceeded, ttl=243, 14
ms
#6 540.at-6-0-0.XR1.NYC9.ALTER.NET (152.63.24.158): TTL Exceeded, ttl=243,
15 ms
#7 0.so-3-1-0.XL1.NYC9.ALTER.NET (152.63.9.58): TTL Exceeded, ttl=244, 15 ms
#8 0.so-4-0-0.TL1.NYC9.ALTER.NET (152.63.0.173): TTL Exceeded, ttl=245, 15
ms
#9 0.so-6-0-0.TL1.CHI2.ALTER.NET (152.63.13.21): TTL Exceeded, ttl=245, 39
ms
#10 0.so-2-0-0.XL1.CHI2.ALTER.NET (152.63.67.126): TTL Exceeded, ttl=244, 34
ms
#11 0.so-7-0-0.XR1.CHI2.ALTER.NET (152.63.67.130): TTL Exceeded, ttl=243, 37
ms
#12 193.at-6-2-0.CL1.CLE1.ALTER.NET (152.63.67.49): TTL Exceeded, ttl=242,
44 ms
#13 191.ATM6-0.GW5.CLE1.ALTER.NET (152.63.69.185): TTL Exceeded, ttl=242, 44
ms
#14 nls-gw.customer.ALTER.NET (157.130.104.94): TTL Exceeded, ttl=241, 45 ms
#15 r-cle-ds3.nls.net (216.144.27.222): TTL Exceeded, ttl=240, 50 ms
#16 w3.nls.net (216.144.1.254): Echo Reply, ttl=48, 54 ms

Statistics: Out 15, in 15, loss 0%, times (min/avg/max) 9/29/54 ms



.

--- BBBS/NT v4.01 Flag-4