IDNet and latency

[Glenn]

Is interleaving turned on?

[DorsetBoy]

   It may be interleaving is on, can you get the adsl stats from your router,you'll need to telnet for them?

[Ray]

 

[Rik]

Welcome to the forum, Fozy (can I put an 'n' in that, please ).

BT seem to have been having a bad hair day. Have you spoken to support. If not, I can take up your case in the morning.

[fozy994]

I sent them an email with tracerts and what not because the offices were closed, if you can do anything to speed it along I'd love it!

[Rik]

I can't do anything to shift it until tomorrow, I'm afraid, but I'll have a word with support in the morning if you want me to.

[fozy994]

Yea if you could please, you are a god!

[Rik]

Flattery will get you everywhere.

[Steve]

 

[Rik]

I sent them an email with tracerts and what not because the offices were closed, if you can do anything to speed it along I'd love it!

Support have requested interleaving be turned off, so retest tomorrow when it will be off, ideally, do so with a cabled connection, with wireless turned off in the router and with the computer running in safe mode with networking support. If all is well, try again in 'full' Winodws mode, if that's OK, turn wireless back on. Your router is apparently off at the moment, it would be better if you ran it 24/7.

[fozy994]

Ok thanks will give it a shot, yea thats the eco power saving mother who switches every switch off given half the chance 

[Steve]

Find some glue

[Rik]

Or a big sign.

[fozy994]

or a fist

[Rik]

 

We're way more subtle than that, Fozy.

[fozy994]

Popping home from work at lunch so I will check my latencys out 

[Rik]

 

[fozy994]

Still the same :s

[Rik]

Can you do a series of manual pings (ping <server> -t -n 20) to www.idnet.net and any servers you use frequently.

[kelevra]

Would BT have put a new profile on the line?

If interleaving has actually been turned off surely the ping should have lowered at least a little.

[Rik]

That's why I asked for some tests that I can talk to support about. Interleaving may have been turned off, but something may have triggered it to turn back on again.

[kelevra]

Mine should have been changed as well so i will check when home and update here with results.

[fozy994]

Ok this is my tracert (i sent ping last time)

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

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

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

  1    <1 ms    <1 ms    <1 ms  . [192.168.2.1]
  2    31 ms    31 ms    32 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    32 ms    31 ms    32 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    32 ms    32 ms    31 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    31 ms    32 ms    32 ms  212.58.238.129
  6    33 ms    33 ms    32 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  7    39 ms    36 ms    32 ms  212.58.255.12
  8    33 ms    33 ms    32 ms  fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]



PINGS

C:\Documents and Settings\Owner>
C:\Documents and Settings\Owner>ping www.idnet.net -t -n 20

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

Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59

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

[Rik]

That looks about average for an interleaved line, let me see what I can find out for you.

[kelevra]

Unfortunately mine seems none the better

Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
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=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms 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
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=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59

Tracing route to www-tmmdi.l.google.com [66.102.9.147]
over a maximum of 30 hops:

 1     4 ms     2 ms     2 ms  192.168.2.1
 2    34 ms    33 ms    36 ms  telehouse-gw4-lo2.idnet.net [212.69.
 3    33 ms    31 ms    32 ms  telehouse-gw3-g0-1-400.idnet.net [21

 4    40 ms    32 ms    30 ms  195.66.224.125
 5    37 ms    32 ms    33 ms  64.233.175.27
 6    57 ms    49 ms    54 ms  209.85.250.216
 7    50 ms    55 ms    46 ms  72.14.232.235
 8    63 ms    56 ms    49 ms  64.233.174.14
 9    46 ms    50 ms    50 ms  lm-in-f147.1e100.net [66.102.9.147]