Hi
Have been down all day.
Router connects, but no webpages load.
Pinged various hosts, only 80% success so packets are getting dropped.
BT exchange checker had a problem with my dialling code 01227 during the night but that is resolved.
Router rebooted numerous times and also switched off for a couple of hours, no luck though.
Spoke to IDNet tech support, they said its a problem at their end, so not related to my exchange.
However as I am only a residential customer and its an IDNet problem, it won't be looked into until Monday morning.
Anyone else in the same boat?
Both BT and LLU lines are OK here...
Fine here too on a FTTC line
Fine here.
All I can find is;
Dialing code affected 01227
Time resolved: Sat 28/07/2012 at 02:30
Dialling codes affected: 01227
We've fixed the problem in the Canterbury area so your broadband should now be working. If it isn't, try restarting your modem or router.
Have you tried restarting the router, maybe switch it off for 30 mins first?
Yes that was the same info re 01227 that I'd seen, and had tried reboot and power off for hour etc.
Surprised that a dropped packet type problem would be an IDNet problem limited to a single customer, although I do admit to knowing next to nothing about how their infrastructure works!
I had a problem with same symptoms last year back and that was traced to an exchange fault, however IDNet say the prob this time is def their end.
Let us know how you get on, I'm a bit puzzled by this one, if the support was OOH they don't usually know where the issue lies. Normally individual user problems relate to accessing the IDNet network ie it's on or off regarding a PPP session. . The rest is normally down to BT.
Update
Well it was back up this morning I am told, but when I came to use it earlier this afternoon we were down again.
Router also now struggling to maintain PPP session, keeps dropping off then saying "LCP allowed to come up"
Webpages still not loading and ping response indicates packet dropping still, so no change really.
Remove power from the router for 30 minutes which allows the session to expire, then reconnect and see what happens.
Have tried that a few times pctech, been off for an hour or too multiple times, still the same though.
Very annoying that if you are only residential and your problems start Saturday morning they don't get looked at until Monday.
Bit of a weird one that.
Update 2:
Well it appears that whoever I spoke to in OOH support who said it was "definitely an IDNet issue" wasn't actually correct, as Steve alluded to OOH support would be unlikely to know what the problem was anyhow.
I had a phone call from Support this morning stating that they can't see anything wrong from their end and my telephone line appears to be fine, and that I should check adsl filters, plugging into the master socket and trying a different adsl router etc.
I had tried all of that except for the router and I have now managed to borrow one to try tonight.
My gut feeling is that it will turn out to be an exchange issue as originally suspected (especially as there were problems reported with my dialling code on Friday night/Saturday morning). Just annoying that the red herring of it being an IDNEt issue was thrown in there!
Oh well, fingers crossed it's back up soon.
I thought it was going to be between you and the exchange, perhaps I should have been more forcible in my opinion.
Indeed Steve, it did seem the most logical possibility.
Well I got home from work yesterday, and magically it was working.
Router had been connected to PPP session for an hour or so, and stayed up all evening.
I assume that there may have been some ongoing fallout from the issue reported by BT with my dialling code in the wee hours of Saturday morning, and that they were remedied Monday afternoon.
So we have a happy household again! :)
But then again it's always easier for me to be wise after the event. :)
This one's obviously been resolved but this website can be useful:
http://www.downforeveryoneorjustme.com/