Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Connect to remote desktop error 00000000, 0 RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I'm trying to connect to a vista computer from a vista computer. I get this error: 00000000, 0 Any ideas?
    Monday, November 24, 2008 3:44 PM

All replies

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

    Could you provide additional details please?  Are you logged into an admin account on the local computer?  Are you opening the Live Mesh Remote Desktop session through the Live Mesh notifier, or from the Live Desktop?  How far, if at all, does the connection get before you see the error?  Does the error say anything else?  The more information you can provide, the more likely we'll be able to narrow down the problem and hopefully help you resolve it.

    Thanks,

    Ben.
    Monday, November 24, 2008 6:11 PM
  • Discussion
    Sign in to vote
    1
    Sign in to vote
    I'm logged in as an admin in both computers. I've tried opening the remote desktop session through both Live Desktop and through the local client. The error occurs about 5-10 seconds after I initiate the connection. This is exactly what the error says:

    Cannot connected to "pc"

    To try connecting again, click Retry.
    Error code: 00000000, 0

    Remote computer is running Vista Home Premium x86 SP1. The computer that is initiating the connection is Vista Ultimate x64 SP1.
    Monday, November 24, 2008 6:19 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thanks for the additional information.  That error code isn't very informative, is it?  The next step, then, is to take a look at the Live Mesh logs from both computers.  If you can, please collect both sets of logs (though you can start with one set, from whichever computer you're currently at) and send them to lmprev@microsoft.com, including a description of the problem, your forum handle, at the title of this forum thread (or a link to this thread).  Instructions for collecting logs are in an Announcement at the top of the forums.  Someone should be able to start helping you as soon as we receive your email.

    Please let me know if you have any questions.  And if our support personnel are able to help you resolve the problem, please feel free to update this forum thread.

    Thanks,

    Ben.
    Monday, November 24, 2008 6:26 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I received the same error (00000000, 0) when trying to connect my home Vista computer from work. I have a Belkin wireless router in my home network with built-in firewall enabled. Do I need to allow any ports through in the router? What are the ports? I used the mesh Remote Desktop inside my home network to get access from one computer to another (Vista to Vista, XP to Vista) without a problem.

    I don't have the Mesh software installed on my work XP, so I don't know were to find logs there.

    Thanks,

    Sergey.
    Monday, December 29, 2008 12:10 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    serrzh said:

    I received the same error (00000000, 0) when trying to connect my home Vista computer from work. I have a Belkin wireless router in my home network with built-in firewall enabled. Do I need to allow any ports through in the router? What are the ports? I used the mesh Remote Desktop inside my home network to get access from one computer to another (Vista to Vista, XP to Vista) without a problem.

    I don't have the Mesh software installed on my work XP, so I don't know were to find logs there.

    Thanks,

    Sergey.



    Hi Sergey,

    If I understand correctly, since you do not have Live Mesh installed on your work computer, you are trying to open a remote session into your home computer through the Live Desktop.  Is that correct?  To answer one of your questions, you do not need to open any special ports to allow Live Mesh Remote Desktop to work.  But since you are unable to connect, please do file a bug for us.  You can attach the logs from your home computer to that bug, but it would also be quite helpful if you provided the steps you followed in detail (e.g., what browser you were using at work, whether your work computer is behind a proxy of any kind, etc.).  Instructions for submitting a bug are in an Announcement at the top of the forums.

    Thanks,

    Ben.
    Monday, January 5, 2009 9:39 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I have the same error. Live Mesh is on my Home Server, i can connect to this server using Live Mesh from most networks. When i'm on the the main Office network that has very strict policies i can't connect resulting in this error. Something must be blocked, I thought everything flows trough https??
    Thursday, January 15, 2009 8:29 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Allards said:

    I have the same error. Live Mesh is on my Home Server, i can connect to this server using Live Mesh from most networks. When i'm on the the main Office network that has very strict policies i can't connect resulting in this error. Something must be blocked, I thought everything flows trough https??



    Is your Office network using an authenticated proxy?
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator
    Thursday, January 15, 2009 5:09 PM
    Moderator
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    It's not explicit authentication no popups, so i guess no authenticated proxy, but i have an proxy in IE and no Firewall client on my laptop.

    I'm a contractor there and i have no idea how the backoffice setup exactly is, it's too big. I did change the proxy for one that lets me read Hotmail / Gmail i will change it back to the original .pac file tomorrow to see what happeneds.


    Thursday, January 15, 2009 6:38 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I changed proxy and now it's fine, it must be some kind of proxy restriction.

    I don't understand how something inside a https strieam can be prevented from working? Other https are working fine!
    Friday, January 16, 2009 1:22 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    The IE proxy on my work XP is set up as Automatic proxy script. If I try to download the URL, I get a huge script with a lot of proxies which may correspond to different locations in the corporate network. I couldn't pick up whether the proxy required authentication but we use WebSSO throughout the network which keeps me away from entering any credentials most of the time. I think I'm restricted about publishing the script which means I can't fill enough info to submit a bug. We use some other proxy, too, beside the script to access some outer resources like partners' SVN, and I'm going to give it a try. But that doesn't make much sense anyways because I can't keep it forever in the browser.
    Tuesday, January 20, 2009 9:10 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I'm having the same problem, with both computers being on my local LAN.  Any ideas where I can start looking for the problem?  Cheers
    Friday, April 3, 2009 9:17 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I've been having this problem since Friday, and am still having it now. Nothing has changed on my system (the proxies, the connections, even the ip addresses). I can still connect successfully to one of the computers in my mesh though
    Sunday, April 5, 2009 4:32 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    There were some reports late last week of people encountering this problem. It seemed to clear after a few hours, though.
    If it doesn't clear for you, please do file a bug on Connect.
     

    How to Submit Bugs and Live Mesh Logs

    -steve

    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Sunday, April 5, 2009 5:08 PM
    Moderator