I'm having problems. My 2wire has all its lights on, but my internet doesn't work. I went through the setup wizard to try and reconnect, and I get the error:
ERROR:
Unable to Access Configuration Server.
The gateway is unable to access the configuration server.
Any suggestions? All other connection bits work. I'm on my phone now, which isn't great.
It's not DNS- tried swapping to OpenDNS and even typing in known IP numbers, which didn't work.
I can ping the gateway, but nothing else. A traceroute to my server fails after the first external hop (the gateway). Is this an IDNet problem?
Since it seems anyone who can help is asleep (probably sensible) I've emailed IDNet and I just have to hope they wake up soon :)
Hi Danni
try a factory reset, the last option of this page (http://192.168.1.254/xslt?PAGE=J21&THISPAGE=A02_POST&NEXTPAGE=J21).
You will then have to run the set up wizard again, check that you are using 528Y - 27G4 - A222 - 22BJ - B22V as the Key.
If you'd not hidden the link, I would have been able to tell it was to type into my computer, not click on my phone (I'm on my laptop now with my 3G dongle as that link didn't work on my phone). I will try that, just need to reconnect the wireless which will then kill my internet connection for a bit.
Sorry
http://192.168.1.254/xslt?PAGE=J21&THISPAGE=A02_POST&NEXTPAGE=J21
Okay, did that and now it's saying it can't connect to the dns server- it seems worse than before.
can you ping 208.67.222.222 (openDNS) ?
can you confirm you have 2 green lights at the bottom of the Router
No to pings, yes to two green lights.
Only place I can ping is the gateway (212.69.63.51)
We are aware of a few users who cannot get traffic past our gateway which we are currently investigating.
If you haven't done so already we would suggest leaving router off for 30 minutes and the trying to reconnect. It may be that there was an earlier problem that has now resolved itself and giving the exchange time to clear the session will resolve things.
So not my fault? Okay. Just had an email saying the same :)
I best go to college, as I'm already going to be rather late (luckily they understand my need for internet access there :P). If it's not working when I get home (I'll check it when I'm at college, as I run a webserver on my home computer) I'll turn it off for 30 minutes as suggested.
Thank you both for your help :)
Danni, because I got you to do a factory reset, you will eventually need to set up your router security again.
Follow this guide when you do... http://www.idnetters.co.uk/forums/index.php?topic=8927.0
You won't be able to check the web server from College, the firewall rules will have reset too and will lock you out :bawl:
Same problems here, can't get past the gateway. IDNet status is showing orange: "A few users may be experiencing traffic throughput problems which we are currently investigating."
So another £10 to Three mobile broadband to be able to work from home today :-(
We have found the issue and the affected connections should be restored shortly if not already.
All working here now.
Ta. :D
What went wrong?
Alex.
We're going to be installing a new router later today to help spread the load of the new Central and the new 21CN Host Link. In preparation, we made changes to the OSPF routing table internally - it went a bit wrong! Sorry to all for the inconvenience.
Simon
Naughty Simon. ;D
Can't get a WAN IP currently.
Yes, gone again here too.
I'm also having a lot of problems although I am currently connected. IDNet's support line is permanently engaged, any chance of an update here please? Thanks.
It's the router upgrade announced here:
http://www.idnetters.co.uk/forums/index.php?topic=12415.msg286631#msg286631
Quote from: Simon_idnet on Jan 28, 2009, 09:55:19
We're going to be installing a new router later today to help spread the load of the new Central and the new 21CN Host Link. In preparation, we made changes to the OSPF routing table internally - it went a bit wrong! Sorry to all for the inconvenience.
Simon
Is it not wise to test these things prior to putting them into a production enviroment...? ??? Or would that just be too much work for you?
Ah sorry, I missed that, thanks for the heads up Rik :thumb:
Quote from: ducky22 on Jan 28, 2009, 12:58:23
Is it not wise to test these things prior to putting them into a production enviroment...? ??? Or would that just be too much work for you?
The forum is not IDNet, we're independent. If you want to complain, you'll have to talk to IDNet directly.
UPDATE:
I've had a chat with Simon, the update caused a problem meaning that all their routers had to be re-booted. This resulted in loss of connection to the world for most people, in some cases it involved a loss of PPP (me!). Things should be OK now, and Simon did not expect any repeats.
The announcement seems to have come several hours after problems first arose?
If so, it might cause less frustration if precautionary announcements of upcoming work were posted. Just a simple there may be problems tomorrow.
Can't argue with that, Dave, although there is an announcement here (http://www.idnetters.co.uk/forums/index.php?topic=12415.0;topicseen).
In early days of TV you used to get a card saying "there is interference, please do not adjust your sets."
Quote from: Rik on Jan 28, 2009, 13:01:26
UPDATE:
I've had a chat with Simon, the update caused a problem meaning that all their routers had to be re-booted. This resulted in loss of connection to the world for most people, in some cases it involved a loss of PPP (me!). Things should be OK now, and Simon did not expect any repeats.
Me also, Rik, but I didn't notice it I was too busy eating my peppercorn ham sandwich at the time. ;)
I delayed my chicken and hot chilli sauce sandwich until after, Ray, martyr to the forum that I am. ;D
Quote from: Rik on Jan 28, 2009, 14:02:54
I delayed my chicken and hot chilli sauce sandwich until after, Ray, martyr to the forum that I am. ;D
Now that's what I call dedication beyond the call of duty, Rik. ;D
Me too. ;)
Announcements coming after I'm having problems don't help ;)
As I'd redone my port forwarding in the firewall before I left for college (I knew they'd be reset ;)) I knew that by the time I'd arrived (10.15am- I was very very lucky, as that was my lesson start time) my internet was working again, so it was fixed for me somewhere between 8.45am and 10.15am :)
You missed the 12:30 downtime then, Danni. :)
Indeed- I was learning algorithms for drawing minimum spanning tree graphs :P
I've always wanted to know how to do that. ;D
Quote from: Rik on Jan 28, 2009, 16:59:40
I've always wanted to know how to do that. ;D
You need to get out more! ;)
:whistle:
Quote from: Lance on Jan 28, 2009, 21:04:31
You need to get out more! ;)
This is true. :)
PPP loss 13 minutes ! I wonder if that's related to yesterdays events?
Yeah me too (and yesterday, and a stale session on Monday: this has not been a good week for my connection!).
There seems to be a problem with one of the routers, which they are working on.
Lossed PPP at 11:21 back at 11:31
back to normal now
Steve
And me, rebooted the router, still a little slow but at least I can connect
An unexpected glitch as the new router was 'introduced' to the network, I gather.
Experienced the outage here too...
A long handshake something from the last Century meeting something from this Century.
Could be. :)
I really should really pick a better time to be messing about with Telnet and DNS servers, i hit saveall and the whole thing went down :bawl:
Quote from: davej99 on Jan 28, 2009, 13:22:00
In early days of TV you used to get a card saying "there is interference, please do not adjust your sets."
I like that idea, except if there is no connection then it would be difficult to see the card. ;D
Quote from: Ted on Jan 29, 2009, 11:45:21
I really should really pick a better time to be messing about with Telnet and DNS servers, i hit saveall and the whole thing went down :bawl:
Aha! So you're to blame? :P
Telnet into the wrong router ;D
Quote from: Ted on Jan 29, 2009, 11:45:21
I really should really pick a better time to be messing about with Telnet and DNS servers, i hit saveall and the whole thing went down :bawl:
Ah, so it was
your fault, Ted. ;)
Quote from: stevethegas on Jan 29, 2009, 11:48:50
Telnet into the wrong router ;D
Ooops! Sorry guys ;D
Just don't hit you Delete button in case the whole internet disappears! ;)
:rofl: :karmic:
:karmic: :rofl2:
Quote from: Ted on Jan 29, 2009, 11:45:21
I really should really pick a better time to be messing about with Telnet and DNS servers, i hit saveall and the whole thing went down :bawl:
So you admit it, you was trying to hack into my router, it went down about 20 minutes ago ;D
Quote from: Glenn on Jan 29, 2009, 12:00:55
So you admit it, you was trying to hack into my router, it went down about 20 minutes ago ;D
I cannot tell a lie,
Sebby told me to do it!! :whistle:
;D I'll tell him! ;)
Quote from: Ted on Jan 29, 2009, 12:17:27
I cannot tell a lie, Sebby told me to do it!! :whistle:
Erm... :out:
Apologies for the disruption earlier today.
It was caused by an OSPF routing update between the edge and core routers that got out of hand. We're working at preventing a recurrence. We do however, expect that there may be another small disruption tomorrow in order to finally fix the issue. We expect that our new circuits will then be fully integrated into the network.
regards
Simon
I have to ask, what's OSPF, Simon?
A phone call later...
Open Shortest Path First - a routing protocol that sends the packets via the smallest number of hops... I learn a little each day. :)
More here:
http://en.wikipedia.org/wiki/Open_Shortest_Path_First
Indeed you do! Like, Wikiing first would have saved you a phone call! :)
Everyday is a school day Rik ! :)
Always something to learn.....
Quote from: Simon on Jan 29, 2009, 18:35:37
Indeed you do! Like, Wikiing first would have saved you a phone call! :)
Ah, but asking Brian meant I understood the answer. ;)
Quote from: vitriol on Jan 29, 2009, 18:35:52
Everyday is a school day Rik ! :)
Always something to learn.....
Does that mean I can go out to play now. ;D
Quote from: Simon on Jan 29, 2009, 18:35:37
Indeed you do! Like, Wikiing first would have saved you a phone call! :)
Ah! But 0800 is a very thrifty phone call. :whistle:
This, too, is true. :)
Not for IDNet, it isn't. ;)
They are all VOIP...
Meaning? I thought with 0800 numbers, the company had to pay for the calls?
well ever since the problems over the last few days, my pings are double or more than what they used to be.
BBC is pinging about 100ms at the mo
IDnet.com is around 40-50ms
My ping is normally around 13-16ms.
Let IDNet know, Paul.
Bang on normal for me, Paul:
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=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms 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 = 22ms, Maximum = 24ms, Average = 22ms
As Sebby says, let support know.
Quote from: Simon on Jan 29, 2009, 19:05:33
Meaning? I thought with 0800 numbers, the company had to pay for the calls?
They do, I just suspect that the cost is lower after the termination charge.
Ah, OK.
Perhaps someone should let Ted know not to telnet the router whilst they're balancing the centrals this afternoon :eek4:
;D
We'll just cut him off. ;)
I understand that today's work should only affect people on GW5 and GW6.
:bawl:
You'll be on your phone at the time. :)
So, I'll have the place to myself? :leer:
I'm on DSL4. :)
You'll be at lunch. :)
True, or unpacking the meat. :)
Quote from: stevethegas on Jan 30, 2009, 11:00:48
Perhaps someone should let Ted know not to telnet the router whilst they're balancing the centrals this afternoon :eek4:
Just typed in "saveall" and my finger is hovering over the return key, What's it worth not to press it? :rub:
Is this an auction, Ted? :)
How about I open the bidding at you pay me £10 :D
I think Ted wanted the cashflow to be in the other direction, Glenn. :)
Quote from: Rik on Jan 30, 2009, 12:11:23
I think Ted wanted the cashflow to be in the other direction, Glenn. :)
I'd settle for 50p and a jammy dodger ;D
I thought you were a jammy dodger, Ted? ;D
Okay, two disconnections in the last 20 minutes (which I was expecting, because of the lovely email). Is it safe for me to do stuff now? :P
I work is scheduled to finish at 2 I believe, so I would wait until then!
I don't know, tbh, Danni. I had just one, for about two minutes. If anything you are planning is critical, I'd suggest holding off for a little while. Or what Lance said. :)
Okay, will only do the "doesn't matter if I get disconnected" stuff then :P
So hang around here. ;)
I'm trying to catch up with my rss feeds on google reader. Plurk will wait- that gets really really annoying if the connection is unstable.
How do you keep up with it all?
Erm... normally by spending the 90-120 minute journey each way to college reading them :P Unfortunately forums aren't great on my current phone (I'm getting a G1 once my new bank card arrives). Today I'm off college, and should be doing maths but I'm on here instead :P
It's warmer here, Danni. :)
Hi psp83
My pings are also high.
bbc.co.uk
Average 48ms
IDnet.com
Average 47ms
IDnet.net
Average 48ms
Which gateway are you using? I'm on gw6. Is anyony else on gw6 geting slow pings?
Quote from: psp83 on Jan 29, 2009, 21:39:06
well ever since the problems over the last few days, my pings are double or more than what they used to be.
BBC is pinging about 100ms at the mo
IDnet.com is around 40-50ms
My ping is normally around 13-16ms.
Welcome to the forum, EB. :welc: :karma:
I'm on DSL4, my pings to IDNet/BBC average 24ms with interleaving on, fwiw.
Ouch- I'm on gw5, and mine are pretty bad:
bbc.co.uk: average 108.348ms
idnet.net: average 87.868ms
idnet.com average 78.135ms
Mine are normally in the 30-40ms range.
Just checked... pings are being hit by people re-connecting after the load balancing exercise. They should settle shortly, if anyone has problems after today, please let support know.
Quote from: EnglishBeef on Jan 30, 2009, 13:28:37
Hi psp83
My pings are also high.
bbc.co.uk
Average 48ms
IDnet.com
Average 47ms
IDnet.net
Average 48ms
Which gateway are you using? I'm on gw6. Is anyony else on gw6 geting slow pings?
I'm on dsl4. not checked my pings today.
Quote from: Danni on Jan 30, 2009, 13:32:51
Ouch- I'm on gw5, and mine are pretty bad:
bbc.co.uk: average 108.348ms
idnet.net: average 87.868ms
idnet.com average 78.135ms
Mine are normally in the 30-40ms range.
GW5 & GW6 will be worst affected as I understand it.
Thanks Rik :)
Thanks Rik
My pings quoted are with interleaving off. I wonder if IDnet would move me to DSL4 which must be for special people!!
I would love to get 24ms pings.
Quote from: Rik on Jan 30, 2009, 13:29:43
Welcome to the forum, EB. :welc: :karma:
I'm on DSL4, my pings to IDNet/BBC average 24ms with interleaving on, fwiw.
It's for old hands, EB. ;) Your pings will also be longer if you're further away from London than me.
I used to be on DSL4. I loved that IP address :'(
Must be across the board, pings for .net are in 3 figures for me at present
Right now:
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=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 23ms, Maximum = 26ms, Average = 24ms
Show off, Rik :P
It's not often anything about my connection makes others jealous, Danni. I have to seize the opportunity. ;D
The work is finished, btw...
must be sorted for me, pings back to normal.
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=10.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/10.0/10.0 ms
I knew my moment of glory wouldn't last. :'(
Quote from: Rik on Jan 30, 2009, 13:52:57
I knew my moment of glory wouldn't last. :'(
hehe, sorz rik :P
Whats the difference between dsl4, gw5 and gw6?
Quote from: Rik on Jan 30, 2009, 13:52:57
I knew my moment of glory wouldn't last. :'(
:hehe:
Quote from: EnglishBeef on Jan 30, 2009, 13:58:33
Whats the difference between dsl4, gw5 and gw6?
They are just the various gateways that customers are assigned to. Only a certain number are assigned to each. All customers now will be going onto gw6.
Mine currently with interleaving on (also on dsl4)
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms 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 = 24ms, Maximum = 26ms, Average = 25ms
So all new customers signing up now will be on gw6 no matter which package they take up (home business etc)?
Quote from: Sebby on Jan 30, 2009, 14:00:28
They are just the various gateways that customers are assigned to. Only a certain number are assigned to each. All customers now will be going onto gw6.
Afaik, yes.
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
One for IDNet I think, Steve.
Are on GW5 Steve? Mine are similar to Ray's but I'm on DSL4
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 :)
No on .net, phone call will be required if doesn't settle.
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
: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
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.
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.
Just to confirm what people are seeing here;
130+ ms to google on gw5
Give it 24 hours or so to settle, if things don't improve, let IDNet know (sample pings would be helpful).
It's variable but just to give a general sense of things, here is a crude plot;
(http://garagos.net/wajn/filedump/pings_21cn.png)
Signs it might be settling down, I'll keep an eye on it.
You're right, it's crude - you need to work on it more before it will be ready for EastEnders. ;D
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? ;)
Especially when they do two upgrades at the same time. :)
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]
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]
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.
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.
Odd, I can't at all, anywhere else is fine.
Ah, you've just got what I get. :)
Doesn't seem to reach destination is you use www.bbc.co.uk. Remove the www and it traces fully.
Yup. BBC must be blocking.
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!
Rough. What gateway are you on now?
Not sure Rik, I was originally on GW5, but think I'm on DSL4 now.
You are, looking at your IP address. So that's odd, as we're in on the same route. Have you forced a re-sync of your router?
Nope.
Connection has been poor for a couple of months now, just not had the time to do much about it. I did report to IDNet and was advised to test the conection using the engineers socket behind the face plate. I hate to admit but I've not had the time to do this as of yet.
If I get chance then I'll try doing that over the weekend.
The only other reason I can think of for poor pings would be exchange congestion. :(
While I've been suffering my friends and family members seem to be unaffected and they're all on the same exchange.
Different VP?
Possibly, after I've been down to the refuse centre tomorrow (got loads of stuff to get rid of) then I'll try removing the faceplate and testing the connection. Thats what I've been advised to do, so I'll do it. I'll blow a few gig on cr*p game demos and stuff from Xbox Live. See how it holds up.
Ok, keep us posted.
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)... and my ping times don't seem good:
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=180ms TTL=122
Reply from 212.58.224.138: bytes=32 time=168ms TTL=122
Reply from 212.58.224.138: bytes=32 time=174ms TTL=122
Reply from 212.58.224.138: bytes=32 time=112ms 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 = 112ms, Maximum = 180ms, Average = 158ms
Not very 'always on' really...
Did you not get the email?
Just checked I got it twice.
Quote from: dlorde on Jan 30, 2009, 19:37:27
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)... and my ping times don't seem good:
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=180ms TTL=122
Reply from 212.58.224.138: bytes=32 time=168ms TTL=122
Reply from 212.58.224.138: bytes=32 time=174ms TTL=122
Reply from 212.58.224.138: bytes=32 time=112ms 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 = 112ms, Maximum = 180ms, Average = 158ms
Not very 'always on' really...
Been in touch with IDNet yet?
Quote from: dlorde on Jan 30, 2009, 19:37:27
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)
Are you losing sync or dropping PPP?
My pings are back to normal this morning:
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=32.6 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=32.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=35.2 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=34.6 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=32.0 ms
--- 212.69.36.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 32.044/33.332/35.277/1.365 ms
danni@Matilda:~$
That's good, thanks, Danni. :)
Quote from: Rik on Jan 31, 2009, 09:27:21
Are you losing sync or dropping PPP?
The modem log shows:
...
01/30/2009 19:04:25 If(ATM1) PPP connection ok !
01/30/2009 19:04:23 ATM1 start PPP
01/30/2009 19:04:23 Dial On Demand(ATM1)
01/30/2009 19:04:22 ATM1 get IP:<removed - Rik>
01/30/2009 19:04:14 If(ATM1) PPP fail : Unknown error or UI Connect/Disconnect
01/30/2009 19:04:12 ATM1 start PPP
01/30/2009 19:04:12 Dial On Demand(ATM1)
01/30/2009 19:03:41 192.168.2.3 login success
...
01/29/2009 22:19:18 NTP Date/Time updated.
01/29/2009 19:18:17 ATM1 get IP:<removed - Rik>
01/29/2009 19:18:15 If(ATM1) PPP connection ok !
01/29/2009 19:18:13 ATM1 start PPP
01/29/2009 19:18:13 Dial On Demand(ATM1)
01/29/2009 19:14:26 sending ACK to 192.168.2.6
01/29/2009 19:11:58 NTP Date/Time updated.
01/29/2009 19:06:29 Can't find NTP time.
01/29/2009 19:06:20 ATM1 get IP:<removed - Rik>
01/29/2009 19:06:11 If(ATM1) PPP fail : Unknown error or UI Connect/Disconnect
01/29/2009 19:06:09 ATM1 start PPP
01/29/2009 19:06:09 Dial On Demand(ATM1)
01/29/2009 19:05:42 192.168.2.3 login success
01/29/2009 11:30:37 sending ACK to 192.168.2.3
...
01/28/2009 19:07:33 NTP Date/Time updated.
01/28/2009 19:02:26 If(ATM1) PPP connection ok !
01/28/2009 19:02:25 ATM1 get IP:<removed - Rik>
01/28/2009 19:02:12 ATM1 start PPP
01/28/2009 19:02:12 Dial On Demand(ATM1)
01/28/2009 19:02:09 192.168.2.3 login success
...
01/28/2009 12:44:15 ATM1 stop PPP
Quote from: Sebby on Jan 31, 2009, 00:38:20
Been in touch with IDNet yet?
Not yet, I thought I'd give it a while to see if it sorts itself out... Pings seem to have recovered:
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=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=34ms TTL=122
Reply from 212.58.224.138: bytes=32 time=24ms TTL=122
Reply from 212.58.224.138: bytes=32 time=53ms 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 = 23ms, Maximum = 53ms, Average = 33ms
C:\>
Quote from: dlorde on Jan 31, 2009, 13:19:27
Not yet, I thought I'd give it a while to see if it sorts itself out... Pings seem to have recovered:
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=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=34ms TTL=122
Reply from 212.58.224.138: bytes=32 time=24ms TTL=122
Reply from 212.58.224.138: bytes=32 time=53ms 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 = 23ms, Maximum = 53ms, Average = 33ms
C:\>
You may want to edit your personal ip address out of your previous post :no:
Unless it's been edited, I can't see it? Only the BBC one there (and I bet they're used to being spammed with pings :P).
It's there, but not for long...
Quote from: dlorde on Jan 31, 2009, 13:12:38
The modem log shows:
...
Can't really work it out from that, but given the times and the lack of other reports, I'd lean towards a sync drop. What's your downstream attenuation, noise margin and sync speed.
Quote from: Rik on Jan 31, 2009, 14:33:07
Can't really work it out from that, but given the times and the lack of other reports, I'd lean towards a sync drop. What's your downstream attenuation, noise margin and sync speed.
It's all looking pretty good speed-wise now:
Actual Data Rate
Up Stream 448 (Kbps.)
Down Stream 7616 (Kbps.)
Noise Margin
Upstream 23 dB
Downstream 12 dB
Attenuation
Upstream 40 dB
Downstream 34 dB
DSL connection rate: 7616 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for line is - 6500 kbps
Actual IP throughput achieved during the test was - 5910 kbps
That looks pretty good. I sense that your noise margin has been set to 12db to stabilise the line, hence the lower sync speed (I suspect you have interleaving on too). If things remain stable, and you can maintain a connection for 14+ days, then your sync speed should increase to 8128.
I reckon it might be interleaving alone that's causing the sync to max out at 7,616k. The margin may be 12dB because the line is so good...
Possible, but given it's 12, I wonder about the target having been changed.
Could be. It just seems a bit of a coincidence that the sync would be exactly 7,616k if it was the margin that was the limiting factor.
I know, two possible coincidences in one post. :)
What's the world coming to? :P
It's going to end in tears. ;D
So am I right to anticipate an increase in speed in a couple of weeks?
To be honest, it's no big deal - I'm happy with the current speed - although I would like a little more reliability.
It's unlikely you'll see a speed increase, except for peak times when previously there was maybe a minor slowdown due to the new centrals being late or if you have a WBC enabled exchange and you ask support to trial you on the up to 24mb service.
What Lance said. :)
OK, that's fine. Thanks all, (oh, and thanks for editing out my IP address, I always seem to forget)
:thanku:
Another disconnection this morning, but back up again quickly.
It seems BT had a wobbly...
Something we're very familiar with. :)
I've been out for half an hour now. Did BT just disconnect the whole of idnet? It seemed like it from here.
I couldn't get on either but was able to access other sites.
I'm not exactly sure what the problem was. Rik may have more information when he gets on, otherwise we'll hear from IDNet soon, no doubt.
Am I the only one who is still down..?
I'm at work and not through an IDNet connection, so I couldn't say.
ducky22: my gw5 is still down
gw5 also :-(.
Hopefully it won't be long. No doubt IDNet are working flat out to sort this...
Down for me as well. Glad I have mobile broadband as a backup.
GW5 connection.
Still down here too. (GW5)... Posting from my phone...
Quote from: scook94 on Feb 03, 2009, 13:51:22
Still down here too. (GW5)... Posting from my phone...
Do you know about the mobile version (http://www.idnetters.co.uk/forums/index.php?wap2), incidentally? It's a lot quicker if you do come on via your mobile. :)
Been down for about an hour on idnet.net.
Trying to work from home because of the weather and suffering dial up. :(
Down for me still too, and have only just managed to get in on my phone. All phone lines to IDNet seem to be busy too. Power issue, maybe?
Could be. Also, they were probably tweaking to resolve the ping issues; perhaps that went wrong?
Me too. :(
(posted using mobile)
I would doubt power as a generator should sort that ... GW5 still down here aswell.
I'm back online ...
I had PPP go down at 12:49, then came back at 13:15, down again at 13:19, back up at 14:03. I haven't been able to get any information, the phones have been in meltdown - possibly not helped by the fact that they are VOIP.
Just came back up for me.
Up for me here now :) Cheers!
:thumb:
Back up for me too!!
CO7 was down from 1:10pm to 2:06pm with a failed PPP authentication. What is going on with IDNet? We have had similar problems for the past few weeks now, our building is almost next door to the local exchange, and our line and hardware are 100% OK.
Time to get a MAC code from IDNet and move somewhere else?
Only you can make that decision. :)
I'm back on :thumb: They should pay by direct debit, saves all this nonsense :whistle:
Haven't read all the post's, what was the problem? :dunno:
They are upgrading their network so I would bear with them ... teething problems I suspect.
So why isn't there a backup if the generator fails? Network planning and management isn't rocket science... Seriously, only incompetence can cause this number of problems. And don't any of the IDNet faithful dare start. I don't want to hear from you. These are continuing problems!
And yes, I will be jumping ship shortly. This doesn't happen with reputable ISPs.
Back on here too.
Quote from: ducky22 on Feb 03, 2009, 14:14:43
So why isn't there a backup if the generator fails? Network planning and management isn't rocket science... Seriously, only incompetence can cause this number of problems. And don't any of the IDNet faithful dare start. I don't want to hear from you. These are continuing problems!
And yes, I will be jumping ship shortly. This doesn't happen with reputable ISPs.
No one's defended IDNet. Today wasn't acceptable, and I'm sure they'd agree with that! The beauty of a one month contract is that you are free to move. :)
Quote from: ducky22 on Feb 03, 2009, 14:14:43
So why isn't there a backup if the generator fails? Network planning and management isn't rocket science... Seriously, only incompetence can cause this number of problems. And don't any of the IDNet faithful dare start. I don't want to hear from you. These are continuing problems!
And yes, I will be jumping ship shortly. This doesn't happen with reputable ISPs.
No one said a generator had failed. I was just guessing as to a possible reason why the phones seemed to be out too.
We wish you every success with your new ISP.
Quote from: ducky22 on Feb 03, 2009, 14:14:43And yes, I will be jumping ship shortly. This doesn't happen with reputable ISPs.
Really ? Have you not worked in IT before ::)
Up with our GW5 account, down with our dsl4.
As we've been unable to get any information, Ducky, we're probably as miffed as you are.
I went down for about an hour but am now back up. Whenever there is s big network change there will be a few problems and a reputable (idnet) isp will sort things out as soon as possible. They will learn lessons from these problems and be even better than they are now. Anyone can criticise over problems in hindsight but no one can see into the future now matter how well prepared you are.
It's just a blip, calm down girls :thumb: :whistle: :out:
I called support,question answered...I guessed it was the new router....as Alf said,teething problems....thanks support
Quote from: uxbod on Feb 03, 2009, 14:17:48
Really ? Have you not worked in IT before ::)
Yes, I do actually.
With that attitude I feel sorry for your poor clients. Plan and test. Don't be lazy. Last week it was "whoops we made a route change and everything died"
And what a suprise regarding the remarks from Cavillas... I said I didn't want to hear it.
Back up on GW5 now...
HSRP ? ;)
Anyone else seeing pings through the roof again, mine have gone out from an average of 24ms to around 130...
M:\>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=158ms TTL=122
Reply from 212.58.224.138: bytes=32 time=164ms TTL=122
Reply from 212.58.224.138: bytes=32 time=170ms TTL=122
Reply from 212.58.224.138: bytes=32 time=163ms 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 = 158ms, Maximum = 170ms, Average = 163ms
M:\>
Here you are
[attachment deleted by admin]
Quote from: uxbod on Feb 03, 2009, 14:14:24
They are upgrading their network so I would bear with them ... teething problems I suspect.
Uxbod has a point. We all know work is ongoing. Though it is irritating to have frequent interruptions, I see no reason to throw the toys out of the pram yet, and certainly not before we know the cause. Though pings are well up.
Same sort of pattern, thanks guys. :thumb:
A detailed explanation of what has gone wrong from either Tim or Simon would help settle people's somewhat frayed nerves (including mine).
I agree.
Quote from: davej99 on Feb 03, 2009, 14:29:19
Uxbod has a point. We all know work is ongoing. Though it is irritating to have frequent interruptions, I see no reason to throw the toys out of the pram yet, and certainly not before we know the cause. Though pings are well up.
Fair enough if this had not been occuring regularly for the last 3 months...but oh wait it has. ::)
It was also refreshing to see the status page showing green across the board throughout the entire outage.
Thought this downtime was to fix the load balancing to get the pings down, but still seems quite all over the place here :(
Everything you've said is factually correct, ducky; no one is disputing that. But it's not worth ranting here as this is just an unofficial forum - complaints need to go to IDNet directly.
I was with Be* and for 3 and a half weeks I had a virtually useless connection to which they wouldn't aknowledge, basically a local piece of LLU equipment at the exchange broke, meaning I was getting pings > 250ms and 75% packet loss and downloads would always fail. For nearly a month, I phoned them up 3-4 times a week, while I wasn't at work trying desperately to get through to their support/supervisors, each time it was, have you unplugged the router, have you left it for 30 minutes, have you plugged the microfilter into the master plate etc.
I kept telling them it wasn't a fault my end and it must be the exchange, nah it's probably BT or your line :( idiots. In the end maybe half a dozen of us on a forum managed to get our evidence together and it was sent numerous times to Be* as well as the CS rep on there iirc. Finally they acknowledged and fixed it, by which time I had moved to IDNet.
BT have been so much worse for me in the past, and Virgin Media, dear god how do people use their oversubscribed service? I was paying for 20mb connection, with horrible upload speeds and getting just shy of 1mb speeds due to them packing people onto the UBR's so ultimately :) I love IDNet, i do miss the old days of 512kb ultra stable broadband though, I was with Zen when ADSL was first rolled out :)
I am on GW5 and got disconnected from my online game for an hour :( went to the chippy to get some grub. came back and saw I was back online but went to check the pings and godamn they are back into the 100's.
Same problems here, needless to say since it's clearly a problem at IDNet. Down completely (bar two minutes in the middle) for over an hour, and now with unacceptable high pings. Phone seemed to be deliberately left off the hook so they didn't have to answer any calls while it was down.
I have to say, I share the disappointment expressed by one or two of the other posters. I used to be a big fan of IDNet, and I've brought quite a few customers to them over the last three years, but now I'm feeling very let down. Let's be clear about this: we pay way over the odds at IDNet, and we do so because we want a no-nonsense premium quality service. Until relatively recently, this was delivered without any fuss, and I was happy to pay more. But now we've had goodness knows how many outages over the last month (my router logs show other occasional small outages in in addition to the ones documented on here as well, not for very long each time, and on every occasion it is not a loss of sync that causes it, it's the PPPoA layer only), and now a no-phone-support-during-outage stunt worthy of Tiscali (and what the hell is the service status page for, if it always claims everything is hunky dory?!), and I'm wondering why I bother to pay more.
As far as I'm concerned, they have until the end of today to sort out the ping fiasco, apologise for the appalling lack of service (customer and internet service) that occurred today, and not have a single other screw-up until the end of this month at least. Failing that, I will asking for my MAC code and recommending to the other 20+ customers that I've brought to them, to do likewise.
Careful, Vader, you'll get me reminiscing about 300 baud modems soon. ;)
I think Be have got a lot better with maintenance and upgrades now, Vader.
I agree with you about 512k - well fixed services in general. There's certainly something to be said for the stability they offered.
I was just thinking everything was sorted.....the first graph was taken at 11pm last night = 20 average ping
....the second graph at 2pm today = 159 average ping
I am sure it is only a matter of time :whistle:
[attachment deleted by admin]
Quote from: Rik on Feb 03, 2009, 14:26:37
Anyone else seeing pings through the roof again, mine have gone out from an average of 24ms to around 130...
Yup, 153ms up from 24ms!
Also dropped to 1Mbps from nearly 7... :'(
Quote from: Mohux_Jnr on Feb 03, 2009, 14:40:31
I was just thinking everything was sorted.....the first graph was taken at 11pm last night = 20 average ping
....the second graph at 2pm today = 159 average ping
I am sure it is only a matter of time :whistle:
I sincerely hope so. :fingers:
Quote from: skwark on Feb 03, 2009, 14:41:35
Yup, 153ms up from 24ms!
Also dropped to 1Mbps from nearly 7... :'(
That shouldn't have happened, only PPP actually dropped. Is your sync speed the same?
Sync still 8128 as always....
Quote from: karvala on Feb 03, 2009, 14:38:14
As far as I'm concerned, they have until the end of today to sort out the ping fiasco, apologise for the appalling lack of service (customer and internet service) that occurred today, and not have a single other screw-up until the end of this month at least. Failing that, I will asking for my MAC code and recommending to the other 20+ customers that I've brought to them, to do likewise.
Couldn't have put it better myself. Zen for sure.
If Rik can't get information out of IDNet, the rest of us are completely screwed.
Quote from: skwark on Feb 03, 2009, 14:46:08
Nope, sync still 8128 as always....
Could you run a BT speed test and post the results. I wonder if it's a profile issue.
Quote from: ducky22 on Feb 03, 2009, 14:46:17
If Rik can't get information out of IDNet, the rest of us are completely screwed.
I try, but ultimately I'm just another customer.
Hmm, it looks like we are "back online" but not running as expected!
(http://www.speedtest.net/result/403459555.png) (http://www.speedtest.net)
Edit: This is with an 8128 sync!
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 1282 kbps
Near normal pings here:
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=27ms TTL=122
Reply from 212.58.224.138: bytes=32 time=25ms TTL=122
Reply from 212.58.224.138: bytes=32 time=28ms TTL=122
Reply from 212.58.224.138: bytes=32 time=27ms 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 = 25ms, Maximum = 28ms, Average = 26ms
Quote from: MattBeard on Feb 03, 2009, 14:51:14
Hmm, it looks like we are "back online" but not running as expected!
(http://www.speedtest.net/result/403459555.png) (http://www.speedtest.net)
Edit: This is with an 8128 sync!
Can you run a BT test, Matt?
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8000 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 6000 kbps
Actual IP throughput achieved during the test was - 699 kbps
Everyone who's having high ping issues, reboot your router.
I did so and back to normal.
M:\>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=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=22ms TTL=122
Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=23ms 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 = 22ms, Maximum = 23ms, Average = 22ms
M:\>
Quote from: skwark on Feb 03, 2009, 14:51:24
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 1282 kbps
You need to let support know, that's completely unacceptable.
Quote from: ducky22 on Feb 03, 2009, 14:56:08
Everyone who's having high ping issues, reboot your router.
I did so and back to normal.
That would suggest my hunch about the network being unbalanced by the raft of re-connections is right...
Whee I'm back on. :thumb:
But my pings have gone from a steady 42 (was 26-27 last year >:() to 185... and yes I have rebooted and refreshed my router. >:( >:( >:(
So, due to SouthEastern rail being cr*p despite putting my season ticket up by 10%, I've had to work from home for two days. Due to IDNet being cr*p at the moment, I lost an hour's work yesterday and two hours today, and now my broadband is crawling - it's like being back at Pipex :-(
Time to check out alternatives, I think...
(http://www.speedtest.net/result/403461543.png) (http://www.speedtest.net)
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 6745 kbps
Pretty good on speed front, for me, just now.
If the network is unbalanced, then they don't have things setup correct. A mass of people reconnecting should fix any unbalanced centrals.
QuoteEveryone who's having high ping issues, reboot your router.
I did so and back to normal.
Outstanding.........back to an 18 ping average :)
Quote from: Mohux_Jnr on Feb 03, 2009, 15:01:09
Outstanding.........back to an 18 ping average :)
Steady on... Outstanding would be if this problem had never occured in the first place.
Well i rebooted router after reading the post above and it came back normal (I think). But for how long I dunno.
Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=23ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms TTL=124
Reply from 85.236.96.22: bytes=32 time=22ms TTL=124
Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms
I'm just guessing, Ducky, in the absence of hard information, but I do know they were locking off some pipes as part of the balancing exercise, so that when people re-connected they would go to a different pipe. The change in pings after the outage makes me think that it's become unbalanced again, particularly as pings started OK, then deteriorated as, I presume, more people came back online.
Quote from: Rik on Feb 03, 2009, 15:03:27
I'm just guessing, Ducky, in the absence of hard information, but I do know they were locking off some pipes as part of the balancing exercise, so that when people re-connected they would go to a different pipe. The change in pings after the outage makes me think that it's become unbalanced again, particularly as pings started OK, then deteriorated as, I presume, more people came back online.
Didn't know they'd blocked off pipes. Clever them... You're probably right.
That would be unusual. ;)
Hmm, restarting the router only made things worse:
(http://www.speedtest.net/result/403469466.png) (http://www.speedtest.net)
You really need to be talking to IDNet, only if they know the extent of the problems can they identify the issue.
Quote from: Mohux_Jnr on Feb 03, 2009, 15:01:09
Outstanding.........back to an 18 ping average :)
Back to normal here too - DSL4 - after rebooting router. :thumb:
Mine went UP to 193! :no:
I'll try again in a minute.
I just reset the PPP session and my pings are back to 24ms average. It's definitely worth a try.
Pings back down to 30ms but for some reason half the pages I try and load aren't working, are the DNS servers having a hiccup?
Line speed looks okay here :- http://www.splatnix.net/cgi-bin/mrtg-rrd.cgi/cisco-linespeed.html
Quote from: VaderDSL on Feb 03, 2009, 15:17:33
Pings back down to 30ms but for some reason half the pages I try and load aren't working, are the DNS servers having a hiccup?
Not that I've seen. I can test a site from here if it would help.
Quote from: uxbod on Feb 03, 2009, 15:19:50
Line speed looks okay here :- http://www.splatnix.net/cgi-bin/mrtg-rrd.cgi/cisco-linespeed.html
Mine are OK too.
Quote from: Rik on Feb 03, 2009, 14:57:21
You need to let support know, that's completely unacceptable.
Followed the advice here, rebooted and it's back to "normal". Pings back down to mid 20s and back to 6-7Mbps. I'm not using their DNS though, so can't comment on that.
http://www.esa.int/
I cannot access that and general browsing feels slower than dialup, takes about 2 minutes to load IDnetters, google etc.
www.esa.int resolves to 84.53.138.42, so you could try accessing that by IP and see if that helps.
Straight in, fast load, no problems. Might be worth clearing your cache and flushing DNS.
Much better after a router reboot:
(http://www.speedtest.net/result/403485244.png) (http://www.speedtest.net)
Phew. ;)
Quote from: Rik on Feb 03, 2009, 15:09:57
You really need to be talking to IDNet, only if they know the extent of the problems can they identify the issue.
I did, and a very nice programmer who's been drafted in to assist on the phones, did some technical stuff and switched me to idnet.net from idnet.gw5, after which everything went back to normal speed :-)
(http://www.speedtest.net/result/403484732.png) (http://www.speedtest.net)
He sounded a little hoarse - apparently they had over 400 calls this morning...
I'm not surprised. That was probably Andy you spoke to. :) Hang on, it was almost certainly Martin, not Andy - did he mention rugby at all? :)
You know, reading through these posts reminded me just how intolerant some of us are when things go wrong. :shake:
It surprises me that this is still so. We were all told about the work taking place, and we all know the problems we can have updating ONE computer with relatively small updates, let alone having to make major changes to a network such as IDNETs. If that is all that goes wrong then "Well done IDNET" I say!
As for lack of notification during the worst of it - I would rather they spent the time putting it right, instead of getting involved in 'verbal' exchanges on the forum.
Mo
:comp:
I think the problem, Mo, is that there have been outages on Wednesday, Thursday, Friday and twice today, with very little communication from IDNet (the phones were in melt-down at lunchtime). In addition, pings have been bad for many people who are keen gamers. Taken together, people have felt they are not getting the service they are paying for.
Quote from: MoHux on Feb 03, 2009, 15:42:18
You know, reading through these posts reminded me just how intolerant some of us are when things go wrong. :shake:
It surprises me that this is still so. We were all told about the work taking place, and we all know the problems we can have updating ONE computer with relatively small updates, let alone having to make major changes to a network such as IDNETs. If that is all that goes wrong then "Well done IDNET" I say!
As for lack of notification during the worst of it - I would rather they spent the time putting it right, instead of getting involved in 'verbal' exchanges on the forum.
Mo
:comp:
What you say is categorically flawed. I'm perfectly tolerant of the occasional problem but not regularly occuring issues. Did you forget this has been happening on and off for months?
Major changes are easily done with minimal or no downtime. How on earth do you think tier 1 carriers operate?
Quote from: ducky22 on Feb 03, 2009, 15:46:03
What you say is categorically flawed. I'm perfectly tolerant of the occasional problem but not regularly occuring issues. Did you forget this has been happening on and off for months?
Major changes are easily done with minimal or no downtime. How on earth do you think tier 1 carriers operate?
I bow to such superior knowledge! :bow:
Well if IDNETs tier 1 carrier messes up then they don't really have a chance do they :P There is a great deal of speculation about what has been happening, and I am sure that IDNET will at some point post a response. IDNET have always been good in that respect. I moved away from IDNET for quite a while to >:D but eventually came back. IMHO the service is second to none, and in the time I have been back there has been very few hickups. I don't game, but I do rely on my email server @ home office pumping messages to my iPhone. So yes its a pain, but is it a poor service, No way in my eyes.
All sorted a quick reset, reboot of the modem and router and all up and loadfing again normally :D Cheers for the help.
Phew. :)
Quote from: MoHux on Feb 03, 2009, 15:50:29
I bow to such superior knowledge! :bow:
I'm glad to hear you bow to my ability to read other threads on this forum and the fact I've experienced problems myself. Are you one of those adults who failed to learn to read and write? My heart bleeds...... ::)
Let's not fall out with each other, guys, none of us is responsible for what has happened.
*Skulks away suspiciously*
Quote from: uxbod on Feb 03, 2009, 15:51:11
Well if IDNETs tier 1 carrier messes up then they don't really have a chance do they :P There is a great deal of speculation about what has been happening, and I am sure that IDNET will at some point post a response. IDNET have always been good in that respect.
IDNet used to be good in that respect, certainly, but these recent episodes have indicated that things seemed to have changed in this regard, sadly. I can't remember the last time there was an hour+ outage accompanied by blocked support lines (which I still think were off the hook, since I and many others tried repeatedly and I have yet to hear from anyone who got through at any point, not to mention the fact that there is usually a queuing system in place that was strangely absent during this time), while all the time the service status page did an impression of the band on the titanic, and then several hours later there is still no acknowledgment from IDNet that anything even happened. If the same thing happened with another ISP, such as TalkTalk or Tiscali, we'd all roll our eyes and say "What can you expect? That's just typical of them." Are we now supposed to be thinking the same thing about IDNet? :eyebrow:
I think the problem with the phones is that they are VOIP, so I suspect (but haven't been able to confirm) that they simply stopped working during the outage.
Just checked, I'm wrong on the phones. :(
So what's the answer?
Quote from: Rik on Feb 03, 2009, 16:12:54
Just checked, I'm wrong on the phones. :(
Glad to hear that... having phones on the same network as everything really would be the worst planning/management possible. Any joy with further details on the outage?
Not yet, I've been promised an update when things are fully under control.
Quote from: Rik on Feb 03, 2009, 16:02:52
Let's not fall out with each other, guys, none of us is responsible for what has happened.
Takes two ............................. ;)
So if one backs off... ;D
Quote from: Rik on Feb 03, 2009, 16:17:48
I'm waiting. ;)
Ah, I see. I just assumed that if you'd been told you were wrong... :whistle:
No, I just got a "we'll phone you back..." ;)
Quote from: Rik on Feb 03, 2009, 16:21:52
No, I just got a "we'll phone you back..." ;)
Guess the phones are working then. ;D
I think a lot of people post here just to make sure it's "not just them".
Of which they are perfectly entitled to an answer.
My speeds are fine and the connection still has a good uptime ratio. I'll look forward to when pings normalise but I'm not so worried. I could really do with a router that brings the PPP back up by itself though :(
Get a 2700, Esh, it does that and allows you to drop it independently of sync. :)
Quote from: karvala on Feb 03, 2009, 16:23:24
Guess the phones are working then. ;D
They are now. :)
Quote from: esh on Feb 03, 2009, 16:24:15
My speeds are fine and the connection still has a good uptime ratio. I'll look forward to when pings normalise but I'm not so worried. I could really do with a router that brings the PPP back up by itself though :(
Which router are you using?
Cisco 877 all the way :D
Quote from: Rik on Feb 03, 2009, 15:39:01
I'm not surprised. That was probably Andy you spoke to. :) Hang on, it was almost certainly Martin, not Andy - did he mention rugby at all? :)
No mention of rugby - he said he was a programmer and he did a bit of Java programming (I'm a Java programmer at present). Poor chap sounded tired, but was patient and very helpful - pleasantly less curt than the other IDNet support persons I've encountered ;-)
Martin is OK, he's a Leicester Tigers fan, so I won't hear anything bad said about him. :)
What a shame about the Saints match then Rik :angel:
See Simon_idnet is, (edit) sorry was just, viewing.
A few words might no go amiss in support of the loyal IDNetters, who are getting some grief for bravely defending the firm.
Quote from: uxbod on Feb 03, 2009, 16:59:38
What a shame about the Saints match then Rik :angel:
Not for me. ;D
03/02/09 16:59:58
Speed Down 358.93 Kbps ( 0.4 Mbps )
Speed Up 370.42 Kbps ( 0.4 Mbps )
Port 8095
Server speedtest1.thinkbroadband.com
IP Address <IP address removed by Rik>
:bawl:
Have you rebooted your router, David?
:thumb: Have now :ithank:
Date 03/02/09 17:23:09
Speed Down 4977.28 Kbps ( 4.9 Mbps )
Speed Up 378.41 Kbps ( 0.4 Mbps )
Port 8095
Server speedtest1.thinkbroadband.com
IP Address <IP address removed by Rik>
:thumb:
That's better. :)
UPDATE FROM IDNET:
One of our broadband access routers failed today which caused a cascade of problems through the network. The problems have been resolved and we are now investigating the cause of the failure. IDNet apologises to all our customers for the disruption to service. Whilst the work continues to re-balance our network, if you're experiencing speed problems please try rebooting your router.
QuoteThat's better.
Let there be light ;D
Back to the torch? ;)
;D ;D :thumb:
Firstly, IDNet would like to apologise for the network outage today. Our LNS server (that terminates broadband connections) failed and that event caused a cascade of problems: the core routers were complaining about not being able to see the routes to broadband customers which meant that our office leased-line to London couldn't access our Status Page, to update it; Our phone system couldn't cope with a 1,000 fold increase in our usual call volume (we'll be taking this up with our 0800 provider too); And when we managed to get the LNS server back up one of our Centrals (the new one) didn't respond which meant that the remaining Centrals quickly became congested. We do not yet fully understand what caused the problem with the LNS server and we are still investigating.
And all this just when we thought we were getting on top of the latency issue...
If anyone is still experiencing poor performance please reboot your router as we have blocked any new logins through to the 'old' Centrals in order to utilise the capacity in the new Central.
Again apologies to all and we can assure you that we will be taking steps in order to ensure that this does not happen again.
Regards
Simon
Thanks, Simon. :thumb:
Best move Simon's post to the Announcements forum, that way everyone can see it ;)
I did think about it, but it's more of an 'in thread' post, if you know what I mean, Glenn. :)
:thnks: Simon...I got the gist of all that ;D
Could always copy it to Announcements, Rik. :)
It had crossed my mind...
Quote from: Simon_idnet on Feb 03, 2009, 17:57:25
Firstly, IDNet would like to apologise for the network outage today. ....
:solved:
Thanks for the post Simon. Doo happens. What counts is leveling with customers and fixing it. So well done. The 20:20 hindsighters will still give you grief. Invariably they don't doo because they don't do.
That's good. :thumb:
everything working ok now :thumb: :thnks: my daughter bless her, (college closed) was trying everything this afternoon to get it going, and giving me grief on the phone at work ::)
You eventually get to to the point where you have been kicked doo-less by some of the largest corporations in the world. Strangely, when its on the fan, the most successful kick least and help most. Then comes the day, as come it will for a' that, when you have what they all need, and you return the favour to friends. And for the rest; you take the money and smile; but never go the extra mile.
re boot has done the trick for me. did notice some slowness earlier and pages just hanging. Just got in and caught up with the goings on. Thanks for the up dates from IDNet and to what seems like a fix. :thumb:
pings still high for me :(
Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 162 ms 167 ms 221 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 * 139 ms 137 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 * 163 ms 155 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 158 ms 162 ms 161 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 157 ms 155 ms 146 ms www.idnet.net [212.69.36.10]
Trace complete.
Have you rebooted, Paul?
I blame Rik, for kicking me out ;D I didn't know what to do, helpless :'(
Quote from: Simon_idnet on Feb 03, 2009, 17:57:25
Firstly, IDNet would like to apologise for the network outage today. Our LNS server (that terminates broadband connections) failed and that event caused a cascade of problems: the core routers were complaining about not being able to see the routes to broadband customers which meant that our office leased-line to London couldn't access our Status Page, to update it; Our phone system couldn't cope with a 1,000 fold increase in our usual call volume (we'll be taking this up with our 0800 provider too); And when we managed to get the LNS server back up one of our Centrals (the new one) didn't respond which meant that the remaining Centrals quickly became congested. We do not yet fully understand what caused the problem with the LNS server and we are still investigating.
And all this just when we thought we were getting on top of the latency issue...
If anyone is still experiencing poor performance please reboot your router as we have blocked any new logins through to the 'old' Centrals in order to utilise the capacity in the new Central.
Again apologies to all and we can assure you that we will be taking steps in order to ensure that this does not happen again.
Regards
Simon
So a couple of questions...
I find it absolutely absurd that your office has ONE leased line. Why not a backup ADSL connection from another provider? Why not a backup ISDN line? Why not even a pay as you go datacard on someone's laptop to allow you to update the status page? Absolutely ridiculous. It this something you're going to fix? Surely someone has a big enough brain to contemplate a BACKUP connection?
Of course, what a suprise that none of the "faithful" pointed the above out.
Phone systems - glad you're blaming someone else. Possibly their fault, possibly not.
Would love to hear more details on the LNS server.
Also, other ISPs have multiple LNS servers - does IDNet?
Quote from: Sebby on Feb 03, 2009, 22:12:00
Have you rebooted, Paul?
Yep. Pings back to normal for now, will check again tonight.
Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 15 ms 13 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 13 ms 13 ms 13 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 13 ms 14 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 13 ms 15 ms 14 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 14 ms 14 ms www.idnet.net [212.69.36.10]
Trace complete.
Results from http://www.speed.io
(Copied on 2009-02-04 08:23:11)
Download: 1692 Kbit/s
Upload : 389 kbit/s
Connects : 1387 conn/min
Ping: 44 ms
Back to my normal stats I think, hope it now stays that way :fingers:
Again this morning! :shake:
Again in what sense, Jill?
Here quite early, but it only lasted 5 minutes or so, net dead :shake:
I've got nothing showing in my router logs, could it have been a local problem?
Quote from: ducky22 on Feb 04, 2009, 01:49:56
So a couple of questions...
I find it absolutely absurd that your office has ONE leased line. Why not a backup ADSL connection from another provider? Why not a backup ISDN line? Why not even a pay as you go datacard on someone's laptop to allow you to update the status page? Absolutely ridiculous. It this something you're going to fix? Surely someone has a big enough brain to contemplate a BACKUP connection?
Of course, what a suprise that none of the "faithful" pointed the above out.
Phone systems - glad you're blaming someone else. Possibly their fault, possibly not.
Would love to hear more details on the LNS server.
You should also address these comments direct to IDNet. This is an unofficial support forum. We are not part of the company, and IDNet don't read every post here.
ahha glad to see that there was a known issue last nite.
cos trying to do a bit of gaming last nite was painful and it had been fine for weeks now so was a real shock to get such a bad nite of latency.
hopefully resolved for tonite :)
Quote from: Rik on Feb 04, 2009, 09:55:02
I've got nothing showing in my router logs, could it have been a local problem?
:dunno: But It's OK now :thumb:
Happened again for me too (i.e. same as Jill) - ok now though.
We've not heard anything, so you'd need to contact IDNet, sorry.
I thought Simon_idnet did the right thing posting an overview of yesterday's problems on the forum. I can't see how it helps to pick it apart after the event, on the contrary, this acts as a disincentive.
We lost connection again from 10:35am to 10:45am this Wednesday morning, and are back to the slow ping rates.
Give support a call.
My connection is also acting up. Pages are taking ages to load.
Try re-booting your router, Lona. If that doesn't help, give support a ring.
Reading 30ms again here, and I didn't even reset anything.
That'll teach you for upgrading the LNS to Vista... ;)
I agree it's a little bit surprising there isn't a backup connection, unless it was some sort of internal routing issue and I don't quite follow. Even we have a backup using GPRS (it's real slow, but it works).
:hiding: Is it safe? ......... :hide:
Mo
;D
Is anything truly safe, Mo? ;)
:dig: Anderson shelter foundations ;D
:ok:
:hehe: Room for 4 ;D
Would that be a sea view, sir?
Always wanted an Anderson .......... we only had room for a Morrison!!
Mo
;D
Rik, why am I getting taken back to the top of the page every time? Is it by design?
You shouldn't be, Mo, is the page fully loaded?
QuoteWould that be a sea view, sir?
Beachy Head seems appropriate ;D
Only to lemmings. :)
*whooooshh*
(that was the sound of the past few dozen posts flying over my head)
Time for a leap of faith I think.........anyone for a cigar ?
Quote from: esh on Feb 04, 2009, 13:03:22
*whooooshh*
(that was the sound of the past few dozen posts flying over my head)
You'll get used to us, Esh, we used to write the Goons sketches in a former life. ;)
Quote from: Rik on Feb 04, 2009, 13:01:55
You shouldn't be, Mo, is the page fully loaded?
Yes Rik. But I am using IE 8. Could be that?
Gotta go ....... Lunch is on the table. ;D
Saved you a place Mo....but if Jill asks for one..................well thats life ;D >:D
Quote from: MoHux on Feb 04, 2009, 13:05:43
Yes Rik. But I am using IE 8. Could be that?
Gotta go ....... Lunch is on the table. ;D
Mine too. :thumb:
Quote from: esh on Feb 04, 2009, 12:19:45
That'll teach you for upgrading the LNS to Vista... ;)
:lol:
It would certainly explain the slowness. :P
What on earth happened to my thread? Goodness, looks like I missed a lot by being at college, and I'm glad of it. I hate arguing :(
Quote from: Danni on Feb 04, 2009, 20:12:02
What on earth happened to my thread?
You've been Nettered! ;D
Yet again disconnected... anyone else lose PPP?
Not here Ducky I have been here all day and no problems
Quote from: ducky22 on Feb 05, 2009, 21:18:54
Yet again disconnected... anyone else lose PPP?
yep,i just lagged out of irc and msn,sigh and sigh again...
Sorry it's no consolation guys, but no problems here on GW5.
Not here, Ducky, but I know Simon was working on balancing the centrals last night, so its possible some PPP sessions got dropped in the process.
just makes me happy to think that a router reboot when this first started and i havnt had any issues since. Something finanly going right in my life though pre router reboot it reminded me of the fun of being on Tiscali before i got hit with there AUP