PING

RA-1972 · Mar 06, 2008, 22:32:30

Has any one notice there pings have doubled since yesterday or is it just mine , on gw5 .

Simon · Mar 06, 2008, 22:51:21

Umm... haven't checked. I don't, often. Want us to ping somewhere for you?

Rik · Mar 07, 2008, 00:47:30

Pings normal here, eg 24ms to the BBC.

Gary · Mar 07, 2008, 08:43:44

Mine are Ok, Gw5 I was informed is what most people are on, the one Rik and a few others use is a much older one and only a few are on that, so the "is it Gw5" idea is a red herring of sorts, that's from IDNet towers

Rik · Mar 07, 2008, 09:26:15

I'd agree, Gary, we're the dinosaurs around here.

Gary · Mar 07, 2008, 09:28:35

Quote from: Rik on Mar 07, 2008, 09:26:15
I'd agree, Gary, we're the dinosaurs around here.

But Dinosaurs with great knowledge Rik

Rik · Mar 07, 2008, 09:38:02

I'm just wondering when my sell-by date is.

Gary · Mar 07, 2008, 09:39:02

Quote from: Rik on Mar 07, 2008, 09:38:02
I'm just wondering when my sell-by date is.

Don't tell Sue

Rik · Mar 07, 2008, 09:45:29

She's probably read the label already, Gary.

Gary · Mar 07, 2008, 09:47:22

Quote from: Rik on Mar 07, 2008, 09:45:29
She's probably read the label already, Gary.

I have the feeling Justina has done the same

Philip · Mar 07, 2008, 09:51:24

C:\Documents and Settings\Administrator>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.251.202] with 32 bytes of data:

Reply from 212.58.251.202: bytes=32 time=32ms TTL=248
Reply from 212.58.251.202: bytes=32 time=33ms TTL=248
Reply from 212.58.251.202: bytes=32 time=32ms TTL=248
Reply from 212.58.251.202: bytes=32 time=35ms TTL=248

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

C:\Documents and Settings\Administrator>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.251.202]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 30 ms 32 ms 39 ms telehouse-gw2.idnet.net [212.69.63.55]
3 38 ms 30 ms 37 ms telehouse-gw3-gi0-1-400.idnet.net [212.
]
4 38 ms 50 ms 33 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91
5 78 ms 32 ms 32 ms 212.58.238.133
6 175 ms 203 ms 144 ms 212.58.239.58
7 33 ms 32 ms 32 ms www2.telhc.bbc.co.uk [212.58.251.202]

heres my results if they are any use

Rik · Mar 07, 2008, 09:56:30

I take it you have interleaving on, Philip?

Philip · Mar 07, 2008, 09:57:30

Quote from: Rik on Mar 07, 2008, 09:56:30
I take it you have interleaving on, Philip?

yes, are they ok?

Rik · Mar 07, 2008, 10:06:01

Bit slower than mine, but ping times increase the further you are away from London, and also depending on how 'deep' your interleaving is, mine seems to the at the lightest level. At less than 1/100th second difference, I doubt either of us would notice, Philip.

Gary · Mar 07, 2008, 10:12:02

C:\Documents and Settings\xxxx>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:

Reply from 212.58.224.131: bytes=32 time=33ms TTL=121
Reply from 212.58.224.131: bytes=32 time=31ms TTL=121
Reply from 212.58.224.131: bytes=32 time=32ms TTL=121
Reply from 212.58.224.131: bytes=32 time=32ms TTL=121

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

Actually mine are a tad slower now, was about 23ms the other day $:-\$

Philip · Mar 07, 2008, 10:13:30

I'm happy enough with the performance

Gary · Mar 07, 2008, 10:15:23

I'm not worried, it does vary, I think BT have Hoobs working at my exchange

ducky22 · Mar 07, 2008, 14:42:00

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.0.1
2 48 ms 43 ms 39 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 43 ms 39 ms 36 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 43 ms 40 ms 41 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 34 ms 31 ms 33 ms 212.58.238.133
6 43 ms 43 ms 47 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 41 ms 45 ms 50 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 47 ms 47 ms 49 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 39 ms 39 ms 37 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 50 ms 43 ms 37 ms 212.58.238.133
6 51 ms 53 ms 49 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

M:\>

Interleaving disabled... Something odd, I even just turned off everything on the network and still have high pings. Odd.

Rik · Mar 07, 2008, 15:05:49

