Answered by:
Live Mesh Remote Desktop doesn't use P2P?

Question
-
Hi,
I'm surprised at how unresponsive at times the remote desktop connection is to my machine in the next room. A tracert reveals that the connection goes via Microsoft, making 30 hops along the way, even though I can directly ping and term-serv (RDP/RDC) directly into that machine. Does Live Mesh Remote Desktop not use direct connections or P2P where possible?
Steven
C:\>tasklist | grep WLCMSTSC
WLCMSTSC.exe 4620 Console 1 45,480 K
C:\>netstat -ano | grep 4620
TCP 192.168.1.101:53091 207.46.132.221:443 ESTABLISHED 4620
C:\>tracert 207.46.132.221
Tracing route to 207.46.132.221 over a maximum of 30 hops
1 3 ms 10 ms 3 ms 192.168.1.1
Note: I'm trying to connect to my nearby computer by using the Live Mesh trayicon, selecting "Connect to device" for the relevant machine. My local IP address is 192.168.1.101, the "remote" machine's IP is 192.168.1.104, and we're all behind a switch/firewall with IP 192.168.1.1.
2 * * * Request timed out.
3 12 ms 8 ms 11 ms ge-3-3-ur01.bellevue.wa.seattle.comcast.net [68.86.177.173]
4 13 ms 9 ms 9 ms te-9-3-ur02.bellevue.wa.seattle.comcast.net [68.86.96.70]
5 11 ms 10 ms 10 ms te-8-3-ar02.seattle.wa.seattle.comcast.net [68.86.96.73]
6 * 12 ms 11 ms te-9-1-ar02.seattle.wa.seattle.comcast.net [68.86.90.210]
7 13 ms * 22 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.110]
8 17 ms 24 ms 12 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
9 13 ms 13 ms 18 ms MICROSOFT-C.car1.Seattle1.Level3.net [4.53.144.22]
10 16 ms 22 ms 16 ms ge-5-2-0-54.tuk-64cb-1a.ntwk.msn.net [207.46.45.69]
11 16 ms 13 ms 17 ms ge-7-0-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.41.78]
12 13 ms 15 ms 14 ms ge-0-1-0-0.cpk-64c-1b.ntwk.msn.net [207.46.35.10]
13 205 ms 203 ms 191 ms ten3-4.cpk-76c-1a.ntwk.msn.net [207.46.34.38]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.Wednesday, September 17, 2008 4:32 PM
Answers
-
Hi,
Actually, Live Mesh will currently attempt to establish a P2P connection for Live Mesh Remote Desktop sessions, if that's an option. That little tid-bit seems to have escaped our announcements - I apologize for leaving this thread hanging.
Ben.- Marked as answer by Ben [Live Mesh] Thursday, January 22, 2009 9:09 PM
Thursday, January 22, 2009 9:09 PM
All replies
-
Hi Steven,
Improving the performance of Live Mesh Remote Desktop is something we've been working very hard on (and is one of the most requested updates from customers). The bad news is that, right now, a Live Mesh Remote Desktop session always goes through the cloud, as you've seen. The good news is that we will be releasing an update in the near future that will enable remote sessions to use the P2P connection.
So, all we can do now is ask for your patience, and assure you that it will get better. :)
Thanks,
Ben.- Marked as answer by Ben [Live Mesh] Wednesday, September 17, 2008 6:03 PM
- Unmarked as answer by Ben [Live Mesh] Thursday, January 22, 2009 9:09 PM
Wednesday, September 17, 2008 6:03 PM -
Great, thanks Ben. I look forward to the update.Wednesday, September 17, 2008 7:24 PM
-
5 months have passed...
Is there any status update?Thursday, January 22, 2009 11:27 AM -
nothing has been publicly released yet... hopefully you (we) won't have to wait too much longer!Thursday, January 22, 2009 12:52 PM
-
Hi,
Actually, Live Mesh will currently attempt to establish a P2P connection for Live Mesh Remote Desktop sessions, if that's an option. That little tid-bit seems to have escaped our announcements - I apologize for leaving this thread hanging.
Ben.- Marked as answer by Ben [Live Mesh] Thursday, January 22, 2009 9:09 PM
Thursday, January 22, 2009 9:09 PM