You're in the right, so it can only serve to protect you no matter how irate you get.
I don't know how I like being compared to tobacco chew, but thanks a ton anyway.
printing from dos cmd prompt
- Thread starter reckedracing
- Start date
- Replies 40
- Views 3K
We may earn a small commission from affiliate links and paid advertisements. Terms
You're in the right, so it can only serve to protect you no matter how irate you get.
I don't know how I like being compared to tobacco chew, but thanks a ton anyway.
ok im confused as to what all of you are talking about. but i too am having a problem with my internet. it periodically times out. like just drops the signal altogether and just pick it back up in like 30 seconds or so it does this every few minutes if not more frequently. what does the ping test do? how do i read the results? what do the other tests do? i want to call my cable company but i dont want them to give me the same run around as they are giving reckedracing. what tests can i run myself to check if its my router, modem, or problem with the incomming signal/line?
reckedracing sorry for the jack but my internet is messed up and i figured this thread is alreadya bout messed up internet
reckedracing sorry for the jack but my internet is messed up and i figured this thread is alreadya bout messed up internet
lol
their phone message already says calls may be recorded so its only fair right
lol
and let me try to help you...
ping test can be run by going start -> run, then type cmd in the box...
this will open a dos command prompt
then type in ping yahoo.com -n 100
yahoo.com is a variable, you can use any site or IP address
no idea what -n is, but 100 is the number of times it tests
the results will show in the dos window
the main result you will be interested in is the 32ms or 64ms or 144ms
the lower the number the faster it is...
you can go to whatismyip.com or the network tools link above to find your IP
from what i understand you can run a ping to your IP which will ping from your machine to your cable modem, your return should say >10ms or <10ms, whatever is the less than symbol...
if it doesn;t say a low number then the problem is in your network...
if that number is fine but the yahoo.com ping is a high number then its prob your line...
i don;t know THAT much myself, but i hope this is all right and helps...
and no prob about thread jacking lol
edit: if your problem happens every few minutes then you should use 500 instead of 100 maybe for more of a time span for the test...
the end results will give you an average ms and a %lost... during your ping test if you lose your connection it will say request timed out, this is when you get the lost packets
their phone message already says calls may be recorded so its only fair right
lol
and let me try to help you...
ping test can be run by going start -> run, then type cmd in the box...
this will open a dos command prompt
then type in ping yahoo.com -n 100
yahoo.com is a variable, you can use any site or IP address
no idea what -n is, but 100 is the number of times it tests
the results will show in the dos window
the main result you will be interested in is the 32ms or 64ms or 144ms
the lower the number the faster it is...
you can go to whatismyip.com or the network tools link above to find your IP
from what i understand you can run a ping to your IP which will ping from your machine to your cable modem, your return should say >10ms or <10ms, whatever is the less than symbol...
if it doesn;t say a low number then the problem is in your network...
if that number is fine but the yahoo.com ping is a high number then its prob your line...
i don;t know THAT much myself, but i hope this is all right and helps...
and no prob about thread jacking lol
edit: if your problem happens every few minutes then you should use 500 instead of 100 maybe for more of a time span for the test...
the end results will give you an average ms and a %lost... during your ping test if you lose your connection it will say request timed out, this is when you get the lost packets
are you on a network or does your compputer go directly to the cable modem?
my ping results :
Pinging yahoo.com [216.109.112.135] with 32 bytes of data:
Reply from 216.109.112.135: bytes=32 time=78ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=63ms TTL=53
Request timed out.
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Request timed out.
Ping statistics for 216.109.112.135:
Packets: Sent = 100, Received = 89, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 78ms, Average = 31ms
Pinging yahoo.com [216.109.112.135] with 32 bytes of data:
Reply from 216.109.112.135: bytes=32 time=78ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=63ms TTL=53
Request timed out.
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=46ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=31ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Reply from 216.109.112.135: bytes=32 time=47ms TTL=53
Reply from 216.109.112.135: bytes=32 time=32ms TTL=53
Request timed out.
Ping statistics for 216.109.112.135:
Packets: Sent = 100, Received = 89, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 78ms, Average = 31ms
Originally posted by GSRCRXsi+Jan 20 2005, 03:49 PM-->
Not in Texas- only one party participating in the conversation has to give consent to record... so you can pretty much record anything that you're taking part in down here.
GSRCRXsi@Jan 20 2005, 04:29 PM
yea when i pinged my own ip i got 0ms
[post=448805]Quoted post[/post]
You always get 0ms when pinging yourself- otherwise something is seriously wrong.
looks like when it works it works great, but the lost packets are whats killing you
alright, i think my problem is fixed...
turns out the cable modem we had is not the best...
it was the original modem from when they started offering cable service in my area a few years back...
toshiba 1100... tech guy told me he saw the same problem last week and the modems lick donkey balls, swapped me out to a new rca modem and we seem to have fixed the problem...
so GSRCRXsi, what kinda of modem do you have and who;s your provider?
turns out the cable modem we had is not the best...
it was the original modem from when they started offering cable service in my area a few years back...
toshiba 1100... tech guy told me he saw the same problem last week and the modems lick donkey balls, swapped me out to a new rca modem and we seem to have fixed the problem...
so GSRCRXsi, what kinda of modem do you have and who;s your provider?
Battle Pope
Well-Known Member
Originally posted by Calesta+Jan 20 2005, 05:53 PM-->
Not in Texas- only one party participating in the conversation has to give consent to record... so you can pretty much record anything that you're taking part in down here.
GSRCRXsi
You always get 0ms when pinging yourself- otherwise something is seriously wrong.
[post=448877]Quoted post[/post]
there's no place like 127.0.0.1
Originally posted by reckedracing+Jan 21 2005, 10:58 AM-->
Interesting. I never had a problem with my Toshiba 1100. They are old though. Speaking of- I still have mine. Time Warner never took it back, and they never charged me for it. It's eBay time.
Battle Pope@Jan 21 2005, 11:00 AM
there's no place like 127.0.0.1
[post=449150]Quoted post[/post]
Or 192.168.x.x or 10.x.x.x or any of the other intranet reserved numbers...
hmmm, sorry but i'm all out of suggestions...
maybe check around online and see if other peopl had problem with that modem...
or else you;re kinda forced to call your provider...
if you route one comp directly to your modem before you call you can eliminate the hassle of them accussing you of having a bad network...
hmmm, so call your provider and tell them there is no router and you are having issues...
or tell them you have a router but unhooked it and are directly connected to the modem...
best of luck
or tell them you have a router but unhooked it and are directly connected to the modem...
best of luck
yea i called adelphia (my ISP) and they said to go to the local office and pick up a new modem free of charge. they ran some tests and they think it might be the modem. they said the modem i have is an old model. so im gonna go down there tomorrow and see how the new modem works out. they said if the new modem doesnt work then they will have to have someone come down and check out the lines. i hope its just the modem...
but a question. will me getting a new modem change my ip address? will that affect anything like my network or router settings?
but a question. will me getting a new modem change my ip address? will that affect anything like my network or router settings?
Your IP address might change, but the router and network settings should all remain the same. Your network is all behind the router, so it won't change at all. The router just wants to see an incoming connection, so it shouldn't care either.