Since 1.00am last night my connection has been losing service every few minutes. There are no red lights on the router and nothing reported in the router log, just a complete loss of throughput lasting between one and two minutes. As no one else appears to be having problems it most be local to me but I can't for the life of me work out what is causing it.
Does it do the same from the test socket behind the master socket?
I had a 2Wire 2700 constantly rebooting, it turned out to be a psu issue
Quote from: Glenn on Jul 25, 2009, 15:05:17
Does it do the same from the test socket behind the master socket?
I don't have a test socket Glenn, just the most basic master socket with no extentions.
If the router isn't logging anything, Zap, would Routerstats be worth a try?
Quote from: Glenn on Jul 25, 2009, 15:06:17
I had a 2Wire 2700 constantly rebooting, it turned out to be a psu issue
I've had that too.
I had a PSU go as well. The power light went, and stayed, red.
Mine kept, in effect, re-booting, it would just make the connection then drop again.
Quote from: Rik on Jul 25, 2009, 15:18:42
If the router isn't logging anything, Zap, would Routerstats be worth a try?
RouterStats indicates a complete loss of service every 5 to 10 minutes. I'm tempted to try another router but as silly as it sounds given my current problem, dropping the connecting is likely to push my sync speed down which always takes my throughput with it even though the two figures are megabits apart. At least that's what's happened in recent weeks. Unfortunately my throughput is currently so low any further loss would put me off the net.
What are you currently using and what could you switch to, Zap?
It'a Netgear DG834Gv5 and I currently have access to two Netgear DG834Gv3 as well as a Speedtouch router although I'm not sure if that's WBC compatible.
I'd take the gamble and switch, myself, Zap. If you're anywhere near me, I have a spare you could borrow if you wanted to try something different.
Thanks for the offer Rik :thumb:
I'll probably swap it out Monday morning when support are back :)
Quote from: zappaDPJ on Jul 25, 2009, 15:58:29
It'a Netgear DG834Gv5 and I currently have access to two Netgear DG834Gv3 as well as a Speedtouch router although I'm not sure if that's WBC compatible.
I had a similar problem with my Netgears (all throughput would just stop, even though sync stayed).
I've had a solid connection on WBC with my Speedtouch 585v6 (and faster than my Netgear DG834v2 and v3) so it may be worth giving it a go.
Steve
Netgear yet again !!! Just been over on TBB reading the o2 forum and there are some very long threads indeed on the subject of Netgears, they seem to be having loss of routing......
and my Netgear ...not techy but seems odd to me.
Quote from: zappaDPJ on Jul 25, 2009, 15:58:29
It'a Netgear DG834Gv5 and I currently have access to two Netgear DG834Gv3 as well as a Speedtouch router although I'm not sure if that's WBC compatible.
Certainly the DG834Gv3 (with latest firmware) is. I know Steve (D-Dan) uses a SpeedTouch.
Thanks for the replies. I tried a number of routers I but found I was no better off. However 24 hours after the problem started it suddenly went away ??? Unfortunately so did my DSL connection rate, IP profile and throughput which all dropped to lower levels. Hopefully BT's comedy show will send it back up at some point ::)
Not on WBC here but my Netgear DG834N on the latest firmware is great, the linskys WRT610N is really bad. I think most newer routers now are not great, features over usability sadly, and as far as O2 I never had any issues with the broadcom chipsets routers on their LLU product but the newer v5 is conextant and the older v3 is Texas which might explain issues.
I use a Netgear DG834N and its not given me any problems in 2 years, YMMV as always with these devices :)
The O2/Be issue appears to be a setup issue at their end and not the routers.
I had this problem a few weeks or so ago too, then out of the blue it just stopped happening, must have been BT doing some work.
It happened again last night. My current thoughput is still really poor and in addition my latency which was originally very good when I first switched to WBC has now quadrupled, probably due to interleaving.
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6386 kbps(DOWN-STREAM), 1229 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 2012 kbps
If you wish to discuss these results please contact your ISP.
I'm going to migrate to AAISP as they think, based on my stats, they can get me a 14.0 Mbps data stream. To be honest, I'll be more than happy with what I had on Max which was close on full sync.
Does anyone happen to know how quickly IDNet will cut off my email? I need to make other arrangements and it could take a week or two to set it all up.
I don't want to influence your decision to move, Zap, but would it worth holding fire for a couple more days, to see how David gets on with AAISP? They don't seem to have quite managed to solve his problems so far.
I'm pretty sure you can pay Idnet a few quid each month to host your email anyway. :)
Quote from: Simon on Jul 28, 2009, 22:06:24
I don't want to influence your decision to move, Zap, but would it worth holding fire for a couple more days, to see how David gets on with AAISP? They don't seem to have quite managed to solve his problems so far.
I don't understand why AAISP can be any better or worse than idnet. The BT part is the same for both ISPs unless idnet are under resourced for WBC and the hostlink is congested. I don't think either of those should apply. According to Simon_idnet 4-5% of their 500 WBC are having issues and as yet neither idnet or BT have a solution.
Good luck if you decide to migrate but as Simon said re David it would be nice to see evidence of possible improvement.
It depends whether the problem that some IDNet users are experiencing is down to IDNet as opposed to BT (that's an if, because we still don't know definitively).
The problem is BT and/or Openreach have lied either to me or IDNet which has left me in limbo. The engineer told me that my line from the faceplate to the exchange is fine, capable in his opinion of 14.0-16.0 Mbps. He told me the problem was an issue at the exchange and that a 'lift and shift' would be requested. BT simply reported back to IDNet that the line was fine with no further detail.
Before I moved to this house I actually went as far as checking how much throughput the BT line was capable of. The previous resident was with Be and had a sync rate of around 16000. When I first moved in I went with Be and had a sync rate just below that but I migrated to IDNet because of the peak time contention on Be's network. I had near full sync with Max, no disconnects and apart from some short lived latency issues everything was fine.
So now I'm stuck on WBC with a fault that means I can't work to anywhere near my full potential during the day (I need over 2.5Mbs + some headroom) and these continual interuptions of service mean I can't adequately run my on-line gaming organisation in the evenings which numbers over 400 people. My daughter had to go to an Internet cafe in the middle of her exams and she that must be obeyed has been restricted to using her employer's connection for her needs. All in all the switch to WBC has been two months of a nightmare and there's no end in sight.
I'd prefer to stick with IDNet but they haven't been able to sort the problem out in two months and I can't see any way forward. I know that my line will support at least quadruple what it is currently giving me because it has done so for 10 months prior to WBC. AAISP have had all the data and they too are convinced that my line can do a lot better than 2Mbs and have offer a money back guarantee on it, I can't see that I have much to lose.
Sorry if this sounds like a rant but desperation has started to set in. I've was told categorically on three occasions that I could switch back to Max if WBC did not work out but this doesn't seem to be the case now and I believe I'm now stuck on some pseudo capped service which runs at one third below the cap in real money and it just isn't enough. I have to make other arrangements for my email which if I honest is something I should have done ages ago. Once that is in place, if things haven't improved drastically I will be moving on I'm afraid.
Oh and thanks for the feedback, I do read it and it is greatfully received :-*
I understand your frustration, Zap, and I wish I had an answer for you. As I think you know, my move to WBC has been smooth, but I don't think the product is mature and certainly my line is less stable now. At the time IDNet launched WBC, they did not know that BT would not revert people, but that's turned out to be the case. :( I am assured that the hostlink is 'running light, ie at a small percentage of its capacity, so there does seem to be some issue with the BT infrastructure on this problem.
Whatever you decide to do, don't be a stranger, you don't have to be a customer to be a Netter, and we'd like to know how you get on. :)
Indeed let us know how you get on, theres a wide range of issues effecting people moving to WBC and it'd be interesting to see if moving to another ISP cures the issue, I have to admit it's crossed my mind.
IDNet support have been in touch today with an update so I'm holding fire for now. I'll keep you informed.
That's good, Zap. :)
Good to know, Zap. :)
:fingers:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>ping idnet.com
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=236ms TTL=59
Reply from 212.69.36.10: bytes=32 time=300ms TTL=59
Reply from 212.69.36.10: bytes=32 time=332ms TTL=59
Reply from 212.69.36.10: bytes=32 time=368ms 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 = 236ms, Maximum = 368ms, Average = 309ms
C:\Users\zappaDPJ>
Ouch! And that's on WBC tonight :eek4:
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6323 kbps(DOWN-STREAM), 1183 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 877 kbps
If you wish to discuss these results please contact your ISP.
I think my connection is about to disappear up its own pipe :'(
Negative sync... I'm surprised BT haven't thought of that. >:D
Well, as it happens, things got steadily worse until I couldn't even get a ping to return. I had zero throughput and then this...
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>ping idnet.com
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=9ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Reply from 212.69.36.10: bytes=32 time=8ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms 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 = 7ms, Maximum = 9ms, Average = 7ms
C:\Users\zappaDPJ>
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6323 kbps(DOWN-STREAM), 1183 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 5141 kbps
If you wish to discuss these results please contact your ISP.
So you were right Sebby, negative sync. I dissapeared up my own pipe and came out the other end :laugh: ;D
I think somewhere, in a reality not so far away, there's a malevolent gremlin laughing his b******s off everytime he twangs my line :bawl:
Blimey, those ping times are more in line with a leased-line than a DSL circuit!
Lets hope the gremlin stops twanging your line now then!
And Simon, get some sleep!
I'm issuing Temazepam to everyone tonight. :)
Quote from: Rik on Jul 30, 2009, 08:42:40
I'm issuing Temazepam to everyone tonight. :)
That'll mess up the ping time ;D
;D
It depends which port you insert it into. :evil: