Connection problems?

Started by Danni, Jan 28, 2009, 06:23:03

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 ... 4 5 6 7 8 ... 16
User actions

Steve

#125
Jan 30, 2009, 14:09:48
Its not done me any favours

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



Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms TTL=59
Reply from 212.69.36.10: bytes=32 time=107ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms 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 = 100ms, Maximum = 161ms, Average = 126ms

Thats normally around 15-20
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

#126
Jan 30, 2009, 14:10:37
One for IDNet I think, Steve.

Glenn

#127
Jan 30, 2009, 14:12:01
Are on GW5 Steve? Mine are similar to Ray's but I'm on DSL4
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Danni

#128
Jan 30, 2009, 14:12:51
danni@Matilda:~$ ping 212.69.36.10 -c5
PING 212.69.36.10 (212.69.36.10) 56(84) bytes of data.
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=123 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=177 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=149 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=172 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=155 ms

--- 212.69.36.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 123.645/155.725/177.507/19.114 ms
danni@Matilda:~$

Of course, I'll give it a bit for things to settle down before moaning :)
IDNet Customer (ex-partner's name): 6th January 2006 - 23rd March 2007
IDNet broadband Customer (my name): 11th June 2008 - 21st April 2010

Now with Be for internets, IDNet for phone.

Steve

#129
Jan 30, 2009, 14:14:21
No on .net, phone call will be required if doesn't settle.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

#130
Jan 30, 2009, 14:18:23
My pins were:  are they any good. :)  Things seem a bit faster and snappier for me.

C:\Windows\system32>ping bbc.co.uk -n 32

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=27ms TTL=121
Reply from 212.58.224.138: bytes=32 time=24ms TTL=121
Reply from 212.58.224.138: bytes=32 time=24ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=25ms TTL=121
Reply from 212.58.224.138: bytes=32 time=25ms TTL=121
Reply from 212.58.224.138: bytes=32 time=40ms TTL=121
Reply from 212.58.224.138: bytes=32 time=24ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=24ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=24ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=22ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121
Reply from 212.58.224.138: bytes=32 time=26ms TTL=121
Reply from 212.58.224.138: bytes=32 time=23ms TTL=121

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

;D
------
Alf :)

Steve

#131
Jan 30, 2009, 14:19:46
 :rofl:

Time to get a life .rebooted the router

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


Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=15ms TTL=122
Reply from 212.58.224.138: bytes=32 time=16ms TTL=122
Reply from 212.58.224.138: bytes=32 time=16ms TTL=122
Reply from 212.58.224.138: bytes=32 time=16ms TTL=122

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




Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

JB

#132
Jan 30, 2009, 14:30:59

I'm afraid a router reboot hasn't improved my figures:-

C:\>ping bbc.co.uk

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

Reply from 212.58.224.138: bytes=32 time=172ms TTL=121
Reply from 212.58.224.138: bytes=32 time=150ms TTL=121
Reply from 212.58.224.138: bytes=32 time=147ms TTL=121
Reply from 212.58.224.138: bytes=32 time=173ms TTL=121

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


Think I'll wait until things settle down before I try again.
JB

'Keyboard not detected ~ Press F1 to continue'

VaderDSL

#133
Jan 30, 2009, 14:48:50
Getting > 200ms here also, granted they've just had a new central put in so I too shall wait until monday to see how it plays out.

esh

#134
Jan 30, 2009, 15:12:59
Just to confirm what people are seeing here;

130+ ms to google on gw5
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

#135
Jan 30, 2009, 15:16:10
Give it 24 hours or so to settle, if things don't improve, let IDNet know (sample pings would be helpful).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

esh

#136
Jan 30, 2009, 15:24:01
It's variable but just to give a general sense of things, here is a crude plot;



Signs it might be settling down, I'll keep an eye on it.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

#137
Jan 30, 2009, 15:26:01
You're right, it's crude - you need to work on it more before it will be ready for EastEnders. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

esh

#138
Jan 30, 2009, 15:42:39
Haha ;)

I've upped the sampling and amount of sites interrogated to get some finer data over this period. The connection seems to reach good speeds still, just the lag is notable over an ssh link now.

Thanks for all the updates.

Upgrades are never easy.

Especially if BT is involved? ;)
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

#139
Jan 30, 2009, 15:44:56
Especially when they do two upgrades at the same time. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB

#140
Jan 30, 2009, 17:03:08

It is very variable as the attached trace shows. I have changed routers and it has helped a bit.

Will see how it settles over the weekend. My exchange is fine and figures earlier this week were good.


[attachment deleted by admin]
JB

'Keyboard not detected ~ Press F1 to continue'

Rik

#141
Jan 30, 2009, 17:16:23
I can't get to the BBC atm, it times out, but I have a different step 6:

tracert www.bbc.co.uk

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

  1     1 ms    <1 ms     1 ms  home [192.168.1.254]
  2    25 ms   151 ms    33 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    27 ms    29 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    25 ms    23 ms    25 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    27 ms    25 ms    23 ms  212.58.238.149
  6    26 ms    29 ms    25 ms  te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

#142
Jan 30, 2009, 17:54:41
I can access, ping and tracert the bbc fine.

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

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    51 ms    44 ms    44 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    42 ms    38 ms    32 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    42 ms    37 ms    36 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    38 ms    35 ms    39 ms  212.58.238.133
  6   322 ms   102 ms    39 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

#143
Jan 30, 2009, 17:57:02
Interesting - I tried www.bbc.co.uk instead of just bbc.co.uk and got this:

C:\Users\Lance>tracert www.bbc.co.uk

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

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    37 ms    40 ms    33 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    31 ms    30 ms    33 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    30 ms    33 ms    31 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5   142 ms    34 ms    42 ms  212.58.238.133
  6    31 ms    33 ms    30 ms  212.58.239.58
  7     *        *        *     Request timed out.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#144
Jan 30, 2009, 17:57:43
Odd, I can't at all, anywhere else is fine.

Ah, you've just got what I get. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB

#145
Jan 30, 2009, 18:11:26

Doesn't seem to reach destination is you use www.bbc.co.uk. Remove the www and it traces fully.
JB

'Keyboard not detected ~ Press F1 to continue'

Rik

#146
Jan 30, 2009, 18:11:54
Yup. BBC must be blocking.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

#147
Jan 30, 2009, 18:31:33
C:\Users\vitriol>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=92ms TTL=121
Reply from 212.58.224.138: bytes=32 time=99ms TTL=121
Reply from 212.58.224.138: bytes=32 time=204ms TTL=121
Reply from 212.58.224.138: bytes=32 time=222ms TTL=121

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

sigh!

Rik

#148
Jan 30, 2009, 18:34:57
Rough. What gateway are you on now?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

#149
Jan 30, 2009, 18:39:31
Not sure Rik, I was originally on GW5, but think I'm on DSL4 now.
Print
Go Up Pages 1 ... 4 5 6 7 8 ... 16
User actions