Mine look normal, one rogue ping though:

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.251.207]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 24 ms 57 ms 25 ms telehouse-gw2.idnet.net [212.69.63.55]
3 25 ms 25 ms 25 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 23 ms 23 ms 25 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 23 ms 25 ms 23 ms 212.58.238.133
6 27 ms 25 ms 25 ms 212.58.239.58
7 25 ms 23 ms 25 ms www5.telhc.bbc.co.uk [212.58.251.207]

Trace complete.

ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.251.207] with 32 bytes of data:

Reply from 212.58.251.207: bytes=32 time=25ms TTL=248
Reply from 212.58.251.207: bytes=32 time=24ms TTL=248
Reply from 212.58.251.207: bytes=32 time=47ms TTL=248
Reply from 212.58.251.207: bytes=32 time=24ms TTL=248

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

ducky22 · Mar 07, 2008, 15:14:01

Forgot to mention am also on gw5.

Rik · Mar 07, 2008, 15:18:26

Most people are, of course...

ducky22 · Mar 07, 2008, 15:21:25

Quote from: Rik on Mar 07, 2008, 15:18:26
Most people are, of course...

Yeah... all the IDNet noobies. hehe.

Rik · Mar 07, 2008, 15:22:47

Not just them, I can be too.

paulsmith109 · Mar 07, 2008, 15:45:18

Try dropping and then re-establishing PPP a few times, checking ping results on each reconnection. I have seen pings of 30ms or higher on some sessions, but on my current session (had to try 4 attempts at this) I have now achieved a steady ping of 12ms to www.idnet.net
Try it and see what happens - you have nothing to lose!
BTW, I also connect via gw5 - could the gateway be the culprit?

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Paul Smith>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 12 ms 11 ms 11 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 12 ms 12 ms 11 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
4 12 ms 12 ms 11 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 12 ms 12 ms 12 ms 212.69.63.209
6 12 ms 12 ms 12 ms www.idnet.net [212.69.36.10]

Trace complete.
C:\Users\Paul Smith>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59

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

Quote from: ducky22 on Mar 07, 2008, 14:42:00
M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.0.1
2 48 ms 43 ms 39 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 43 ms 39 ms 36 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 43 ms 40 ms 41 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 34 ms 31 ms 33 ms 212.58.238.133
6 43 ms 43 ms 47 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 41 ms 45 ms 50 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 47 ms 47 ms 49 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 39 ms 39 ms 37 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 50 ms 43 ms 37 ms 212.58.238.133
6 51 ms 53 ms 49 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

M:\>

Interleaving disabled... Something odd, I even just turned off everything on the network and still have high pings. Odd.

Rik · Mar 07, 2008, 15:47:44

Have you contacted support with your results?

paulsmith109 · Mar 07, 2008, 15:51:41

Quote from: Rik on Mar 07, 2008, 15:47:44
Have you contacted support with your results?

I sent an email, they looked into it and found no obvious network problems at their end.

Rik · Mar 07, 2008, 16:12:12

Quote from: ducky22 on Mar 07, 2008, 14:42:00
Interleaving disabled... Something odd, I even just turned off everything on the network and still have high pings. Odd.

Do you run a server, Ducky?

Rik · Mar 07, 2008, 16:13:21

Quote from: paulsmith109 on Mar 07, 2008, 15:51:41
I sent an email, they looked into it and found no obvious network problems at their end.

I'm certainly not seeing anything odd myself, I did a 24 ping test recently, and other than the odd rogue, they were all comfortably in my 'normal' range.

RA-1972 · Mar 07, 2008, 18:50:59

What happen was the other night gameing with a mate (diff exchange then me ) pings where fine and all ok getting about 20 ping and then 12.10 am lost ppp session , so turn comp off and went to bed , last night connection was back on but pings have doubled to between 40 & 50 , so i think it could be the exchange might have done some work , maybe .

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

C:\Documents and Settings\>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data

Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59

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

C:\Documents and Settings\nathan stone>

router settings . Software Version: 1.09
ADSL Version: 6.0.2.0
Boot Code Version: 0.01
MAC Address: 00-1C-10-00-EB-35

DSL Status

DSL Status: UP
DSL Modulation Mode: Auto
DSL Path Mode: FAST
Downstream Rate: 8128 Kbps
Upstream Rate: 448 Kbps
Downstream Margin: 12 db
Upstream Margin: 25 db
Downstream Line Attenuation: 21
Upstream Line Attenuation: 24
Downstream Transmit Power: 19
Upstream Transmit Power: 11
LOS Errors: 0

Rik · Mar 07, 2008, 18:55:29

