Cable users: ping your default gateway please...

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
mobobuff

mobobuff

Lifer
Apr 5, 2004
11,099
1
81
Originally posted by: tec699
How can I ping my copnnection thru Windows XP?
Click to expand...

Start > Run > 'cmd'

type in the black box: ipconfig

look at the number after "Default gateway"

type: ping -t xxx.xxx.xxx.xxx

replace the x's with the default gateway.

Hold Ctrl+C when you want it to stop.
 
T

Trente

Golden Member
Apr 19, 2003
1,750
0
0
start->run->CMD, then click o.k.

type ipconfig then press enter.

X= IP address displayed next to default gateway.

type ping -n 25 X then press enter.
 
E

Eli

Super Moderator | Elite Member
Oct 9, 1999
50,419
8
81
Originally posted by: tec699
How can I ping my copnnection thru Windows XP?
Click to expand...
Go to Run, type in CMD

type in ipconfig

It will say Default Gateway ......... xxx.xxx.xxx.xxx

Ping the IP -n 25.

If you are behind a router, it will probably say 192.168.0.1 as your gateway. If that's the case, you'll have to look in your routers info to find it.

Go to(most likely) http://192.168.0.1

Enter your username/password(You do have a username/pw setup... right?).

Muck around until you find your current settings(IP address, subnet mask, gateway, dns, etc). For me, it's under a tab called Status.

:p
 
M

MaxDSP

Lifer
May 15, 2001
10,056
0
71
time=16ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time<10ms
time=16ms
time<10ms
time<10ms
time=16ms

Ping statistics for 67.x:
Packets: Sent = 25, Received = 25, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 16ms, Average = 8ms

Using Comcast 3mbps...
 
P

PlatinumGold

Lifer
Aug 11, 2000
23,168
0
71
Pinging 68.44.52.1 with 32 bytes of data:

Reply from 68.44.52.1: bytes=32 time=13ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=13ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=13ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=11ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=10ms TTL=64
Reply from 68.44.52.1: bytes=32 time=12ms TTL=64
Reply from 68.44.52.1: bytes=32 time=13ms TTL=64

Ping statistics for 68.44.52.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 13ms, Average = 11ms
 
P

psiu

Golden Member
Oct 1, 2003
1,629
1
0
Originally posted by: Trente
Well, here we have a protected box that can only be opened by the cable guy.

I'll check it later today/tomorrow and see if this gets worse during peak hours, will post resutls...

BTW, I also have a splitter in the house that is not needed now. should I try bypassing it by myself?

BTW no.2, take a look at this: http://img1.tapuz.co.il/forums/38556910.jpg Do these figures seem right?
Click to expand...

That's good signal, as far as the modem is concerned.
 
P

Pshawn5

Senior member
Aug 8, 2001
615
0
0
Pinging 66.27.20.1 with 32 bytes of data:

Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=13ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=11ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=10ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=10ms TTL=255
Reply from 66.27.20.1: bytes=32 time=8ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255
Reply from 66.27.20.1: bytes=32 time=6ms TTL=255
Reply from 66.27.20.1: bytes=32 time=7ms TTL=255

Ping statistics for 66.27.20.1:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 13ms, Average = 7ms


for roadrunner
 
N

nageov3t

Lifer
Feb 18, 2004
42,808
83
91
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

;)
 
B

beatmix01

Golden Member
Jun 22, 2001
1,008
1
0
i was just thinking how many people are pinging their local networks gateway as opposed to your ISP's gateway.
 
cronos

cronos

Diamond Member
Nov 7, 2001
9,380
26
101
Pinging 24.159.240.1 with 32 bytes of data:

Reply from 24.159.240.1: bytes=32 time=7ms TTL=254
Reply from 24.159.240.1: bytes=32 time=7ms TTL=254
Reply from 24.159.240.1: bytes=32 time=10ms TTL=254
Reply from 24.159.240.1: bytes=32 time=7ms TTL=254
Reply from 24.159.240.1: bytes=32 time=12ms TTL=254
Reply from 24.159.240.1: bytes=32 time=19ms TTL=254
Reply from 24.159.240.1: bytes=32 time=7ms TTL=254
Reply from 24.159.240.1: bytes=32 time=12ms TTL=254
Reply from 24.159.240.1: bytes=32 time=15ms TTL=254
Reply from 24.159.240.1: bytes=32 time=9ms TTL=254
Reply from 24.159.240.1: bytes=32 time=13ms TTL=254
Reply from 24.159.240.1: bytes=32 time=6ms TTL=254
Reply from 24.159.240.1: bytes=32 time=11ms TTL=254
Reply from 24.159.240.1: bytes=32 time=10ms TTL=254
Reply from 24.159.240.1: bytes=32 time=8ms TTL=254
Reply from 24.159.240.1: bytes=32 time=7ms TTL=254
Reply from 24.159.240.1: bytes=32 time=30ms TTL=254
Reply from 24.159.240.1: bytes=32 time=8ms TTL=254
Reply from 24.159.240.1: bytes=32 time=9ms TTL=254
Reply from 24.159.240.1: bytes=32 time=22ms TTL=254
Reply from 24.159.240.1: bytes=32 time=9ms TTL=254
Reply from 24.159.240.1: bytes=32 time=15ms TTL=254
Reply from 24.159.240.1: bytes=32 time=8ms TTL=254
Reply from 24.159.240.1: bytes=32 time=9ms TTL=254
Reply from 24.159.240.1: bytes=32 time=9ms TTL=254
 
E

Eli

Super Moderator | Elite Member
Oct 9, 1999
50,419
8
81
Originally posted by: beatmix01
i was just thinking how many people are pinging their local networks gateway as opposed to your ISP's gateway.
Click to expand...
Hopefully nobody here is stupid enough to do that, and if they are, those're some slowass LANs!

Ping statistics for 192.168.0.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

lol
 
The Stigenator

The Stigenator

Lifer
Oct 9, 1999
15,216
3
81
Pinging 24.10.40.1 with 32 bytes of data:

Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=115ms TTL=254
Reply from 24.10.40.1: bytes=32 time=17ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=41ms TTL=254
Reply from 24.10.40.1: bytes=32 time=15ms TTL=254
Reply from 24.10.40.1: bytes=32 time=72ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=32ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=25ms TTL=254
Reply from 24.10.40.1: bytes=32 time=14ms TTL=254
Reply from 24.10.40.1: bytes=32 time=51ms TTL=254
Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=16ms TTL=254
Reply from 24.10.40.1: bytes=32 time=13ms TTL=254

Ping statistics for 24.10.40.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 115ms, Average = 31ms
 
E

Eli

Super Moderator | Elite Member
Oct 9, 1999
50,419
8
81
Originally posted by: TheGoodGuy
Pinging 24.10.40.1 with 32 bytes of data:

Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=115ms TTL=254
Reply from 24.10.40.1: bytes=32 time=17ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=41ms TTL=254
Reply from 24.10.40.1: bytes=32 time=15ms TTL=254
Reply from 24.10.40.1: bytes=32 time=72ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=32ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=25ms TTL=254
Reply from 24.10.40.1: bytes=32 time=14ms TTL=254
Reply from 24.10.40.1: bytes=32 time=51ms TTL=254
Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=16ms TTL=254
Reply from 24.10.40.1: bytes=32 time=13ms TTL=254

Ping statistics for 24.10.40.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 115ms, Average = 31ms
Click to expand...
Ouch.
 
T

Trente

Golden Member
Apr 19, 2003
1,750
0
0
What the hell is going on around here?

Most people get stable ping results while others get these kind of results...

time=33ms
time=14ms
time=6ms
time=7ms
time=17ms
time=9ms
time=28ms
time=18ms
time=9ms
time=8ms
time=7ms
time=15ms
time=15ms
time=38ms
time=16ms
time=5ms
time=5ms
time=6ms
time=6ms
time=7ms
time=6ms
time=8ms
time=6ms
time=10ms
time=24ms

damn...
 
T

tm37

Lifer
Jan 24, 2001
12,436
1
0
Originally posted by: loki8481
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

;)
Click to expand...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DAD>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : clarkconnect.lan
IP Address. . . . . . . . . . . . : 192.168.1.252
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

C:\Documents and Settings\DAD>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 53, Received = 53, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
:D
 
N

ndee

Lifer
Jul 18, 2000
12,680
1
0
ok, I don't get this thread. What does pinging your gateway has to do with cable?!
 
Twista

Twista

Diamond Member
Jun 19, 2003
9,646
1
0
with 32 bytes of data:

C:\Documents and Settings\fuckyou>ping xxxxxxxx -n 25

Pinging xxxxxxxx with 32 bytes of data:

Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=20ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time<10ms TTL=64
Reply from: bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=20ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=10ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from : bytes=32 time=20ms TTL=64
Reply from bytes=32 time=10ms TTL=64
Reply from bytes=32 time<10ms TTL=64
Reply from : bytes=32 time<10ms TTL=64
Reply from bytes=32 time=20ms TTL=64
Reply from bytes=32 time=11ms TTL=64

Ping statistics for
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 20ms, Average = 10ms




treaceryt





Tracing route to xxxxxxxxxxxxx
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms xxxxxxxxxxxxxxx

Trace complete.
 
N

NikPreviousAcct

No Lifer
Aug 15, 2000
52,763
1
0
Originally posted by: ndee
ok, I don't get this thread. What does pinging your gateway has to do with cable?!
Click to expand...

If you have a "slow" connection on cable, no cable company will take any ping results that are pinging anything beyond the gateway that you connect to. If your connection is/has a problem, then you'll see it there. If it's just fine but pinging, say, yahoo.com and everything else turns up with problems, it's not the ISP's problem and they'll tell you too bad.
 
N

NikPreviousAcct

No Lifer
Aug 15, 2000
52,763
1
0
--- 24.20.8.1 ping statistics ---
33 packets transmitted, 28 received, 15% packet loss, time 32029ms
rtt min/avg/max/mdev = 248.875/483.327/858.095/151.741 ms

...which reminds me, I need to call my ISP for even one single packetloss issue. That's why my connection is all fUx0r3d up.
 
N

ndee

Lifer
Jul 18, 2000
12,680
1
0
Originally posted by: Nik
Originally posted by: ndee
ok, I don't get this thread. What does pinging your gateway has to do with cable?!
Click to expand...

If you have a "slow" connection on cable, no cable company will take any ping results that are pinging anything beyond the gateway that you connect to. If your connection is/has a problem, then you'll see it there. If it's just fine but pinging, say, yahoo.com and everything else turns up with problems, it's not the ISP's problem and they'll tell you too bad.
Click to expand...

But that doesn't have anything to do with Cable or ADSL, does it? And what's the use if I ping MY default gateway when HE has a problem?
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom