ERROR

from usenet:

===========================================================

Every IP packet has a Time to Live setting that specifies the maximum
number of router hops. Every router that forwards the packet decrements
this counter by one. When the counter reaches zero without reaching the
destination, that router sends a Time Exceeded error message back to the
source. This does not imply that anything is wrong with the network,
just that the path is longer than your ping can travel.

If you are using a Windows workstation then execute

C:\>ping 127.0.0.1

The response will indicate a TTL value (128, for example). This should
be more than enough to reach any destination, but if the value is, say,
32, this is too small.

You can run

C:\>ping -i 128 x.x.x.x

to increase the TTL to 128. This should allow the ping to complete.

Every Windows version from Win98 and up has an adequate TTL, but some
early versions of Win95 are a bit too small. See
http://www.sohointer.net/howto/tweak_tcp.htm for information on
increasing the TTL or removing a too-small TTL.

If it turns out that your TTL is adequate, then what is happening is
that your ping packets are getting caught in a routing loop and
expiring. These routing loops usually disappear after a while, but it is
possible to get a persistent routing loop across service providers. If
this appears to be the case, you'll want to run a traceroute

C:\>tracert x.x.x.x

and save the output for your ISP for analysis. The traceroute should
show the routing loop as a series of repeating IP addresses. These
addresses will indicate where the loop is located and allow your ISP to
fix it.


<i>It's always the one thing you never suspected.</i>

4 10 ms 10 ms 20 ms fe1-0-0.core01.tor.pathcom.com [209.250.130.178]

5 10 ms 10 ms 10 ms gw-velocet.torontointernetxchange.net [198.32.24
5.50]
6 10 ms 10 ms 20 ms hadrian1.tor.velocet.net [216.138.255.1]
7 10 ms 10 ms 10 ms trebuchet.tor.velocet.net [216.138.223.2]
8 20 ms 20 ms 10 ms redfix.velocet.net [216.138.223.142]
9 10 ms 20 ms 10 ms trebuchet.tor.velocet.net [216.138.223.2]
10 20 ms 20 ms 10 ms redfix.velocet.net [216.138.223.142]
11 10 ms 10 ms 10 ms trebuchet.tor.velocet.net [216.138.223.2]
12 10 ms 10 ms 20 ms redfix.velocet.net [216.138.223.142]
13 10 ms 10 ms 10 ms trebuchet.tor.velocet.net [216.138.223.2]
14 10 ms 10 ms 20 ms redfix.velocet.net [216.138.223.142]
15 10 ms 10 ms 20 ms trebuchet.tor.velocet.net [216.138.223.2]
^C
C:\>^C

called them , told them: no sir, it is normal, when you are disconnected, it bounces between routers.
if i am not online, i should timeout, not TTL expired in transit!!!
the tech support guy opened a ticket with my phone company to check with them as well.
i wonder if i should try another router.
At 8:20 this morning i was reading my emails, and in my ISP's logs, at 8:20 i logged of the internet(their router).
weird,eh?
thx for the help

<font color=green>it is never fast enough</font color=green>

should these pings even be making it out? Most routers will not let ICMP replies in without a config change.

Granted, it should be Request timed out instead of what you're seeing, but I'm wondering how your config is.

<i>It's always the one thing you never suspected.</i>

i guess problem solved
got a new router, a linksys.
will see
thx for your help

<font color=green>it is never fast enough</font color=green>