Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
after update yesterday can't connect remotely -- error: 0000001B, 5 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
     After the Mesh update yesterday I have been unable to remote connect into my home computer (Vista x64 Ultimate) from my work computer (XP Pro).  I am still able to connect from my home computer to my work computer.

    (I've attached my logs to feeback ID 379143)
    Friday, October 31, 2008 8:00 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote
    Hi,

    I can confirm that we started seeing more reports like this with the latest update, though it's actually a permutation of an issue we've see before.  The problem is, while we're aware of the problem (manifesting for some people as a 500 or 401 error - and it seems to have something to do with your computer's ability to get a device identification from Windows Live ID) we do not yet know the exact cause of the error.  That's why the response you received didn't contain much information.  Essentially, we're aware of people having the issue that your logs show your computer is encountering, but we don't yet know exactly why that's happening, nor how to resolve, or even workaround, it.  We'll definitely let everyone know when we have more information.

    Thanks,

    Ben.
    Monday, November 3, 2008 4:45 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you for submitting a bug, and thank you very much for posting the Connect Feedback ID here.  I see the bug internally, and we'll update you as soon as we learn anything.

    Ben.
    Friday, October 31, 2008 9:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I got a comment on my ticket saying this is a known issue.  Can you be more specific on what the issue is?  Also, can you confirm that the known issue started after the update on Thursday?  Thanks.

    • Edited by joshbish Saturday, November 1, 2008 1:13 AM
    Saturday, November 1, 2008 1:13 AM
  • Question
    Sign in to vote
    2
    Sign in to vote
    Hi,

    I can confirm that we started seeing more reports like this with the latest update, though it's actually a permutation of an issue we've see before.  The problem is, while we're aware of the problem (manifesting for some people as a 500 or 401 error - and it seems to have something to do with your computer's ability to get a device identification from Windows Live ID) we do not yet know the exact cause of the error.  That's why the response you received didn't contain much information.  Essentially, we're aware of people having the issue that your logs show your computer is encountering, but we don't yet know exactly why that's happening, nor how to resolve, or even workaround, it.  We'll definitely let everyone know when we have more information.

    Thanks,

    Ben.
    Monday, November 3, 2008 4:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    THis happened to me today, first time, Vista SP1 to Vista SP2 x64. Only have logs from the Sp1 machine.
    Saturday, February 14, 2009 3:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    First time seeing this as well on a system that's been fine since installed. This is actually the first time I've seen this as a problem on any of my devices and the only thing that did change is I set it to auto startup and login which it wasn't before today.

    Win7 x64, Device shows as online and attempts to connect then errors. System is on my local LAN and accessing it from within the LAN.
    Saturday, February 14, 2009 4:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Now getting 80004005, 0 error
    Saturday, February 14, 2009 4:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yup.  Seemed to happen after the Windows Live updates are applied.   Probably Live Sync breaking LiveMesh....

    Sigh.
    Saturday, February 14, 2009 4:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
     Getting same error starting tonight - can't connect to two seperate machines (XP pro SP2) from Vista Home Premium SP1.  Getting same error if connecting from browser.
    Saturday, February 14, 2009 4:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Error Code: 0000001B, 5
    Just started happening to me tonight and I have been using mesh remote desktop for months with no problems.  What could it be?

    Saturday, February 14, 2009 4:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same here, as posted above 0000001B, 5. Please please fix this soon. Didn't realize how often i used it till it was gone.
    Saturday, February 14, 2009 6:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
     YMMV, but this morning it is working on all machines again...without any reboots.
    Saturday, February 14, 2009 1:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I'd suggest that everyone encountering this collect their logs and lodge a bug on Microsoft Connect (instructions here). Firstly though, check through the list of existing (or new) bugs, and if there is already a similar one then just add your validation / comments to that one.

    A quick check through the bugs for remote desktop (there are quite a few) on Connect don't yield any bugs for these new sets of problems.

    Oren
    Saturday, February 14, 2009 3:42 PM