none
Cannot RDP into VM Role RRS feed

  • Question

  • Hello, I cannot connect RDP to my VM-Role. I read many of the articles already posted but I don't think it applies to my case. I can't even ping my vm role, however the portal screens say the vm is running and that the rdp endpoint is available (see below).

        Name    Protocol    Public Port    Private Port    Load Balanced
        RemoteDesktop    tcp    52562    3389    NO

    When I launch the rdp file, I get the following error:

    Remote Desktop can't connect to the remote computer for one of these reasons:

    1) Remove access to the server is not enabled

    2) The remote computer is turned off

    3) The remote computer is not available on the network

    Help?

    Friday, July 13, 2012 12:08 AM

Answers

All replies

  • I am experiencing the same problem. Below is my tracert log.

    Produced by the following command: tracert -w 5000 -4 -h 30 tentacle-att-primary.cloudapp.net

    Tracing route to tentacle-att-primary.cloudapp.net [157.56.166.235]
    over a maximum of 30 hops:

      1     1 ms     1 ms     2 ms  192.168.1.1 
      2    11 ms    11 ms     9 ms  192.168.1.1 
      3     8 ms    10 ms    21 ms  COX-68-12-10-48-static.coxinet.net [68.12.10.48] 
      4    12 ms    14 ms    11 ms  COX-68-12-8-178-static.coxinet.net [68.12.8.178] 
      5    28 ms    27 ms    30 ms  68.1.5.140 
      6    16 ms    14 ms    16 ms  68.105.30.38 
      7    17 ms    15 ms    16 ms  204.152.140.23 
      8    18 ms    17 ms    16 ms  ge-6-1-0-0.dal-64cb-1a.ntwk.msn.net [207.46.47.118] 
      9    57 ms    57 ms    61 ms  xe-1-0-1-0.bay-16c-1b.ntwk.msn.net [207.46.40.30] 
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.
     27     *        *        *     Request timed out.
     28     *        *        *     Request timed out.
     29     *        *        *     Request timed out.
     30     *        *        *     Request timed out.

    Trace complete.


    Friday, July 13, 2012 3:26 AM
  • I have just dropped the vm and recreated it with a larger instance (from extra-small to small) and still no luck. MS please help out!
    Friday, July 13, 2012 7:46 PM
  • Hey Sig1 and DavidR63,

    Can you guys confirm that you WERE able to connect to the VM originally using RDP and then suddenly the ability to connect stopped? If so, especially given you tried to change the size and it still didn't work, we would really like to take a closer look at your VMs. Please send your subscription ID, deployment ID of the VM, the name of the VM, and a link to this thread(http://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforWindows/thread/bf45c0d5-5735-4888-87c3-94b8bd199e47) to IaaSForum@microsoft.com.

    Corey

    Saturday, July 14, 2012 12:19 AM
    Moderator
  • That e-mail address bounces.
    Monday, April 14, 2014 9:13 PM
  • I am experiencing similar RDP connection issues, and the resize hack (change to another VM size, then back to the original size) did not work for me.

    I also tried using PsPing from the SysInternals Suite to do a TCP ping to the assigned RDP port (port 52271 for this VM), but those PsPings to [ip]:52271 fail with the message "This operation returned because the timeout period expired."

    This is a newly-created VM, and I have yet to be able to successfully RDP to it.

    Suggestions?

    • Edited by mesheets Tuesday, May 6, 2014 2:41 PM
    Tuesday, May 6, 2014 2:39 PM
  • I am experiencing similar RDP connection issues, and the resize hack (change to another VM size, then back to the original size) did not work for me.

    I also tried using PsPing from the SysInternals Suite to do a TCP ping to the assigned RDP port (port 52271 for this VM), but those PsPings to [ip]:52271 fail with the message "This operation returned because the timeout period expired."

    This is a newly-created VM, and I have yet to be able to successfully RDP to it.

    Suggestions?


    I had a similar issue which I reported in this thread. I tried everything and could not get back into the VM. Fortunately I had not started installing or configuring the VM; it was still a vanilla image. From here forward, for machines that I cannot simply delete and start over, I've decided to use another provider that offers VMWare Hosting, so that I can console into the machine should I randomly loose connectivity. I won't divulge that provider's name here, but if you're interested, feel free to email me:  MSDN [at} Andrew.TechAdvantage.co
    Tuesday, May 6, 2014 2:53 PM