Almondsbury nightmare

Don't know if anybody gas seen this debacle?

Almondsbury recently turned on thanks to BDUK cash, but not one connection has worked. Everybody is getting authentication errors, but the Openreach routers seem to be connecting.

Anybody experienced this before? Any advice?

All providers? All hardware?

There will be some with the white openreach modems and secondary router, and some with HH5, BrightBox2 or latest SkyHub

Some routers do seem to take a while to get their act together, i.e. 5 to 10 minutes from when first connected, which seems forever when waiting for them, and I even after two months if I restart everything I get the odd timeout doing the PPPoE stuff.

If it is everyone and all providers and is JUST one cabinet affected, then wiring in cabinet has been done wrong, or a failure in the actual VDSL2 DSLAM

It appears it's everyone. Check the comments. Not one person has managed to connect.

Mine has been retrying all afternoon. There's some who had kit installed yesterday who still aren't connected.

I've counted at least three cabinets - including my own - with people having the same issue.

Sent off an email, in the meantime keep an eye on pages like

http://aaisp-btmso.blogspot.co.uk/

Cannot see anything relevant. Could be an issue with the handover node kit at the exchange, but there are stories around suggesting first customers went live in December (or was that in Bradley Stoke but on next door exchange?)

Thanks Andrew - your help is very much appreciated.

December was via Filton. Some houses in south of town on neighbouring exchange.

Visit from Kelly today to install Fibre (FTTC) connection.

All appeared to go well, but keep getting a PPP authentication error. So, I am left with no internet connection until PlusNet can resolve this.

PPP authentication issues are usually simple to fix, so puzzled why PlusNet are quoting a 4 day fix.

If you are off the same exchange as the OP is posting about, then it suggests something a little more major is going wrong.

I suspect a router config issue in the BT network. Hopefully sorted out by now