Test my connection

Toggle sidebar Toggle sidebar
M

Marty

Banned
Oct 11, 1999
1,534
0
0
I'm considering running a server but don't know if I have the connection to do it. If you guys could try pinging 128.253.175.159 and letting me know what ping you get as well as where you are located/who your isp is.

Thanks

Marty
 
J

Jackhamr60504

Member
Nov 12, 2001
96
0
0
I got

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=41ms TTL=113
Reply from 128.253.175.159: bytes=32 time=43ms TTL=113
Reply from 128.253.175.159: bytes=32 time=41ms TTL=113
Reply from 128.253.175.159: bytes=32 time=43ms TTL=113

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 42ms

from an AT&T cable modem near Chicago... What kind of connection do you have?
 
Boonesmi

Boonesmi

Lifer
Feb 19, 2001
14,448
1
81
from:
birmingham, AL
bellsouth.net DSL


Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=110ms TTL=111
Reply from 128.253.175.159: bytes=32 time=95ms TTL=111
Reply from 128.253.175.159: bytes=32 time=110ms TTL=111
Reply from 128.253.175.159: bytes=32 time=120ms TTL=111

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 120ms, Average = 108ms

 
S

samgau

Platinum Member
Oct 11, 1999
2,403
0
0
Firewall here at work prevents pinging and traceroute accross the net... sucks big time...
 
jlee

jlee

Lifer
Sep 12, 2001
48,518
223
106
Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=137ms TTL=109
Reply from 128.253.175.159: bytes=32 time=68ms TTL=109
Reply from 128.253.175.159: bytes=32 time=60ms TTL=109
Reply from 128.253.175.159: bytes=32 time=60ms TTL=109

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 137ms, Average = 81ms


Gainesville, FL - BellSouth ADSL.
 
T

thorin

Diamond Member
Oct 9, 1999
7,573
0
0
Dude your TTL completely sucks:

U:\winnt>ping 128.253.175.159

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=50ms TTL=111
Reply from 128.253.175.159: bytes=32 time=40ms TTL=111
Reply from 128.253.175.159: bytes=32 time=60ms TTL=111
Reply from 128.253.175.159: bytes=32 time=40ms TTL=111

Company LAN (T1) in Onartio Canada.

For any newbs here's info on TTL :p :

"The Time To Live (TTL) field can be interesting. Every IP packet that gets sent out has a TTL field which is set to a relatively high number (in this case, ping packets get a TTL of 255). As the packet traverses the network, the TTL field gets decreased by one by each router it goes through; when the TTL drops to 0, the packet is discarded by the router. The IP spec says that the TTL should be set to 60 (though it's 255 for ping packets). The main purpose of this is so that a packet doesn't live forever on the network and will eventually die when it is deemed "lost."
But it can provide additional information. We can use the TTL to determine approximately how many router hops the packet has gone through. In this case it's 255 minus N hops, where N is the TTL of the returning Echo Replies. If the TTL field varies in successive pings, it could indicate that the successive reply packets are going via different routes, which isn't a great thing."

U:\winnt>tracert 128.253.175.159

Tracing route to mfs24.resnet.cornell.edu [128.253.175.159]
over a maximum of 30 hops:

[Inner company hops 1 thru 3 surpressed, all of these came in at <10ms]
4 10 ms 30 ms 50 ms core1-ott-POS4-1.bb.attcanada.ca [216.191.225.1]
5 10 ms 20 ms 80 ms core1-tor-POS8-1.bb.attcanada.ca [216.191.65.177]
6 40 ms 20 ms 70 ms gwy1-tor-SRP2-0.bb.attcanada.ca [216.191.65.243]
7 30 ms 10 ms 80 ms 12.125.142.5
8 80 ms 50 ms 30 ms gbr5-p80.cgcil.ip.att.net [12.123.5.218]
9 30 ms 40 ms 111 ms tbr1-p013501.cgcil.ip.att.net [12.122.11.41]
10 * * * Request timed out.
11 60 ms 80 ms 90 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
12 30 ms 70 ms 90 ms gar1-p360.n54ny.ip.att.net [12.123.1.129]
13 30 ms 80 ms 81 ms 12.125.51.210
14 70 ms 80 ms 80 ms at-gsr1-nyc-1-0-OC12.appliedtheory.net [169.130.3.30]
15 40 ms 60 ms 80 ms at-gsr1-syr-3-0-OC12.appliedtheory.net [169.130.3.42]
16 60 ms 60 ms 60 ms at-gsr2-syr-1-2-cornelluniv-1.appliedtheory.net [169.130.253.6]
17 40 ms 81 ms 80 ms mcfad1-8540-vl7.cit.cornell.edu [128.253.222.149]
18 40 ms 70 ms 90 ms mfs24.resnet.cornell.edu [128.253.175.159]

