locked
This device is synchronizing but cannot be remotely accessed. RRS feed

  • General discussion

  • On Live Mesh, I am getting the notice that "this device is synchronizing but cannot be remotely accessed."  Actually, it can be accessed via the notifier.  This is on an XP machine, and I gather is a fairly common issue.
    Friday, October 24, 2008 7:47 PM

All replies

  • Hi,

    What operating system is on the computer you're trying to connect from (I'm assuming that the XP machine is the one you're connecting to)?  If I understand correctly, you can connect remotely to that machine using Live Mesh Remote Desktop by initiating the connection with the notifier, but not from the Live Desktop.  Is that right?

    If you're connecting from a computer running Windows Vista, and you have disabled UAC, you've encountered a known issue that should be resolved in our next release.

    If you're connecting from a computer running Windows XP, What browser are you using?  Right now the best experience is with IE 7.  You could also try clearing out your browser cache, and attempting the connection again.

    Please let me know if this helps.

    Ben.
    Friday, October 24, 2008 9:01 PM
  • I believe that I can connect directly from either a Vista or XP computer even though the icon for this computer has the little exclaimation point.  (I'll check this and get back if that's incorrect.)  What I cannot do is connect from the internet-based Live Desktop.  I am able to connect from the Live Desktop to other Vista and XP computers that are similarily configured, some of which are on the same network.  I disabled my McAfee protection, but that didn't help.  Windows Firewall is turned off.  I tried uninstalling and reinstalling the local version of Mesh on that computer.  Didn't help.

    Saturday, October 25, 2008 3:42 PM
  • Forgot to mention that the machine in question is an XP machine
    Saturday, October 25, 2008 3:43 PM
  • Now confirmed, I can connect computer to computer, but not from the online Live Desktop.
    Sunday, October 26, 2008 9:26 PM
  • Hi,

    So, I take it that you've tried connecting to this one computer from multiple other computers (via the Live Desktop in each case), correct?  That is, you've gone to the Live Desktop from, say, computer A, computer B, and computer C, and in all cases you cannot get to computer D (which is running XP) via Live Mesh Remote Desktop from the Live Desktop.  Is that right?

    Are you using the same browser on A, B, & C (and if so, what browser)?  The problem you're describing sounds like it should be a simple fix: delete your browser cache and try again.  But, if you're hitting the same problem on multiple computers, and/or if you're using different browsers, etc. - then it seems that something more is going on.

    If you wouldn't mind, can you please describe in full detail all the situations in which the remote connection to that XP computer are failing, including the OS of the computer you're connecting from in each case, the browser you're using, whether you've tried clearing the browser's cache, tried other browsers, etc.?  The more information you can give me, the easier it will be to narrow in on what additional information we'll need to figure this out.

    Thanks,

    Ben.
    Monday, October 27, 2008 3:42 PM
  • With the new upgrade, things have gotten worse.  (I have submitted a bug report).  Now, although the notifier says I am connected, in reality I am not.  Also (and somewhat strangely, I can connect from this computer to the Live Desktop using Firefox, but not IE.  (IE tries multiple times and gives me the message, "
    The Windows Live Network is unavailable from this site for one of the following reasons:

    • This site may be experiencing a problem
    • The site may not be a member of the Windows Live Network
    Although this is an XP machine, Vista and XP machines on the same network do not have these problems.  I have tried disabling the McAfee security, but it made no difference.


    Friday, October 31, 2008 1:07 AM
  •  Hi,

    I'm sorry to hear that things haven't improved, but thank you for opening a bug.  If you wouldn't mind, could you post the Connect Feedback ID here?  That will make it easier for me to track, and post back here when we determine what the issue is.

    Thanks,

    Ben.
    Friday, October 31, 2008 4:56 PM
  • Hi,

    I have similar but not same problem. I have 3 PC's in my Circle. Let's call them A - Vista x86, B - Vista x64, C - XP x86 and D - Live Desktop. Machine B and C is in this same network. I'm runnig this same browser on A, B & C (it's IE 7). The problem is that I can't connect to machine B from A and C using Live Mesh app and using Live Desktop as well. RPC on B machine running correctly, but Mesh TRC on this machine seems to can't start. This is my log file:

    TRC_Initialize
    2008-11-01 19:19:15.033 PID:0xb70 TID:0xb74 L:0786:CRDPENCRPCServerManager::StartRPCServer - Starting RPC endpoint encrpcpipe[00000b70]
    2008-11-01 19:19:15.033 PID:0xb70 TID:0xb74 L:0685:CRDPENCRPCServerManager::RegisterServer - Registering server RDPWLC_SYSTEM_SESSION_ENDPOINT
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0209:RDPENCHLP_DumpDisplayDevices - Virtual Desktop Bounding Rectange: (0, 0, 1919 1199)
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0214:RDPENCHLP_DumpDisplayDevices - Virtual Desktop Dimensions: 1920 x 1200
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0225:RDPENCHLP_DumpDisplayDevices - Display Device 1:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0226:RDPENCHLP_DumpDisplayDevices - -----------------
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0231:RDPENCHLP_DumpDisplayDevices -

    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0233:RDPENCHLP_DumpDisplayDevices - (*) DeviceName: \\.\DISPLAY1
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0234:RDPENCHLP_DumpDisplayDevices - (*) DeviceString:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0237:RDPENCHLP_DumpDisplayDevices - ATI Radeon HD 3870 X2
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0245:RDPENCHLP_DumpDisplayDevices - (*) Device is currently LOADED.
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0250:RDPENCHLP_DumpDisplayDevices - (*) Flags:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_ATTACHED_TO_DESKTOP
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_PRIMARY_DEVICE
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0280:RDPENCHLP_DumpDisplayDevices - (*) This is the PRIMARY monitor.
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0288:RDPENCHLP_DumpDisplayDevices - (*) Monitor Rectangle: (0, 0, 1919, 1199)
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0293:RDPENCHLP_DumpDisplayDevices - (*) Monitor Dimensions: 1920 x 1200
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0300:RDPENCHLP_DumpDisplayDevices - (*) Working Area: (0, 0, 1919, 1199)
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0225:RDPENCHLP_DumpDisplayDevices - Display Device 2:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0226:RDPENCHLP_DumpDisplayDevices - -----------------
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0231:RDPENCHLP_DumpDisplayDevices -

    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0233:RDPENCHLP_DumpDisplayDevices - (*) DeviceName: \\.\DISPLAY2
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0234:RDPENCHLP_DumpDisplayDevices - (*) DeviceString:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0237:RDPENCHLP_DumpDisplayDevices - ATI Radeon HD 3870 X2
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0250:RDPENCHLP_DumpDisplayDevices - (*) Flags:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_REMOVABLE
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0225:RDPENCHLP_DumpDisplayDevices - Display Device 3:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0226:RDPENCHLP_DumpDisplayDevices - -----------------
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0231:RDPENCHLP_DumpDisplayDevices -

    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0233:RDPENCHLP_DumpDisplayDevices - (*) DeviceName: \\.\DISPLAYV1
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0234:RDPENCHLP_DumpDisplayDevices - (*) DeviceString:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0237:RDPENCHLP_DumpDisplayDevices - Live Mesh Remote Desktop Mirror Driver
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0250:RDPENCHLP_DumpDisplayDevices - (*) Flags:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_MIRRORING_DRIVER
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0225:RDPENCHLP_DumpDisplayDevices - Display Device 4:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0226:RDPENCHLP_DumpDisplayDevices - -----------------
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0231:RDPENCHLP_DumpDisplayDevices -

    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0233:RDPENCHLP_DumpDisplayDevices - (*) DeviceName: \\.\DISPLAYV2
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0234:RDPENCHLP_DumpDisplayDevices - (*) DeviceString:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0237:RDPENCHLP_DumpDisplayDevices - RDPDD Chained DD
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0250:RDPENCHLP_DumpDisplayDevices - (*) Flags:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_MIRRORING_DRIVER
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0225:RDPENCHLP_DumpDisplayDevices - Display Device 5:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0226:RDPENCHLP_DumpDisplayDevices - -----------------
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0231:RDPENCHLP_DumpDisplayDevices -

    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0233:RDPENCHLP_DumpDisplayDevices - (*) DeviceName: \\.\DISPLAYV3
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0234:RDPENCHLP_DumpDisplayDevices - (*) DeviceString:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0237:RDPENCHLP_DumpDisplayDevices - RDP Encoder Mirror Driver
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0250:RDPENCHLP_DumpDisplayDevices - (*) Flags:
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:0260:RDPENCHLP_DumpDisplayDevices - - DISPLAY_DEVICE_MIRRORING_DRIVER
    2008-11-01 19:19:15.049 PID:0xb70 TID:0xb74 L:1149:CRDPBaseCurtain::IsCurtainEnabled - enable key doesn't exist
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xb74 L:0718:CRDPDskExpMgr::GetSPIFlags - Entered GetSPIFlags
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xb74 L:0722:CRDPDskExpMgr::GetSPIFlags - after impersonate in GetSPIFlags (1)
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xb74 L:0756:CRDPDskExpMgr::GetSPIFlags - Wallpaper is ()
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xba4 L:1149:CRDPBaseCurtain::IsCurtainEnabled - enable key doesn't exist
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xba4 L:1877:CRDPENCWin32DesktopProxy::CheckDesktopResChange - Resolution changed
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xba4 L:1218:CRDPENCWin32DesktopProxy::DskProxyThreadProc - Desktop res change detected
    2008-11-01 19:19:15.064 PID:0xb70 TID:0xba4 L:2324:CRDPENCWin32DesktopProxy::OnDisplayChangeEvent - OnDisplayChangeEvent
    2008-11-01 19:19:15.080 PID:0xb70 TID:0xb74 L:1277:CDriverManager::LoadConfiguration - Failed to open registry key SOFTWARE\Microsoft\Live Mesh\Remote Desktop\Configuration
    2008-11-01 19:19:15.080 PID:0xb70 TID:0xba4 L:1149:CRDPBaseCurtain::IsCurtainEnabled - enable key doesn't exist
    2008-11-01 19:19:15.080 PID:0xb70 TID:0xb74 L:1009:CRDPENCScreenMgr::ChangeDesktopSettings - Changing desktop settings to 1920 x 1200 at 24 bpp
    2008-11-01 19:19:15.080 PID:0xb70 TID:0xba4 L:1149:CRDPBaseCurtain::IsCurtainEnabled - enable key doesn't exist
    2008-11-01 19:19:15.080 PID:0xb70 TID:0xba4 L:2359:CRDPENCWin32DesktopProxy::OnDisableCurtain - OnDisableCurtain
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xba4 L:1149:CRDPBaseCurtain::IsCurtainEnabled - enable key doesn't exist
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xba4 L:2359:CRDPENCWin32DesktopProxy::OnDisableCurtain - OnDisableCurtain
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb98 L:0296:CRDPENCRPCServer::RemoteClose - RemotePipeClosed
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb74 L:0711:CRDPENCRPCServerManager::UnregisterServer - Unregistering server RDPWLC_SYSTEM_SESSION_ENDPOINT
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb9c L:1851:CTSThread::internalThreadMsgLoop - Thread: 0xb9c bailing out because of defered quit
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb9c L:1513:CTSThread::ThreadWaitForMultipleObjects - internalThreadWaitForMultipleObjects failed
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xba4 L:1538:CRDPENCWin32DesktopProxy::DriverEscapeInternal - Failed to create the driver DC 21
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb74 L:1198:CDriverManager::SendToDD - Driver escapefailed 0x80070015
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb74 L:1044:CDriverManager::SendWindowTrackingState - SendToDD (TS_RDPENC_FN_WNDTRK) failed! hr[0x83452029]
    2008-11-01 19:19:15.095 PID:0xb70 TID:0xb74 L:0956:CDriverManager::UnloadDriver - Failed to disable the window tracker on uload hr[0x83452029]
    TRC_Terminate

    Hope that was helpful and we get solve.

    Saturday, November 1, 2008 8:08 PM
  • All is working fine now after the update.  Thanks for the feedbacks.
    Monday, November 3, 2008 3:16 PM
  • Hi RobiZX,

    Would you mind opening a bug on this and attaching your full set of Live Mesh logs from each machine (if possible)?  Instructions are in an Announcement at the top of the forums.

    Thanks,

    Ben.
    Monday, November 3, 2008 6:37 PM
  • Hi Ben,

    sorry, my problem has gone after re-install os on machine B so I haven't check subject from a long time :) But if someone will get the same problem as my, the most important thing is set up remote desktop in system properties before you add a machine to Live Mesh Circle.

    BTW everything is working well and I'm fully enjoy with Mesh :)

    Thanks,
    RobiZX
    Tuesday, March 31, 2009 7:15 PM
  • Hi Ben,

    sorry, my problem has gone after re-install os on machine B so I haven't check subject from a long time :) But if someone will get the same problem as my, the most important thing is set up remote desktop in system properties before you add a machine to Live Mesh Circle.

    BTW everything is working well and I'm fully enjoy with Mesh :)

    Thanks,
    RobiZX

    Thanks for the update and glad you are enjoying Live Mesh!
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Wednesday, April 1, 2009 3:58 PM
    Moderator