Post by news.verizon.netIf I ping the various DNS servers I am pretty regularly, but not
Reply from 151.204.0.85: bytes=32 time=121ms TTL=249
Reply from 151.204.0.85: bytes=32 time=115ms TTL=249
Reply from 151.204.0.85: bytes=32 time=94ms TTL=249
Request timed out.
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Minimum = 94ms, Maximum = 121ms, Average = 110ms
Reply from 151.204.0.85: bytes=32 time=117ms TTL=249
Reply from 151.204.0.85: bytes=32 time=83ms TTL=249
Reply from 151.204.0.85: bytes=32 time=122ms TTL=249
Reply from 151.204.0.85: bytes=32 time=105ms TTL=249
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Minimum = 83ms, Maximum = 122ms, Average = 106ms
Request timed out.
Reply from 151.204.0.85: bytes=32 time=116ms TTL=249
Reply from 151.204.0.85: bytes=32 time=120ms TTL=249
Reply from 151.204.0.85: bytes=32 time=84ms TTL=249
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Minimum = 84ms, Maximum = 120ms, Average = 106ms
Reply from 151.204.0.85: bytes=32 time=60ms TTL=249
Reply from 151.204.0.85: bytes=32 time=54ms TTL=249
Reply from 151.204.0.85: bytes=32 time=77ms TTL=249
Request timed out.
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Minimum = 54ms, Maximum = 77ms, Average = 63ms
Post by Rage CosmosPost by news.verizon.netEverything is slow, internet surfing, newsgroups, even emais is a
problem. Sites either won;t load or take 10 minutes to load the
homepage. If I try to download from newgroups, it will start a
download and then it just stops.
The same thing happened Thursday night, but tehn it cleared up
after 10 pm. Now its bad again.
Slow here in Westchester County.
It's not exactly spectacular, but no packet loss from here:
Pinging 151.204.0.85 with 32 bytes of data:
Reply from 151.204.0.85: bytes=32 time=46ms TTL=249
Reply from 151.204.0.85: bytes=32 time=47ms TTL=249
Reply from 151.204.0.85: bytes=32 time=46ms TTL=249
Reply from 151.204.0.85: bytes=32 time=45ms TTL=249
Reply from 151.204.0.85: bytes=32 time=47ms TTL=249
Reply from 151.204.0.85: bytes=32 time=47ms TTL=249
Reply from 151.204.0.85: bytes=32 time=48ms TTL=249
Reply from 151.204.0.85: bytes=32 time=48ms TTL=249
Reply from 151.204.0.85: bytes=32 time=47ms TTL=249
Reply from 151.204.0.85: bytes=32 time=48ms TTL=249
Ping statistics for 151.204.0.85:
Packets: Sent = 10, Received = 10, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 48ms, Average = 46ms
The other addresses you used were all faster & 0 losses.
Perhaps you have some issues on your home-line? Try going to another
site and pinging from there. dnsstuff.com is one place you can do that
from; lots of others available. Best would be to locate one
geographically close to you so the comparisons are apples to apples.
Using tracert might provide some interesting data. Here's how mine
works:
F:\>tracert 151.204.0.85
Tracing route to nspen.bellatlantic.net [151.204.0.85]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]
2 36 ms 35 ms 34 ms 10.16.7.1
3 35 ms 34 ms 35 ms ge-2-2-0-0.CORE-RTR1.SYR.verizon-gni.net
[130.81.4.117]
4 70 ms 45 ms 44 ms 130.81.20.100
5 46 ms 45 ms 46 ms 130.81.19.95
6 47 ms 47 ms 47 ms
so-7-0-0-0.CORE-RTR2.PSKN.verizon-gni.net [130.81.20.199]
7 47 ms 47 ms 47 ms nspen.bellatlantic.net [151.204.0.85]
Trace complete.
Interesting note: If I don't use the -d, it complains it cannot resolve
the system name and fails to trace. Perhaps temporary, but ... .
--
--
Regards,
Twayne
Open Office isn't just for wimps anymore;
OOo is a GREAT MS Office replacement
www.openoffice.org