locked
Live Mesh Connect versus Remote Desktop RRS feed

  • Question

  • I've noticed that when I use connect with Live Mesh the performance is pretty poor. It has to black out the backround on the host machine and use window outlines when moving windows.

    In contrast, if I connect to the same machine using Remote Desktop (over a Hamachi VPN) the performance is much better. I can keep the wallpaper enabled and display windows while dragging and everything is still much smoother than Mesh.

    Why is there such a performance discrepancy? I was under the impression they use the same underlying technology.

    Also, I've noticed with the newest version of Mesh, it effectively disables the secondary monitor on the host computer. Is this the expected behaviour? It would be nice of Mesh to restore icon and gadget positions after disconnecting...

    It would also be nice if Mesh is going to be altering the hosts display confiuration anyway, if it would match the client's resolution so you can at least go fullscreen without havin to scroll or resize. Plus keeping the aspect ratio correct would be very nice...

    Thanks.


    Saturday, November 15, 2008 3:21 AM

Answers

  • Hi T Magritte,

    You mention a number of ideas in your post for ways to improve Live Mesh Remote Desktop.  We are, of course, still working to increase speed, functionality, etc. - please feel free to add your requests to our Suggestions sticky.  We've made numerous improvements to Live Mesh as a direct result of customer feedback in the past, and will continue to do so in the future, so your suggestions do make a difference!

    Thanks,

    Ben.
    Monday, November 17, 2008 3:54 PM
  • Hi,

    Live Mesh Remote Desktop will always initiate with a relayed connection, though it will try to establish a direct P2P connection whenever possible.  If a P2P connection cannot be established, however, the remote session traffic will all be relayed.

    Ben.
    Friday, November 21, 2008 7:21 PM

All replies

  • From what I understand the main reason that mesh RDP would be any slower than the normal, direct method, is in the case of a firewall between two machines. When firewalled the connection becomes proxied slowing things down considerably. I've tried this at work and seen significant differences between connecting to a firewalled and a non-firewalled machine.

    Alternatively it would be great if we could change the live mesh RDP port (listening) so as to avoid blockages of ports etc (just like RDP can be conifgured to listen on a different port).
    Saturday, November 15, 2008 1:56 PM
  • Hi T Magritte,

    You mention a number of ideas in your post for ways to improve Live Mesh Remote Desktop.  We are, of course, still working to increase speed, functionality, etc. - please feel free to add your requests to our Suggestions sticky.  We've made numerous improvements to Live Mesh as a direct result of customer feedback in the past, and will continue to do so in the future, so your suggestions do make a difference!

    Thanks,

    Ben.
    Monday, November 17, 2008 3:54 PM
  • Hi Ben,

    Can you comment on whether what nachmore says is correct? I was under the impression that the mesh server mediates a direct peer to peer connection rather than proxy all traffic. Is that not the case?

    Thanks.
    Wednesday, November 19, 2008 1:10 AM
  • Hi,

    Live Mesh Remote Desktop will always initiate with a relayed connection, though it will try to establish a direct P2P connection whenever possible.  If a P2P connection cannot be established, however, the remote session traffic will all be relayed.

    Ben.
    Friday, November 21, 2008 7:21 PM