Microsoft Mesh still up?

i had an email that said that the service was to go away on the 13th. but my mesh clients are still working and can still log in.

It will go away. Just move to SkyDrive already, which also does the same individual folder sync.

Annoyingly, SkyDrive is entirely broken for me.

There seems to be a routing configuration problem somewhere between me and SkyDrive, leaving me unable to reach the content server used for my account (it's not every content server though, I've downloaded public files from other accounts just fine).

The result is that while the metro Skydrive app and web site can list the file, anything besides Office documents cannot be downloaded or viewed. The desktop SkyDrive app refuses to sign in.

This is extremely annoying, but since the issue lies at some server between here and there that only has an IP address (tracert can't resolve a name for it), I have no idea how to fix it.

Try other computer and see if it is account related or device related. I have other account issues as well, like I cannot register VS Express because my account is screwed up.

1 hour ago, magicalclick wrote

Try other computer and see if it is account related or device related. I have other account issues as well, like I cannot register VS Express because my account is screwed up.

It is ISP related. It works fine from computers that are connected to the Internet via a different ISP, because they can reach the relevant server. From my ISP, I somehow cannot.

Here's what happens:

C:\Users\sgroot>ping l7oytg.sn2.livefilestore.com

Pinging sn2lfs.storage.msn.com.nsatc.net [207.46.0.171] with 32 bytes of data:
Reply from 202.213.193.233: TTL expired in transit.
Reply from 202.213.193.233: TTL expired in transit.
Reply from 202.213.193.233: TTL expired in transit.
Reply from 202.213.193.233: TTL expired in transit.

Ping statistics for 207.46.0.171:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\sgroot>tracert l7oytg.sn2.livefilestore.com

Tracing route to sn2lfs.storage.msn.com.nsatc.net [207.46.0.171]
over a maximum of 30 hops:

   1     6 ms     3 ms     2 ms  r177.tokynt01.ap.so-net.ne.jp [202.223.119.194]
   2     2 ms     4 ms     2 ms  maru-01Gi2-9.net.so-net.ne.jp [202.223.119.193]
   3    11 ms     3 ms    12 ms  ote-gw5Po1.net.so-net.ne.jp [110.67.171.9]
   4     3 ms     2 ms    13 ms  202.213.193.241
   5     2 ms     2 ms     5 ms  202.213.193.234
   6     6 ms     3 ms    12 ms  202.213.193.233
   7     3 ms     2 ms     2 ms  202.213.193.234
   8     9 ms     3 ms    11 ms  202.213.193.233
   9     3 ms     3 ms     3 ms  202.213.193.234
  10     3 ms    15 ms     3 ms  202.213.193.233
  11     3 ms     3 ms     3 ms  202.213.193.234
  12     3 ms    12 ms    13 ms  202.213.193.233
  13     3 ms     3 ms     3 ms  202.213.193.234
  14     9 ms     3 ms    12 ms  202.213.193.233
  15     3 ms     3 ms     3 ms  202.213.193.234
  16    15 ms     3 ms    10 ms  202.213.193.233
  17     3 ms     3 ms     3 ms  202.213.193.234
  18     6 ms     3 ms     9 ms  202.213.193.233

Remainder omitted because it just repeats.

The server l7oytg.sn2.livefilestore.com seems to be used for all files on my account except Office files. There's seems to be a routing configuration error somewhere that causes a routing loop. The problem only happens when connecting from my ISP.

The problem is, if I want to contact my ISP about it I need to be able to explain this problem in Japanese. Which I can't.

ping l7oytg.sn2.livefilestore.com

Pinging sn2lfs.storage.msn.com.nsatc.net [207.46.0.171] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.0.171:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

That's from the US :/

@evildictaitor: You can't actually ping the servers. They don't respond to ping requests (I've tested this with some servers that I can reach). The fact that you're not getting the TTL expired message means you're not running into the same issue as me.

Just check this link. If you can see the image, it's working for you. For me, the page will load but the image will not.

Oh ok. I can see the image :/

@Sven Groot:I can see the image too.

Btw, I think the network guys there should be able to understand your problem just by the tracert dump and a line of "cannot connect l7oytg.sn2.livefilestore.com, please check".

The problem has resolved itself. Once again, procrastination has saved the day!