I'm having to post this message from my phone as any website I try and access from the pc results in a bt wholesale service message appearing on screen.
Any network problems I'm not aware of?
Still getting this message but I'm able to ping websites from the command prompt.
I had that problem not so long ago. It happened soon after IDNet had an issue with one of their DNS servers I believe but I'm not sure that was necessarily the cause. I think I eventually resolved it by turning my modem off for quite some time i.e. longer than 10 minutes. I'd give that a try if you haven't done so already :fingers:
I went to bed early last night at 12.15am due to no connectivity at all. LAN UP, DSL Light on, Internet light on.. but windows 7 complaining there was a problem with internet connectivity.
all pings to idnet dns unsuccessful.
So its possible there was a fault last night.. or... BT were doing their 'after midnight lets not tell anyones customers in advance maintenance'
DSL4 i'm on, are you also?
I had a brief (~ a minute) loss of internet at around 6:30 this morning, but no problems now or last night (that I know of).
Also on DSL4.
I lost my connection just after midnight last night, don't know what time it came back as I switched the router off, internet light was off so I suspect that BT were up to something
Looks like it was this http://status.aaisp.net.uk/?incident=589 mine's connected to Manchester anyway
Quote from: tobykim on Oct 08, 2010, 10:48:16
Looks like it was this http://status.aaisp.net.uk/?incident=589 mine's connected to Manchester anyway
QuoteThe issue at 06:33:42 looks like the end of a major issue within BT but somehow triggered a crash on our LNS.
To within a few seconds that's when my connection went down, so it seems to have affected IDNet as well.
I'm back again!
It appears that a couple of you lost your connection completely but that's not what occurred to me.
Overnight regardless of browser or website all that would appear on screen was a generic BT Wholesale Service Information message HOWEVER my connection was still live as I could ping websites perfectly from the command prompt.
Odd...
:welcback: Griff. :)
Quote from: .Griff. on Oct 08, 2010, 11:53:52
Odd...
Very. A major crash within BT was reported overnight for the Manchester area but, due to the topography of their network, may have spilled over into a larger geographic spread.
last half an hour been getting
BT WHOLESALE:
SERVICE INFORMATION
Close Window
You have been connected to this page due to one of the following reasons. You must now shut down your browser and Internet applications before attempting to reconnect.
1. The BTWholesale access circuit to your Service Provider is currently down.
Your service should be resumed soon.
Or
2. You are testing your local connection to BT using
'bt_test_user@startup_domain'
Or
3. You are testing your connection to your Service Provider using 'bt_test_user@domain' where domain is your Service Provider domain name.
Or
4. Your Service Provider is currently unable to accept your connection request please wait until service is restored or contact your Service Provider for further information.
Or
5. You have attempted to access an invalid Service Provider domain.
I wonder if this http://status.zensupport.co.uk/index.php?serviceid=5&incidentid=1982&simple=1 had any bearing on it?
I don't think IDNet have any edge routers in Manchester do they but if it was a BRAS issue it could have resulted in the problem.
I think but am not sure that you see that screen if there's an issue completing the tunnel between you and your ISP but if that were true your pings should have gone nowhere unless it directs them over BTnet but prevents HTTP traffic.
Weird.
It's a message that's been seen on ADSL too, Griff. My guess would be BT playing with the network.
Seems to be appearing when i'm using the idnet dns addresses, i've had to use opendns to bypass this on both pc's here.
In that case, let support know, maybe the servers had a little hiccough.
Nothing to do with Idnet dns. I use Opendns and still got that message on screen.
Thanks, Griff. As you were, Jase. ;)