Answered by:
All my machine cannot work on Remote Desktop!

Question
-
All my machines cannot connect via remote desktop, I only can see a yellow triangle on my machines. So, how can I provide logs for more analysis?Sunday, February 14, 2010 4:44 PM
Answers
-
See this post on how to submit logs and bug reports - http://social.microsoft.com/Forums/en-US/LiveMesh/thread/d52b350a-f3e0-41c6-8e78-d6378e566b9eJim
Microsoft MVP Consumer Security - Forum Moderator - Live One Care - Live Mesh - Microsoft Security Essentials- Marked as answer by Stephen BootsMVP, Moderator Wednesday, May 5, 2010 12:27 PM
Sunday, February 14, 2010 10:24 PMModerator
All replies
-
See this post on how to submit logs and bug reports - http://social.microsoft.com/Forums/en-US/LiveMesh/thread/d52b350a-f3e0-41c6-8e78-d6378e566b9eJim
Microsoft MVP Consumer Security - Forum Moderator - Live One Care - Live Mesh - Microsoft Security Essentials- Marked as answer by Stephen BootsMVP, Moderator Wednesday, May 5, 2010 12:27 PM
Sunday, February 14, 2010 10:24 PMModerator -
Are all of the machines on a local LAN? Are you seeing this in the Live Desktop or the Live Mesh notifier?
When did you install Live Mesh and has it ever shown the machines as available for connection?
-steve
~ Microsoft MVP Windows Live ~ Windows Live OneCare| Live Mesh|MS Security Essentials Forums Moderator ~Monday, February 15, 2010 2:41 AMModerator -
thank you all..
hi... I have submitted the log.
Also.. when I viewing the logs, I always see
2010-02-15 09:14:50.423,INFO,Moe,100,0,13,Comms: TCP Endpoint Service Client State Machine: Processing event : TimerExpired
2010-02-15 09:14:50.423,INFO,Moe,100,0,13,Comms: TCP Endpoint Service Client State Machine: Transition from WaitLong -> Init
2010-02-15 09:14:50.423,INFO,Moe,100,0,13,Comms: TCP Endpoint Service Client State Machine: Processing event : MaxStopped
2010-02-15 09:14:50.423,INFO,Moe,100,0,13,Comms: TCP Endpoint Service Client State Machine: Transition from Init -> WaitLong
2010-02-15 09:14:50.423,INFO,Moe,100,0,13,Comms: TCP Endpoint Service Client State Machine: Waiting 239 seconds before re-attempt
This error message shown on all my machines (2 boxes).
Steve:
Are all of the machines on a local LAN? No..
Are you seeing this in the Live Desktop or the Live Mesh notifier? I see the message on both.
When did you install Live Mesh and has it ever shown the machines as available for connection? Yes. I have been using that for 1 or 2 months already.Monday, February 15, 2010 9:27 AM -
I have the same problem. I submitted a bug report ID 531740 about 2 weeks ago.
"Are all of the machines on a local LAN?" yes all 3
"Are you seeing this in the Live Desktop or the Live Mesh notifier?" Live desktop: "This device is synchronizing but cannot be remotely accessed."
Notifier: "Live mesh remote desktop is not available"
"When did you install Live Mesh and has it ever shown the machines as available for connection?" Installed more than a year ago and worked flawlessly until about one month ago.
Systems: Win 7 64bit home, Win Vista 32bit home, Win XP 32bit home. Belkin N1 Vision router. All hardware/software is fully updated. MS security essentials installed.
Tried running mstsc from 7 to vista but was unable to establish a connection.
"Remote desktop can't connect to the remote computer for one of these reasons: 1 remote access to the server is not enabled. 2 the remote computer is turned off. 3 the remote computer is not available on the network.
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled"
The vista computer is turned on and I can browse its files over the LAN. I have also selected vista's "allow remote assistance" but do not know if that is different to "remote access" as above.- Edited by HKMike Tuesday, February 16, 2010 5:33 AM further info
Tuesday, February 16, 2010 4:54 AM -
Is it showing offline along with the yellow triangle?
Thats what mine does when it goes into sleep mode.Wednesday, February 17, 2010 1:40 AM