Trace complete.


Thorin
 
W

WyteWatt

Banned
Jun 8, 2001
6,255
0
0
Reply from 128.253.175.159: bytes=32 time=61ms TTL=108
Reply from 128.253.175.159: bytes=32 time=50ms TTL=108
Reply from 128.253.175.159: bytes=32 time=60ms TTL=108
Reply from 128.253.175.159: bytes=32 time=50ms TTL=108

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 61ms, Average = 55ms

On Cox.net new cable modem network! Not bad at all for your pings.

 
I

Informant X

Senior member
Jan 18, 2000
840
1
81
Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=7ms TTL=123
Reply from 128.253.175.159: bytes=32 time=7ms TTL=123
Reply from 128.253.175.159: bytes=32 time=7ms TTL=123
Reply from 128.253.175.159: bytes=32 time=7ms TTL=123

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

MasterHoss

Platinum Member
Apr 25, 2001
2,323
0
0
damn. I need to talk to my network administrator. I used to be able to ping away as I pleased.... oh well

OC-3 .... nice (how much was it)
 
T

thorin

Diamond Member
Oct 9, 1999
7,573
0
0
Informant X
"And what's TTL anywho? "

Heh....I included that in my post above yours. Try reading the thread next time :p

Thorin
 
Z

zippy

Diamond Member
Nov 10, 1999
9,998
1
0
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\XXXXXXXXXXXX>ping 128.253.175.159

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=374ms TTL=113
Reply from 128.253.175.159: bytes=32 time=395ms TTL=113
Reply from 128.253.175.159: bytes=32 time=267ms TTL=113
Reply from 128.253.175.159: bytes=32 time=484ms TTL=113

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 484ms, Average = 380ms

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\XXXXXXXXXXXXXXXXx>ping 128.253.175.159

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=502ms TTL=113
Reply from 128.253.175.159: bytes=32 time=137ms TTL=113
Reply from 128.253.175.159: bytes=32 time=95ms TTL=113
Reply from 128.253.175.159: bytes=32 time=72ms TTL=113

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 502ms, Average = 201ms

C:\DOCUME~1\XXXXXXXXXXXXXX>ping 128.253.175.159

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=584ms TTL=113
Reply from 128.253.175.159: bytes=32 time=142ms TTL=113
Reply from 128.253.175.159: bytes=32 time=63ms TTL=113
Reply from 128.253.175.159: bytes=32 time=392ms TTL=113

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 584ms, Average = 295ms
______________________________________________________
I'm in NY state with Time Warner RoadRunner cable.
 
T

thevillageinn

Member
Jan 16, 2002
71
0
0
Southern California, T1 from Sprint, over company network.

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=90ms TTL=116
Reply from 128.253.175.159: bytes=32 time=90ms TTL=116
Reply from 128.253.175.159: bytes=32 time=90ms TTL=116
Reply from 128.253.175.159: bytes=32 time=90ms TTL=116

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

C:\>

Here's my connection at home...RoadRunner cable from Time Warner, also in Southern California

Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=85ms TTL=109
Reply from 128.253.175.159: bytes=32 time=84ms TTL=109
Reply from 128.253.175.159: bytes=32 time=98ms TTL=109
Reply from 128.253.175.159: bytes=32 time=86ms TTL=109

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 98ms, Average = 88ms

C:\>
 
M

Marty

Banned
Oct 11, 1999
1,534
0
0
Hmmm, some of the pings seem encouraging, but the TTL does look bad. Any judgement on whether or not I could run a decent server based on these results?

Marty
 
M

Marty

Banned
Oct 11, 1999
1,534
0
0
BTW, how accurate is the TTL number? I'm only asking because I'm getting some wierd results.

C:\>ping www.rit.edu

Pinging ase-web.rit.edu [129.21.2.233] with 32 bytes of data:

Reply from 129.21.2.233: bytes=32 time<10ms TTL=59
Reply from 129.21.2.233: bytes=32 time<10ms TTL=59
Reply from 129.21.2.233: bytes=32 time<10ms TTL=59
Reply from 129.21.2.233: bytes=32 time<10ms TTL=59

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