The work BT are doing does cause a loss of PPP for a few minutes between 00:00-06:00, so it may have been that. It shouldn't be extending pings unless they are introducing a new hop or two, how many steps do you get on a tracert to idnet? This is mine:

tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 27 ms 23 ms 25 ms telehouse-gw2.idnet.net [212.69.63.55]
3 25 ms 23 ms 23 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
4 31 ms 23 ms 25 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 25 ms 25 ms 25 ms 212.69.63.209
6 25 ms 25 ms 27 ms www.idnet.net [212.69.36.10]

Trace complete.

RA-1972 · Mar 07, 2008, 19:00:38

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

C:\Documents and Settings\nathan stone>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 234 ms 53 ms 41 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 50 ms 50 ms 46 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 41 ms 40 ms 44 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 41 ms 42 ms 42 ms 212.69.63.225
6 42 ms 41 ms 41 ms www.idnet.net [212.69.36.10]

Trace complete.

Rik · Mar 07, 2008, 19:03:49

It does look like the extra time is taken in reaching IDNet, ie in BT's network. How far are you from London? Is interleaving on?

RA-1972 · Mar 07, 2008, 19:05:42

fast path mode , and about 170 miles from london .

Rik · Mar 07, 2008, 19:07:19

I'm interleaved and 50 miles. It might be worth running a few tracerts over the weekend and letting IDNet have them if things haven't settled down. Your line is fine, full sync with headroom on the noise margin (I should have realised you weren't interleaved from that

).

RA-1972 · Mar 07, 2008, 19:08:53

lol it is gatting late mate .

will do rik thanks for the help .

Rik · Mar 07, 2008, 19:09:59

NP.

Incidentally, it shows how accurate the speed tester is at working out distance.

RA-1972 · Mar 07, 2008, 19:11:35

Yeah but doesnt the speed tester work it out from the ident servers and not where i live ? maybe .

Rik · Mar 07, 2008, 19:16:12

It's possible, though it seems to give different distances to people. I don't trust speed testers anyway.

RA-1972 · Mar 07, 2008, 19:18:48

My speed is still good just done speed test , peak time aswell

Rik · Mar 07, 2008, 19:20:52

Try the Maidenhead server - that's often faster.

RA-1972 · Mar 07, 2008, 19:28:45

nope little bit slower .

Rik · Mar 07, 2008, 19:29:25

You must the the exception that proved the rule.

Still, it did improve the ping!

Cookiemonster · Mar 07, 2008, 19:29:47

Better ping though

Rik · Mar 07, 2008, 19:37:35

Which demonstrates perfectly what a crude tool the ping is.

ducky22 · Mar 08, 2008, 01:58:57

Quote from: Rik on Mar 07, 2008, 16:12:12
Do you run a server, Ducky?

I do but only an SSL page is accessible externally and I yanked the ethernet cable out anyway for 10mins before I tested.

Latency is still a lot higher that it used to be which was around 22-24ms. Line is definitely fastpath.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 32 ms 36 ms 40 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 28 ms 31 ms 27 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 42 ms 40 ms 50 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 50 ms 52 ms 49 ms 212.58.238.133
6 41 ms 45 ms 36 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

Rik · Mar 08, 2008, 09:36:32

Let support have some tracerts/pings, see if they can spot anything.

ducky22 · Mar 08, 2008, 14:09:36

Things seem to have improved... which either means IDNet/BT found something and fixed it, or it was the result of congestion. I am on a 'red' congested exchange but already on supermax because of this. :-(.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 30 ms 32 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 24 ms 24 ms 31 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 24 ms 25 ms 25 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 34 ms 41 ms 39 ms 212.58.238.133
6 25 ms 27 ms 28 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

M:\>tracert jolt.co.uk

Tracing route to jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 27 ms 26 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 23 ms 23 ms 24 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 33 ms 28 ms 28 ms g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
5 26 ms 28 ms 24 ms v3952.cr05.tn5.bb.pipex.net [62.72.137.9]
6 36 ms 57 ms 44 ms g2-48-5.ar01.tn5.bb.pipex.net [62.72.140.14]
7 26 ms 28 ms 25 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 25 ms 27 ms 25 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.

RA-1972 · Mar 08, 2008, 14:46:36

tracert www.jolt.co.uk

Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 46 ms 40 ms 43 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 40 ms 41 ms 40 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 41 ms 40 ms 42 ms g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
5 42 ms 40 ms 44 ms v3952.cr05.tn5.bb.pipex.net [62.72.137.9]
6 43 ms 40 ms 40 ms g2-48-5.ar01.tn5.bb.pipex.net [62.72.140.14]
7 42 ms 41 ms 40 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 41 ms 42 ms 45 ms www.jolt.co.uk [82.133.85.65]

Trace complete.

tracert www.bbc.co.uk

Tracing route to www.bbc.co.uk [212.58.253.73]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 40 ms 41 ms 39 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 40 ms 39 ms 40 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 40 ms 45 ms 40 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 41 ms 40 ms 41 ms 212.58.238.133
6 43 ms 41 ms 41 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
7 42 ms 42 ms 41 ms www.bbc.net.uk [212.58.253.73]

Trace complete.

Edit: Personal information removed.

paulsmith109 · Mar 09, 2008, 09:29:20

Still looking good here!

C:\Users\Paul Smith>ping www.jolt.co.uk

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=11ms TTL=59
Reply from 82.133.85.65: bytes=32 time=11ms TTL=59
Reply from 82.133.85.65: bytes=32 time=11ms TTL=59
Reply from 82.133.85.65: bytes=32 time=12ms TTL=59

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

C:\Users\Paul Smith>tracert www.jolt.co.uk

Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.2.1]
2 11 ms 12 ms 12 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 11 ms 12 ms 11 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
4 13 ms 11 ms 11 ms g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
5 12 ms 12 ms 12 ms v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
6 11 ms 10 ms 11 ms g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
7 13 ms 11 ms 11 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14
8 13 ms 12 ms 13 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.

RA-1972 · Mar 11, 2008, 18:32:30

I spoke to support ref my ping looks like a BT fault me sycn is still maxed . DOH !!! good old bt .
Test1 comprises of Best Effort Test: -provides background information.
IP profile for your line is - 7150 kbps
DSL connection rate: 448 kbps(UP-STREAM) 8128 kbps(DOWN-STREAM)
Actual IP throughput achieved during the test was - 6550 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or
websites please contact your ISP for assistance.

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

C:\Documents and Settings\tracert idnet.net

Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 48 ms 41 ms 43 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 41 ms 42 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 41 ms 42 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 42 ms 41 ms 47 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 40 ms 41 ms 41 ms idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\ .

So me pings are still high have to wait and see. I do alot gameing i can handle it but hopefully they will come back down .

P.S Longer ethernet cable wouldnt effect ping would it ?

Rik · Mar 11, 2008, 18:42:55

No, the ethernet cable would have an effect, but I doubt it could be measured with anything less than an atomic clock.

It looks like you have interleaving on to me, did IDNet say?

RA-1972 · Mar 11, 2008, 18:46:56

Nope off .

Software Version: 1.09
ADSL Version: 6.0.2.0
Boot Code Version: 0.01
MAC Address: 00-1C-10-00-EB-35

DSL Status

DSL Status: UP
DSL Modulation Mode: Auto
DSL Path Mode: FAST
Downstream Rate: 8128 Kbps
Upstream Rate: 448 Kbps
Downstream Margin: 11 db
Upstream Margin: 25 db
Downstream Line Attenuation: 21
Upstream Line Attenuation: 24
Downstream Transmit Power: 19
Upstream Transmit Power: 11
LOS Errors: 0

Rik · Mar 11, 2008, 18:49:27

Odd that. It seems that first hop is the worst. What happens if you just ping idnet?

RA-1972 · Mar 11, 2008, 18:50:31

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

C:\Documents and Settings\>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59

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

C:\Documents and Settings\

Rik · Mar 11, 2008, 18:51:18

It does look like a BT issue, then.

RA-1972 · Mar 11, 2008, 18:51:43

Do you think if ask idnet for diff IP would that make any difference ?

RA-1972 · Mar 11, 2008, 18:52:16

You reply to quick .

Rik · Mar 11, 2008, 18:53:22

I doubt it, that shouldn't affect your routing. Ask them though, if they think it would help.

Sorry, can't help the speed - it's the only way I can keep on top of the forum.

RA-1972 · Mar 12, 2008, 20:15:28

I have reset my router and pings have dropped by 10 ms , so might give my router a night off and see if it gets any better .

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

C:\Documents and Settings\nathan stone>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59

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

C:\Documents and Settings\nathan stone>

paulsmith109 · Mar 13, 2008, 07:08:00

Maintain router synch. Just keep disconnecting/reconnecting PPP session, checking ping results after each reconnection, and see if anything changes. My wife managed to turn off my router yesterday. It resynched OK of course but pings to idnet had increased to 22ms. I `ve just changed PPP session and on the third change my pings had returned to 11ms.
Give it a try!