PDA

View Full Version : Some kinda joke?


GRIM
10-16-00, 08:10 PM
these are my results of my daily 5pm ping to the router, normally I would be getting 300+ms
hmmm must be a fluke?

Pinging 24.7.74.153 with 32 bytes of data:

Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=27ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=13ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=13ms TTL=253
Reply from 24.7.74.153: bytes=32 time=27ms TTL=253
Reply from 24.7.74.153: bytes=32 time=83ms TTL=253
Reply from 24.7.74.153: bytes=32 time=13ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253
Reply from 24.7.74.153: bytes=32 time=13ms TTL=253
Reply from 24.7.74.153: bytes=32 time=14ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 83ms, Average = 20ms
http://www.geocities.com/drk6x/images/@home.jpg

Cuu
10-16-00, 08:42 PM
Pinging 24.7.74.153 with 32 bytes of data:

Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=19ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=17ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=19ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=15ms TTL=253
Reply from 24.7.74.153: bytes=32 time=18ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=17ms TTL=253
Reply from 24.7.74.153: bytes=32 time=18ms TTL=253
Reply from 24.7.74.153: bytes=32 time=18ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 19ms, Average = 17ms

dray_heinz
10-16-00, 08:47 PM
I am getting the same results as you guys.

Reply from 24.7.74.153: bytes=32 time=20ms TTL=253
Reply from 24.7.74.153: bytes=32 time=39ms TTL=253
Reply from 24.7.74.153: bytes=32 time=17ms TTL=253
Reply from 24.7.74.153: bytes=32 time=20ms TTL=253
Reply from 24.7.74.153: bytes=32 time=21ms TTL=253
Reply from 24.7.74.153: bytes=32 time=22ms TTL=253
Reply from 24.7.74.153: bytes=32 time=19ms TTL=253
Reply from 24.7.74.153: bytes=32 time=21ms TTL=253
Reply from 24.7.74.153: bytes=32 time=25ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=65ms TTL=253
Reply from 24.7.74.153: bytes=32 time=15ms TTL=253
Reply from 24.7.74.153: bytes=32 time=17ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=16ms TTL=253
Reply from 24.7.74.153: bytes=32 time=17ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 65ms, Average = 21ms


I am not going to say anything else until I see the same speeds at 9 or so tonight.

