Forum Home
Press F1
Thread ID: 81024	2007-07-13 03:05:00	inconsistant pings with Cable	KLL (12551)	Press F1

Post ID	Timestamp	Content	User
568686	2007-07-13 03:05:00	I don't get it, I'm constantly getting inconstant pings with (TC) cable that does not go away until about 11pm at night. I have rang TC multiple times and in fact, two techies have come along and they have only fixed it temporarily and then a few days later, it comes back again: An example: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Karl>tracert www.trademe.co.nz Tracing route to www.trademe.co.nz [202.21.128.2] over a maximum of 30 hops: 1 84 ms 32 ms 91 ms 121-72-229-1.cable.telstraclear.net [121.72.229. 1] 2 152 ms 102 ms 84 ms ge-1-0-947.u32.telstraclear.net [218.101.61.74] 3 29 ms 102 ms 82 ms ge-1-3-0-957.ie1.telstraclear.net [218.101.61.69 ] 4 130 ms 282 ms 89 ms ge-4-0-819.u22.telstraclear.net [203.98.23.2] 5 106 ms 144 ms 102 ms 203.167.225.19 6 87 ms 115 ms 168 ms www.trademe.co.nz [202.21.128.2] Trace complete. C:\Documents and Settings\Karl>ping -n 20 trademe.co.nz Pinging trademe.co.nz [203.57.145.2] with 32 bytes of data: Reply from 203.57.145.2: bytes=32 time=49ms TTL=60 Reply from 203.57.145.2: bytes=32 time=31ms TTL=60 Reply from 203.57.145.2: bytes=32 time=22ms TTL=60 Reply from 203.57.145.2: bytes=32 time=44ms TTL=60 Reply from 203.57.145.2: bytes=32 time=98ms TTL=60 Reply from 203.57.145.2: bytes=32 time=33ms TTL=60 Reply from 203.57.145.2: bytes=32 time=60ms TTL=60 Reply from 203.57.145.2: bytes=32 time=31ms TTL=60 Reply from 203.57.145.2: bytes=32 time=25ms TTL=60 Reply from 203.57.145.2: bytes=32 time=20ms TTL=60 Reply from 203.57.145.2: bytes=32 time=66ms TTL=60 Reply from 203.57.145.2: bytes=32 time=28ms TTL=60 Reply from 203.57.145.2: bytes=32 time=27ms TTL=60 Reply from 203.57.145.2: bytes=32 time=43ms TTL=60 Reply from 203.57.145.2: bytes=32 time=71ms TTL=60 Reply from 203.57.145.2: bytes=32 time=83ms TTL=60 Reply from 203.57.145.2: bytes=32 time=149ms TTL=60 Reply from 203.57.145.2: bytes=32 time=35ms TTL=60 Reply from 203.57.145.2: bytes=32 time=78ms TTL=60 Reply from 203.57.145.2: bytes=32 time=70ms TTL=60 Ping statistics for 203.57.145.2: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 149ms, Average = 53ms C:\Documents and Settings\Karl>tracert paradise.net.nz Tracing route to paradise.net.nz [203.96.152.127] over a maximum of 30 hops: 1 * 162 ms 100 ms 121-72-229-1.cable.telstraclear.net [121.72.229. 1] 2 67 ms 23 ms 34 ms ge-1-0-947.u32.telstraclear.net [218.101.61.74] 3 74 ms 77 ms 26 ms ge-1-3-0-957.ie1.telstraclear.net [218.101.61.69 ] 4 45 ms 182 ms 62 ms ge-4-0-819.u22.telstraclear.net [203.98.23.2] 5 67 ms 108 ms 111 ms 203.167.209.100 6 98 ms 62 ms 132 ms www.paradise.net.nz [203.96.152.127] Trace complete. C:\Documents and Settings\Karl>ping -n 15 www.paradise.net.nz Pinging www.paradise.net.nz [203.96.152.127] with 32 bytes of data: Reply from 203.96.152.127: bytes=32 time=42ms TTL=123 Reply from 203.96.152.127: bytes=32 time=188ms TTL=123 Reply from 203.96.152.127: bytes=32 time=60ms TTL=123 Reply from 203.96.152.127: bytes=32 time=70ms TTL=123 Reply from 203.96.152.127: bytes=32 time=80ms TTL=123 Reply from 203.96.152.127: bytes=32 time=148ms TTL=123 Reply from 203.96.152.127: bytes=32 time=107ms TTL=123 Reply from 203.96.152.127: bytes=32 time=78ms TTL=123 Reply from 203.96.152.127: bytes=32 time=152ms TTL=123 Reply from 203.96.152.127: bytes=32 time=79ms TTL=123 Reply from 203.96.152.127: bytes=32 time=114ms TTL=123 Reply from 203.96.152.127: bytes=32 time=80ms TTL=123 Reply from 203.96.152.127: bytes=32 time=88ms TTL=123 Reply from 203.96.152.127: bytes=32 time=86ms TTL=123 Reply from 203.96.152.127: bytes=32 time=115ms TTL=123 Ping statistics for 203.96.152.127: Packets: Sent = 15, Received = 15, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 188ms, Average = 99ms My friends have cable in different parts of Chch and this is not a problem for them. I'm guessing this is a fault (***!) but is there anything at my end I can do? I can provide more details if needed thanks.	KLL (12551)
568687	2007-07-13 10:33:00	bump..please help :)	KLL (12551)
568688	2007-07-13 22:57:00	Can you tell us exactly what the problem is... given that it's pretty normal to have inconsistent ping times to any website, using cable or whatever.	Greg (193)
568689	2007-07-14 07:13:00	Cable does not equal perfectly consistent ping times or anything. What if the servers had crashed on the other end? Or every single person in the world wanted to go to that website? In any case, cable wouldn't make any difference. Just be happy you have cable while we stick it out with normal DSL or Wireless:D	beeswax34 (63)
1