Power cut and now problems,any help appreciated

Started by MarkE, Jun 01, 2009, 11:04:02

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

MarkE

Right around 12am in Berkshire (Shinfield area) last night I had a power cut,the power instantly tried to come back on but failed,no problem I thought to myself.At 2am it was back on and for some
strange reason it took ping times with it,they have climbed from 10ms to 60 and 80,I thought possibly my router may need a power down so did that for 2 hours and also tried numerous router
factory resets,but to no use,does anyone have an idea of what might have happened? Even browsing the web and reading mail is clunky now.

The Netgear router is on a surge protector.


my stats currently are


ADSL Link     Downstream     Upstream
Connection Speed    8128 kbps    832 kbps
Line Attenuation    21.0 db    11.0 db
Noise Margin    8.3 db    12.0 db

Rik

Your sync is fine, can you do a BT test to check your profile, Mark?
Rik
--------------------

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

MarkE

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 - 6677 kbps

Rik

So it's just pings. You don't appear to have interleaving on, so I'm at a loss to suggest what to do. It's probably worth a call to support as you've already done everything I would have suggested.
Rik
--------------------

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

MarkE

Thanks Rik,calling support was the first thing i did,but the guy was at a loss as to whats caused it,he mentioned its possible that the router is now damaged due to the power cut.

Just to give you some idea,after the powercut I had immense trouble getting the router to work again,it took a lot of router reboots to get anything and now it is working,the ping times are
just cranky,I find it more than a little odd that I have had a power cut and now ping times have gone as well.

I am confused as to what to do,I do not have a spare router and the thought of spending £80 on a decent new one right now,does not overly amuse me  >:(

Rik

Are you anywhere near me, Mark, I have a spare you could try.

You shouldn't have to pay more than about £45 for a new Netgear, btw, with a 2700 from eBay being in the range of £10-20.
Rik
--------------------

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

MarkE

That is very nice of you to offer Rik,I am in Berkshire (Shinfield).

Thanks for the router suggestions,I will take a look,is it possible that last nights power cut has done something to my exchange (Hyde end road Spencers wood)

Rik

It's unlikely to be an exchange issue, but a real possibility that the spiking which occurs around a power cut has got through your defences. For that reason, I run my router on its own UPS. If you want to try it, I could let you have a Netgear DG834 v2 to test with. I would send you the 834G, but I might be needing it next week when I move to WBC. :)
Rik
--------------------

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

MarkE

That is most kind of you Rik,but I do not wish to impose,so I will take a look at the routers you have suggested,thank you very much chap  :thumb:

Rik

If you change your mind, Mark, just PM me your address. :)
Rik
--------------------

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

MarkE

Thank you Rik,that is most kind of you,I will pm you if i require it,once again many thanks  :)

Rik

Rik
--------------------

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

MarkE

I have installed my adsl card and removed the router,I am guessing that the ping times problem is Idnet again  :shake:

ping times to multiplay.co.uk

Reply from 85.236.96.22: bytes=32 time=52ms TTL=124
Reply from 85.236.96.22: bytes=32 time=69ms TTL=124
Reply from 85.236.96.22: bytes=32 time=43ms TTL=124
Reply from 85.236.96.22: bytes=32 time=39ms TTL=124

normally in the 10s and 14s


ping times to google.co.uk

Reply from 72.14.221.104: bytes=32 time=39ms TTL=246
Reply from 72.14.221.104: bytes=32 time=43ms TTL=246
Reply from 72.14.221.104: bytes=32 time=45ms TTL=246
Reply from 72.14.221.104: bytes=32 time=54ms TTL=246



pings for idnet

Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59



Rik

They do seem high, atm. I'd expect 23ms to IDNet:

ping www.multiplay.co.uk

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=37ms TTL=124
Reply from 85.236.96.22: bytes=32 time=37ms TTL=124
Reply from 85.236.96.22: bytes=32 time=38ms TTL=124
Reply from 85.236.96.22: bytes=32 time=51ms 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 = 37ms, Maximum = 51ms, Average = 40ms

ping www.google.co.uk

Pinging www.l.google.com [209.85.227.147] with 32 bytes of data:

Reply from 209.85.227.147: bytes=32 time=42ms TTL=247
Reply from 209.85.227.147: bytes=32 time=41ms TTL=247
Reply from 209.85.227.147: bytes=32 time=58ms TTL=247
Reply from 209.85.227.147: bytes=32 time=61ms TTL=247

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

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=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=58ms TTL=59
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59

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

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

MarkE

Any news as to why the sudden high ping times Rik?  Nothing I try  seems to be stabilizing mine at the moment

Rik

I checked, Mark, but IDNet can see nothing their end to explain it.  :(
Rik
--------------------

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

Glenn

Mark, I work in Reading, so if you need to borrow a router I could drop my 2700 off.
Glenn
--------------------

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

MarkE

Thats very nice of you Glenn,but i had installed my adsl pci card and it was the same pingwise,so I am pretty sure its not router related to the power cut now  :'(

Thank you for the offer though chap.

MarkE

Tried a different router today,ping times still screwed up massively,so as expected this is yet again an Idnet problem I presume,I did actually think the 100ms ping times were a thing of the past quite disappointed.

Another thing I thought worth mentioning is that my pings are getting worse after peak time like 12am or so  :eek4:

Sebby

You must get on contact with IDNet, in that case.

Steve

Since some Netgears on certain exchanges will give a full sync. Have you checked interleave's not been slipped on?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

MarkE

I just phoned support Steve and asked,interleaving is off and they can not understand why my browsing is clunky and why ping times to multiplay.co.uk and google have gone through the roof.
They suggested it was contention ratio at the exchange,however it had been fine for 2 months since rejoining Idnet.

Rik

Rik
--------------------

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

MarkE


Rik

Rik
--------------------

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

MarkE


Rik

Rik
--------------------

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