audiblevibe
10-16-00, 08:51 PM
yeah im getting awesome pings too, but i notice i cant connect to the sites www.metacrawler.com (http://www.metacrawler.com) www.sitetracker.com (http://www.sitetracker.com)

and many other random sites.
anyone else having this problem?

Cuu
10-16-00, 09:06 PM
same here. i can't connect to most sites.

spoke too soon

Pinging 24.7.74.153 with 32 bytes of data:

Reply from 24.7.74.153: bytes=32 time=111ms TTL=253
Reply from 24.7.74.153: bytes=32 time=92ms TTL=253
Reply from 24.7.74.153: bytes=32 time=137ms TTL=253
Reply from 24.7.74.153: bytes=32 time=107ms TTL=253
Reply from 24.7.74.153: bytes=32 time=98ms TTL=253
Reply from 24.7.74.153: bytes=32 time=89ms TTL=253
Reply from 24.7.74.153: bytes=32 time=92ms TTL=253
Reply from 24.7.74.153: bytes=32 time=67ms TTL=253
Reply from 24.7.74.153: bytes=32 time=113ms TTL=253
Reply from 24.7.74.153: bytes=32 time=98ms TTL=253
Reply from 24.7.74.153: bytes=32 time=126ms TTL=253
Reply from 24.7.74.153: bytes=32 time=86ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 137ms, Average = 101ms

it's not bad. it sucks!

[This message has been edited by Cuu (edited 10-16-2000).]

Cable Guy
10-16-00, 09:09 PM
Hmm maybe they fixed it?

------------------
Its the cable guy!

dray_heinz
10-16-00, 09:13 PM
Reply from 24.7.74.153: bytes=32 time=130ms TTL=253
Reply from 24.7.74.153: bytes=32 time=155ms TTL=253
Reply from 24.7.74.153: bytes=32 time=141ms TTL=253
Reply from 24.7.74.153: bytes=32 time=137ms TTL=253
Reply from 24.7.74.153: bytes=32 time=123ms TTL=253
Reply from 24.7.74.153: bytes=32 time=160ms TTL=253
Reply from 24.7.74.153: bytes=32 time=151ms TTL=253
Reply from 24.7.74.153: bytes=32 time=120ms TTL=253
Reply from 24.7.74.153: bytes=32 time=138ms TTL=253
Reply from 24.7.74.153: bytes=32 time=119ms TTL=253
Reply from 24.7.74.153: bytes=32 time=94ms TTL=253
Reply from 24.7.74.153: bytes=32 time=92ms TTL=253
Reply from 24.7.74.153: bytes=32 time=117ms TTL=253
Reply from 24.7.74.153: bytes=32 time=143ms TTL=253
Reply from 24.7.74.153: bytes=32 time=122ms TTL=253
Reply from 24.7.74.153: bytes=32 time=154ms TTL=253
Reply from 24.7.74.153: bytes=32 time=129ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 49, Received = 49, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 160ms, Average = 120ms


Maybe we spoke to soon. These are my results half an hour after the last ones I posted. It looks like its starting to climb again http://www.speedguide.net/ubb/frown.gif

audiblevibe
10-16-00, 09:14 PM
I cant even connect to @homes main page.

audiblevibe
10-16-00, 09:15 PM
I can connect to speedguide though http://www.speedguide.net/ubb/smile.gif

GRIM
10-16-00, 09:18 PM
Starting to rise some but concidering what we usually get at this time of day this is good news if it's not a fluke

Pinging 24.7.74.153 with 32 bytes of data:

Reply from 24.7.74.153: bytes=32 time=137ms TTL=253
Reply from 24.7.74.153: bytes=32 time=96ms TTL=253
Reply from 24.7.74.153: bytes=32 time=164ms TTL=253
Reply from 24.7.74.153: bytes=32 time=110ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 164ms, Average = 126ms
http://www.geocities.com/drk6x/images/@home.jpg

GRIM
10-16-00, 09:19 PM
HMMMM! seem to be having web page issues now as a side affect I believe
http://www.geocities.com/drk6x/images/@home.jpg

audiblevibe
10-16-00, 09:20 PM
I want to add an email account, like many things i can get it there barely but then when i hit a button to submit something it just Friggin times out! Starting to piss me off. I have to get a website up by tonight and im afraid to sub,mit it to search engines for fear it won't work right. It started earlier this morning it seems. And it BullS$%#

Cable Guy
10-16-00, 09:21 PM
Seems the ping went up

------------------
Its the cable guy!

audiblevibe
10-16-00, 09:24 PM
Im about to kill a cable guy.

SS
10-16-00, 09:34 PM
CABLE GUY!!!! YES OF COURSE IT "SEEMS THE PING WENT UP", and yes indeed, maybe they DID fix it, oops maybe not. Please reply and say "maybe they didn't fix it."

I'm so glad to hear you guys are having the same web browsing problems, too. I thought it was something I did. Pings have been fair, but spikey as hell. Pings are now rising. GG.

glc1
10-16-00, 09:42 PM
Originally posted by SS:
CABLE GUY!!!! YES OF COURSE IT "SEEMS THE PING WENT UP", and yes indeed, maybe they DID fix it, oops maybe not. Please reply and say "maybe they didn't fix it."

I'm so glad to hear you guys are having the same web browsing problems, too. I thought it was something I did. Pings have been fair, but spikey as hell. Pings are now rising. GG.Don't pay any attention to Cable Guy, he is just trying to get his posts up (aka spammer). He's always been like that...LOL

dray_heinz
10-16-00, 10:31 PM
Reply from 24.7.74.153: bytes=32 time=265ms TTL=253
Reply from 24.7.74.153: bytes=32 time=272ms TTL=253
Reply from 24.7.74.153: bytes=32 time=253ms TTL=253
Reply from 24.7.74.153: bytes=32 time=294ms TTL=253
Reply from 24.7.74.153: bytes=32 time=317ms TTL=253
Reply from 24.7.74.153: bytes=32 time=311ms TTL=253
Reply from 24.7.74.153: bytes=32 time=295ms TTL=253
Reply from 24.7.74.153: bytes=32 time=308ms TTL=253
Reply from 24.7.74.153: bytes=32 time=297ms TTL=253
Reply from 24.7.74.153: bytes=32 time=306ms TTL=253
Reply from 24.7.74.153: bytes=32 time=310ms TTL=253
Reply from 24.7.74.153: bytes=32 time=329ms TTL=253
Reply from 24.7.74.153: bytes=32 time=323ms TTL=253
Reply from 24.7.74.153: bytes=32 time=292ms TTL=253
Reply from 24.7.74.153: bytes=32 time=303ms TTL=253
Reply from 24.7.74.153: bytes=32 time=270ms TTL=253
Reply from 24.7.74.153: bytes=32 time=259ms TTL=253

Ping statistics for 24.7.74.153:
Packets: Sent = 265, Received = 265, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 205ms, Maximum = 346ms, Average = 275ms

Nothing has changed going way down http://www.speedguide.net/ubb/frown.gif

audiblevibe
10-16-00, 10:59 PM
Pings probably went down becuase noone could access any real sites.

audiblevibe
10-16-00, 10:59 PM
Pings probably went down becuase noone could access any real sites.

Cuu
10-17-00, 01:02 AM
my ping is around 450+ms right now, and it takes forever to browse. i just thought of some. hey grim, you said there were 6 comcast vans trying to figure out the problem. i thought the problem router was somewhere in the bay area. just venting..not at you grim. later.

DaveM
10-17-00, 02:10 AM
1 24.7.74.153 56bytes 41ms Success
2 24.7.74.153 56bytes 41ms Success
3 24.7.74.153 56bytes 27ms Success
4 24.7.74.153 56bytes 41ms Success
5 24.7.74.153 56bytes 41ms Success
===============================
11Pm.
Im not in your area, I am pinging from Seattle.
If you are inside the gateway and get high pings and I'm outside the gateway and get low pings. It would appear to be network congestion.

And thats why when everybody was having problems surfing, that your pings were great. YOUR DNS Servers were down.

Heres a hint.
Try using another gateway (if you can)
I know I can use any News Server and any Email server and any DNS server in the @ Home network. Say our DNS server goes down, I just plug a different DNS into my Netgear router. Or the News server is down... I might plug one in from Illinois.
*hint* your gateway has to match your ip address ie. 24.aaa.bbb.ccc is your ip then your gateway would need to be 24.aaa.bbb.xyz, where xyz is the only part that differs from your IP address.

To find other servers use WSFTP Ping Pro Pack and find @home networks that begin with 24.xxx.xxx.xxx

From there you can ping like news.city.home.com and you will get response from news.regionmastercity.home.com

As long as you are in the @home network, all these servers that are "@HOME" are legal servers for your network configuration.

I swear we had our DNS servers down for 24 hours, But I had a list of other DNS severs and I was the only person on our node who could surf the web.

[This message has been edited by DaveM (edited 10-17-2000).]

GRIM
10-17-00, 03:11 AM
Originally posted by Cuu:
grim, you said there were 6 comcast vans trying to figure out the problem. i thought the problem router was somewhere in the bay area. just venting..not at you grim. later.
Yes I believe it is located some where in that direction, but this proves how confused the are. At ths point venting is all we can do, thats what makes message boards like this one a great place to post. There are peeps here who feel our pain and understand
from their own experiences good and bad. Vent on braaaahhhhhhhh!
http://www.geocities.com/drk6x/images/@home.jpg

GRIM
10-17-00, 03:15 AM
Yo DaveM! good info thanks a lot
http://www.geocities.com/drk6x/images/@home.jpg