C:\>tracert www.rit.edu

Tracing route to ase-web.rit.edu [129.21.2.233]
over a maximum of 30 hops:

1 16 ms <10 ms <10 ms mcfad2-8540-vl548.cit.cornell.edu [128.253.175.132]
2 <10 ms <10 ms <10 ms cornellnet3-gig2-0-0.cit.cornell.edu [132.236.222.161]
3 <10 ms <10 ms 16 ms 199.109.1.250
4 <10 ms <10 ms 16 ms core1-9-2.rit.edu [129.21.8.117]
5 <10 ms <10 ms 16 ms core1m.rit.edu [129.21.7.150]
6 <10 ms <10 ms 16 ms ase-web.isc.rit.edu [129.21.2.233]

Trace complete.

C:\>

I get a really low TTL with an extremely low ping. What's the deal?

Marty
 
M

Mavrick007

Diamond Member
Dec 19, 2001
3,198
0
0
TTL=110
TTL=110
TTL=110
TTL=110

Minimum = 57ms, Maximum = 58ms, Average = 57ms

NB, Canada on ADSL
 
D

DSTA

Senior member
Sep 26, 2001
431
0
0
Avg. ping of around 330, TTL 108 (ISDN, Germany)

BTW you might think of installing some kind of firewall, as it is you've got at least port 135 and 445 open.

 
B

Barnaby W. Füi

Elite Member
Aug 14, 2001
12,343
0
0
c1816619-b:/home/death# ping -c 16 128.253.175.159
PING 128.253.175.159 (128.253.175.159): 56 data bytes
64 bytes from 128.253.175.159: icmp_seq=0 ttl=111 time=49.0 ms
64 bytes from 128.253.175.159: icmp_seq=1 ttl=111 time=45.1 ms
64 bytes from 128.253.175.159: icmp_seq=2 ttl=111 time=47.2 ms
64 bytes from 128.253.175.159: icmp_seq=3 ttl=111 time=45.9 ms
64 bytes from 128.253.175.159: icmp_seq=4 ttl=111 time=47.6 ms
64 bytes from 128.253.175.159: icmp_seq=5 ttl=111 time=52.3 ms
64 bytes from 128.253.175.159: icmp_seq=6 ttl=111 time=45.3 ms
64 bytes from 128.253.175.159: icmp_seq=7 ttl=111 time=45.1 ms
64 bytes from 128.253.175.159: icmp_seq=8 ttl=111 time=57.8 ms
64 bytes from 128.253.175.159: icmp_seq=9 ttl=111 time=47.7 ms
64 bytes from 128.253.175.159: icmp_seq=10 ttl=111 time=45.3 ms
64 bytes from 128.253.175.159: icmp_seq=11 ttl=111 time=52.9 ms
64 bytes from 128.253.175.159: icmp_seq=12 ttl=111 time=47.1 ms
64 bytes from 128.253.175.159: icmp_seq=13 ttl=111 time=51.9 ms
64 bytes from 128.253.175.159: icmp_seq=14 ttl=111 time=62.0 ms
64 bytes from 128.253.175.159: icmp_seq=15 ttl=111 time=48.7 ms

--- 128.253.175.159 ping statistics ---
16 packets transmitted, 16 packets received, 0% packet loss
round-trip min/avg/max = 45.1/49.4/62.0 ms
 
S

Strych9

Golden Member
May 5, 2000
1,614
0
76
Reply from 128.253.175.159: bytes=32 time=100ms TTL=108
Reply from 128.253.175.159: bytes=32 time=91ms TTL=108
Reply from 128.253.175.159: bytes=32 time=93ms TTL=108
Reply from 128.253.175.159: bytes=32 time=93ms TTL=108

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 100ms, Average = 94ms

AT&T Broadband, Fresno, CA
 
HalfCrazy

HalfCrazy

Senior member
Oct 3, 2001
853
0
0
Pinging 128.253.175.159 with 32 bytes of data:

Reply from 128.253.175.159: bytes=32 time=170ms TTL=111
Reply from 128.253.175.159: bytes=32 time=150ms TTL=111
Reply from 128.253.175.159: bytes=32 time=150ms TTL=111
Reply from 128.253.175.159: bytes=32 time=150ms TTL=111

Ping statistics for 128.253.175.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 150ms, Maximum = 170ms, Average = 155ms

Alger, OH Wcoil.com 56k

Cable or dsl is not available here yet. :(
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom