Everything owned by Microsoft is down for me! MSN, Xbox Live, - the lot!

netgem21 · Mar 31, 2009, 15:43:02

OK, I still can't find anything about MTU but it's randomly started working now. Guess support found the issue. Thanks Rik!

Rik · Mar 31, 2009, 15:45:48

Not necessarily, they had no problems with the site when I spoke to them, so it may have been just that one part of the site that was affected.

What router do you have?

RichR · Mar 31, 2009, 15:49:28

For tracert on OS X either use Network Utility in /Applications/Utilities. Click on the Traceroute tab, enter the IP address you're interested in and click start.
If you're feeling brave you can use Terminal, also in /Applications/Utilities, and type traceroute www.msn.com

Rik · Mar 31, 2009, 15:51:40

Thanks, Rich, it's good to have a bilingual user around.

Sebby · Mar 31, 2009, 19:17:06

Quote from: RichR on Mar 31, 2009, 15:49:28
For tracert on OS X either use Network Utility in /Applications/Utilities. Click on the Traceroute tab, enter the IP address you're interested in and click start.
If you're feeling brave you can use Terminal, also in /Applications/Utilities, and type traceroute www.msn.com

Good to know!

D-Dan · Mar 31, 2009, 19:51:30

I have to admit that I haven't read all this thread, but I started at the beginning and came straight to the end to see if there had been a change of focus. So if this has been mentioned, I apologise.

Conficker blocks access to all sites with "microsoft" in the url, amongst others including "antivir", "conficker" and several others. A quick test would be to google "conficker" and look for a result where "conficker" is part of the URL, and try to access it. If you can't get there either, come back because there's a way around it to get to the removal tools.

Steve

Edit: BTW - the virus is set to activate tomorrow - so if you have suspicions you may be infected - act now.

Rik · Mar 31, 2009, 19:52:59

Interesting piece of lateral thinking, Steve. Thanks.

Sebby · Mar 31, 2009, 22:08:11

Quote from: D-Dan on Mar 31, 2009, 19:51:30
Edit: BTW - the virus is set to activate tomorrow - so if you have suspicions you may be infected - act now.

Exactly, act now - get rid of Windows!

Rik · Apr 01, 2009, 08:19:52

Just because you've joined the clan.

Sebby · Apr 01, 2009, 18:29:37

Exactly, I have to promote it.

Rik · Apr 01, 2009, 18:32:46

Are you up to your Captaincy yet?

Sebby · Apr 01, 2009, 18:41:26

I'm getting there!

Rik · Apr 01, 2009, 18:43:37

Let us know when to issue a Major alert.

uxbod · Apr 02, 2009, 15:55:43

would somebody please try getting to www.zimbra.com or www.zimbra.com/forums for me please ? I cannot get to any of these sites at all. Worked fine first thing this morning. Yet I get alerts of thread updates; and one of the other mods says he can connect just fine

Rik · Apr 02, 2009, 15:56:44

No problems with either here.

uxbod · Apr 02, 2009, 16:10:28

are you on gw5 Rik ?

Rik · Apr 02, 2009, 16:13:33

GW6 atm. Routing shouldn't be affected by gateway, though.

Rik · Apr 02, 2009, 16:18:38

A tracert for me shows:

tracert www.zimbra.com

Tracing route to www1.zimbra.mail.vip.ac4.yahoo.net [76.13.17.53]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms home [192.168.1.254]
2 22 ms 21 ms 23 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 22 ms 21 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 22 ms 23 ms 25 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 101 ms 102 ms 100 ms 83.245.126.11
6 101 ms 98 ms 98 ms xe-2-0-0.msr2.ac2.yahoo.com [216.115.108.127]
7 100 ms 102 ms 98 ms te-9-1.bas-b1.ac4.yahoo.com [76.13.0.207]
8 107 ms 100 ms 100 ms www1.zimbra.mail.vip.ac4.yahoo.net [76.13.17.53]

Trace complete.

uxbod · Apr 02, 2009, 16:19:39

snap ... this is so weird

Yet my traceroute is different on GW6 :-

cisco877#traceroute www.zimbra.com

Translating "www.zimbra.com"...domain server (212.69.36.3) [OK]

Type escape sequence to abort.
Tracing the route to www1.zimbra.mail.vip.ac4.yahoo.net (76.13.17.53)

1 telehouse-gw2-lo2.idnet.net (212.69.63.55) 40 msec 48 msec 48 msec
2 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 40 msec 48 msec 52 msec
3 redbus-gw2-g0-1-331.idnet.net (212.69.63.5) 40 msec 40 msec 44 msec
4 83.245.126.11 120 msec 112 msec 104 msec
5 xe-2-0-0.msr1.ac2.yahoo.com (216.115.108.123) 108 msec
xe-7-0-0.msr1.ac2.yahoo.com (216.115.108.125) 112 msec
xe-2-0-0.msr1.ac2.yahoo.com (216.115.108.123) 124 msec
6 te-8-1.bas-b1.ac4.yahoo.com (76.13.0.205) 116 msec 116 msec
te-9-1.bas-b2.ac4.yahoo.com (76.13.0.211) 112 msec
7 * * *

Rik · Apr 02, 2009, 16:28:46

It looks like your IP address may be being blocked - can you ask anyone at the site?

uxbod · Apr 02, 2009, 16:39:33

Cheers Rik ... I have pinged a couple of the employees to see if they can check it out for me ... Well gets me out of some moderating I guess

Rik · Apr 02, 2009, 17:04:18

Unfortunately, I'm not in your IP range to test, and IDNet are all in the same range as me.

If it's of any use, I can ping you fine (I'll PM a tracert if you want one).

uxbod · Apr 02, 2009, 17:19:51

It a internal network issue @ Yahoo

Thanks for your help Rik (again)

Rik · Apr 02, 2009, 17:23:03

NP.