404, Routing and Squirrels!

Technical Ben · Mar 26, 2011, 09:27:23

Scheduled repairs? Seems funny how it happened at 1 in the morning. I understand it can be annoying, but at that time in the morning it's going to take more than 15 mins to get to the site and fix and server/line breakdowns.

Simon · Mar 26, 2011, 10:29:56

Thanks, Simon. We can only assume from the lack of further responses, that the issue is resolved.

Rik · Mar 26, 2011, 10:57:02

The topology of BT's network makes Stepney Green a particular vulnerability. BT don't seem to believe in built-in redundancy, unless you work for them, of course.

silverblade · Mar 27, 2011, 04:58:32

It's gone funny again just now (4:55 AM) with exactly the same symptoms.

sof2er · Mar 27, 2011, 04:59:36

Same here again...........................

Gary · Mar 27, 2011, 09:15:08

Quote from: silverblade on Mar 27, 2011, 04:58:32
It's gone funny again just now (4:55 AM) with exactly the same symptoms.

See BT for details maybe

Glad I was asleep.

wecpcs · Mar 27, 2011, 12:24:52

Quote from: sof2er on Mar 27, 2011, 04:59:36
Same here again...........................

I am also having problems, as I cannot access any of Microsoft's web sites including forums and Live. So something is still terribly wrong somewhere in the system.

I hope it gets sorted very soon as I want to reinstall my Windows Home Server as something has screwed up my Remote Access totally, despite it being configured manually in the router as per normal. It seemed to go pear-shaped about a week ago after an MS update. Without access to MS sites it will be impossible to carry out a re-installation successfully.

Colin

Rik · Mar 27, 2011, 12:26:11

Has anyone told support of their problems?

wecpcs · Mar 27, 2011, 12:34:28

Quote from: Rik on Mar 27, 2011, 12:26:11
Has anyone told support of their problems?

I thought there was no point in that on a Sunday as they are not there and it is not a total loss of service.

Colin

Rik · Mar 27, 2011, 12:40:31

It's worth an email, Colin, Simon's already picked up on this thread.

Gary · Mar 27, 2011, 13:39:32

Quote from: wecpcs on Mar 27, 2011, 12:24:52
I am also having problems, as I cannot access any of Microsoft's web sites including forums and Live. So something is still terribly wrong somewhere in the system.

I hope it gets sorted very soon as I want to reinstall my Windows Home Server as something has screwed up my Remote Access totally, despite it being configured manually in the router as per normal. It seemed to go pear-shaped about a week ago after an MS update. Without access to MS sites it will be impossible to carry out a re-installation successfully.

Colin

No issues here Colin, have uou changed DND servers to see if that helps?

dudwell · Mar 27, 2011, 14:02:06

Hotmail not working here. I'm on OpenDNS.

Edit: changing to IDNet's DNS doesn't help.

Gary · Mar 27, 2011, 14:10:48

Talk of the devil, mines stopped working now, no access to msn, hotmail or messenger

the joys of computing time to do Sunday type things and go out me thinks.

Edit: Using Norton DNS, messenger is working using my iPhone via a third party app though. MSN, hotmail fine via O2

zappaDPJ · Mar 27, 2011, 14:12:26

I've also been having problems since around 5.00am e.g.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>tracert http://www.microsoft.com
Unable to resolve target system name http://www.microsoft.com.

C:\Users\zappaDPJ>

Gary · Mar 27, 2011, 14:20:15

Quote from: zappaDPJ on Mar 27, 2011, 14:12:26
I've also been having problems since around 5.00am e.g.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>tracert http://www.microsoft.com
Unable to resolve target system name http://www.microsoft.com.

C:\Users\zappaDPJ>

Well if I can get to it via O2's network zap and using multiple DNS servers people cannot get to it via IDNet is that showing IDNet at fault? I just called my neighbour and he can get on fine via Sky's service

zappaDPJ · Mar 27, 2011, 14:27:48

We've been at a friends house most of the morning and I can access Microsoft's site from their AOL connection. I was hoping things would be resolved by now but apparently not so I'm off again.

Gary · Mar 27, 2011, 14:30:05

Quote from: zappaDPJ on Mar 27, 2011, 14:27:48
We've been at a friends house most of the morning and I can access Microsoft's site from their AOL connection. I was hoping things would be resolved by now but apparently not so I'm off again.

Xilo is looking more tempting by the day right now

JB · Mar 27, 2011, 15:03:19

No MSN for me via IDNet. Tried IDNet, Norton and Open DNS servers.

Steve · Mar 27, 2011, 15:05:51

Just to confirm MSN.com is up but not currently accessible via an IDNet connection with any DNS server.

JB · Mar 27, 2011, 15:07:26

Thanks Steve.

Edit: Can access via 'hidemyass' proxy.

cavillas · Mar 27, 2011, 15:14:41

There doesn't seem to be much news regarding this problem at the moment and it does seem to be widespread amongst Idnett users. ANy news would be helpful, please.

JB · Mar 27, 2011, 15:16:23

My MSN has just connected. I'll see if it stays up.

Steve · Mar 27, 2011, 15:16:53

I've just sent an email to support.

cavillas · Mar 27, 2011, 15:23:32

Tried this Trace and it seems to be ok until the first node of Microsoft, all seems to go ok through Telehouse Idnet and just beyond.

Tried the same to www.msn.com with the same results.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [65.55.12.249]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.0.1]
2 22 ms 21 ms 21 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 22 ms 21 ms 21 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 62 ms 38 ms 112 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

5 22 ms 22 ms 21 ms igblmdistc7504.uk.msft.net [195.66.224.140]
6 21 ms 21 ms 21 ms ge-5-2-0-0.lts-64cb-1a.ntwk.msn.net [207.46.42.1
52]
7 100 ms 99 ms 99 ms so-7-1-0-0.ash-64cb-1b.ntwk.msn.net [213.199.144
.158]
8 99 ms 99 ms 99 ms ge-0-0-0-0.ash-64cb-1a.ntwk.msn.net [207.46.43.2
]
9 166 ms 164 ms 163 ms ge-5-0-0-0.co2-64c-1a.ntwk.msn.net [207.46.40.80
]
10 164 ms 163 ms 163 ms ge-2-0-0-0.co1-64c-1a.ntwk.msn.net [207.46.43.16
4]
11 162 ms 161 ms 162 ms xe-0-1-0-0.co1-96c-1a.ntwk.msn.net [207.46.33.17
7]
12 * * * Request timed out.
13 * * * Request timed out.
14 * *

Simon_idnet · Mar 27, 2011, 15:37:31

We were receiving the route to Microsoft via the Linx Route Servers. I've now disabled that peering in order to force the traffic through another route and that seems to have cleared it. I've opened a ticket with Microsoft to alert them.
Simon