locked
HostName is blank. Network In and Network Out is 0B - cannot connect to Azure Virtual Machine using Remote Desktop RRS feed

  • Question

  • After a 2 week absence from dabbling with Azure - or rather trying to dabble with SSO, WAP and Mobile Applications - I am having an issue trying to connect to a VM using Remote Desktop Connection.  I powered back on several machines, but, I get the error on one of them when I try to connect.

        "Remote Desktop cannot connect to the remote compute for one of these reasons...."

    Interestingly, the HostName is blank in the Dashboard View.  Network In and Network Out is 0B. So, it looks like a problem with the network of the VM.

    I have tried:

    (1) Restarting the VM
    (2) Changing the size of the VM so that it gets re-provisioned
    (3) Changing the public port for the RDP-connection

    Other virtual machines are OK - except that since the problem machine with no network is my DNS server (my alternate DNS was not setup yet), another machine in that private network cannot connect to the Internet.

    So, I am wondering what else I can try to get the network back for that VM.  If it can't be recovered, can I create a new VM and make that the DNS server?  In the future, perhaps I should leave the DNS machine(s) running - I will have to test by just leaving the machine(s) on for a period and checking out the usage - when I get back to square 1! :-).

    Friday, September 25, 2015 8:15 AM

Answers

  • Hi,

    Unable to RDP could be an issue with the port, firewall or Guest OS issue. mostly hostname missing happens when guest OS is corrupted. you can check if the guest OS is corrupted if the VM is deployed from azure ibiza portal. please try below link if you have deployed V2 VM to check if guest OS is corrupted.
     https://azure.microsoft.com/en-us/blog/boot-diagnostics-for-virtual-machines-v2/
     if you have deployed VM from classic portal. delete the VM by keeping the disk and create new V2 VM to check the Boot Diagnostics or please create a support ticket so that supoort team will update you status of your VM.
    Note 1) please note down the disk name before you delete the VM.
           2) You need to create V2 VM from powershell and select the effected VM disk while creating new VM.


    Appreciate your time and feel free to update your quires if any, Im more glad to help you.

    Regards,
    Mahendranath 

    Friday, September 25, 2015 8:51 AM
  • Hi Julian,

    First, it's not your fault, the VM must run normally even you start it after one year, so this is an interesting issue.

    The steps you made to push the VM to get a network configuration are right, but it's intriguing that the VM did not start normally.

    I will suggest you another step.

    I don't know if you are using the classic deployment or the Resource manager deployment.

    If option1 (Classic deployment). You can create an image from this virtual machine, then deploy this image. So it will be a clone of your virtual machine ant it will normally boot and receive the right configuration

    https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/

    In  you case, do not sysprep your VM, just capture it


    Regards, Samir Farhat || Datacenter Consultant || The way to share my knowledge with the community Visit my blog : buildwindows.wordpress.com

    Friday, September 25, 2015 8:49 AM
  • Hi Julian,

    I have seen you have created a support ticket however I like to share how to create V2 VM from the disk. As of now this can be done through powershell.

    Prerequisites

    • Need to move deleted VM disk from classic storage account to storage account V2

    Powershell templet

    New-AzureResourceGroupDeployment -Name "VMname" -ResourceGroupName "Resoource grop nameINstorageaccountregion" -TemplateUri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/201-vm-from-specialized-vhd/azuredeploy.json"

    This templet will ask for below details.

    location: East US _ example

    osDiskVhdUri: < Give URL of V2 storage account>

    osType: Windows - Example

    vmName: < name>

      https://azure.microsoft.com/en-us/blog/boot-diagnostics-for-virtual-machines-v2/

    Regards,

    Mahendranath  Miryala

    Wednesday, September 30, 2015 1:46 PM
  • Hi,

    I already encountered the same issue, and Microsoft was aware of that.

    Mysteriously, the name has appeared after few days of the operation.

    i installed the last Azure agent on the VM and Stopped/Started the VM.

    Hope this helps.

    https://social.msdn.microsoft.com/Forums/azure/en-US/ad40b207-559b-4731-9d24-11a2b44f239c/the-computername-is-empty-?forum=WAVirtualMachinesforWindows


    Regards, Samir Farhat || Datacenter Consultant || The way to share my knowledge with the community Visit my blog : buildwindows.wordpress.com

    Wednesday, September 30, 2015 2:32 PM
  • Hi Samir,

    Either V1 or V2 VM is ok to user but user want to know why he is not able to RDP. As per customer verbatim hostname missing occurs generally when VM has not booted, there is some issue with Guest OS. As there is only option for V1 VM if VM is working or not is check RDP but V2 Customer can check where exactly the VM hanged.   

    Regards,

    Mahendranath Miryala

    Wednesday, September 30, 2015 3:44 PM

All replies

  • Hi Julian,

    First, it's not your fault, the VM must run normally even you start it after one year, so this is an interesting issue.

    The steps you made to push the VM to get a network configuration are right, but it's intriguing that the VM did not start normally.

    I will suggest you another step.

    I don't know if you are using the classic deployment or the Resource manager deployment.

    If option1 (Classic deployment). You can create an image from this virtual machine, then deploy this image. So it will be a clone of your virtual machine ant it will normally boot and receive the right configuration

    https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/

    In  you case, do not sysprep your VM, just capture it


    Regards, Samir Farhat || Datacenter Consultant || The way to share my knowledge with the community Visit my blog : buildwindows.wordpress.com

    Friday, September 25, 2015 8:49 AM
  • Hi,

    Unable to RDP could be an issue with the port, firewall or Guest OS issue. mostly hostname missing happens when guest OS is corrupted. you can check if the guest OS is corrupted if the VM is deployed from azure ibiza portal. please try below link if you have deployed V2 VM to check if guest OS is corrupted.
     https://azure.microsoft.com/en-us/blog/boot-diagnostics-for-virtual-machines-v2/
     if you have deployed VM from classic portal. delete the VM by keeping the disk and create new V2 VM to check the Boot Diagnostics or please create a support ticket so that supoort team will update you status of your VM.
    Note 1) please note down the disk name before you delete the VM.
           2) You need to create V2 VM from powershell and select the effected VM disk while creating new VM.


    Appreciate your time and feel free to update your quires if any, Im more glad to help you.

    Regards,
    Mahendranath 

    Friday, September 25, 2015 8:51 AM
  • Hi,

    Could you please let me know if the steps provided has helped in resolving your issue. 

    Let us know if you need further assistance.

    Best Regards
    Mahendranath Miryala
    _____________________________________________________________________________________
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful.
    Tuesday, September 29, 2015 12:31 PM
  • Thanks for looking - I was able to create an image and then clone the machine using your link (without the SysPrep).  Unfortunately, the new cloned machine (from the Classic Deployment) also could not connect thru RDP, so, I suspect that there must be something wrong with the image.  it too has an empty HostName.  I am going to try the Boot Diagnostics suggested next.
    Wednesday, September 30, 2015 6:16 AM
  • There is a V2 VM script at:

    https://gist.github.com/nmackenzie/db9a4b7abdee2760dba8

    and more information at

    http://blogs.msdn.com/b/cloud_solution_architect/archive/2015/05/05/creating-azure-vms-with-arm-powershell-cmdlets.aspx

    but I wonder if I should utilize the image that I created from the problematic machine - or just the disk.

    Wednesday, September 30, 2015 7:11 AM
  • Hi Julian,

    I have seen you have created a support ticket however I like to share how to create V2 VM from the disk. As of now this can be done through powershell.

    Prerequisites

    • Need to move deleted VM disk from classic storage account to storage account V2

    Powershell templet

    New-AzureResourceGroupDeployment -Name "VMname" -ResourceGroupName "Resoource grop nameINstorageaccountregion" -TemplateUri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/201-vm-from-specialized-vhd/azuredeploy.json"

    This templet will ask for below details.

    location: East US _ example

    osDiskVhdUri: < Give URL of V2 storage account>

    osType: Windows - Example

    vmName: < name>

      https://azure.microsoft.com/en-us/blog/boot-diagnostics-for-virtual-machines-v2/

    Regards,

    Mahendranath  Miryala

    Wednesday, September 30, 2015 1:46 PM
  • Hi,

    I already encountered the same issue, and Microsoft was aware of that.

    Mysteriously, the name has appeared after few days of the operation.

    i installed the last Azure agent on the VM and Stopped/Started the VM.

    Hope this helps.

    https://social.msdn.microsoft.com/Forums/azure/en-US/ad40b207-559b-4731-9d24-11a2b44f239c/the-computername-is-empty-?forum=WAVirtualMachinesforWindows


    Regards, Samir Farhat || Datacenter Consultant || The way to share my knowledge with the community Visit my blog : buildwindows.wordpress.com

    Wednesday, September 30, 2015 2:32 PM
  • Hi Julian,

    I have seen you have created a support ticket however I like to share how to create V2 VM from the disk. As of now this can be done through powershell.

    Prerequisites

    • Need to move deleted VM disk from classic storage account to storage account V2

    Powershell templet

    New-AzureResourceGroupDeployment -Name "VMname" -ResourceGroupName "Resoource grop nameINstorageaccountregion" -TemplateUri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/201-vm-from-specialized-vhd/azuredeploy.json"

    This templet will ask for below details.

    location: East US _ example

    osDiskVhdUri: < Give URL of V2 storage account>

    osType: Windows - Example

    vmName: < name>

      https://azure.microsoft.com/en-us/blog/boot-diagnostics-for-virtual-machines-v2/

    Regards,

    Mahendranath  Miryala

    It seems  that the user want to create V1 Machine and not ARM machine ? AM i right ?

    Regards, Samir Farhat || Datacenter Consultant || The way to share my knowledge with the community Visit my blog : buildwindows.wordpress.com

    Wednesday, September 30, 2015 2:34 PM
  • Hi Samir,

    Either V1 or V2 VM is ok to user but user want to know why he is not able to RDP. As per customer verbatim hostname missing occurs generally when VM has not booted, there is some issue with Guest OS. As there is only option for V1 VM if VM is working or not is check RDP but V2 Customer can check where exactly the VM hanged.   

    Regards,

    Mahendranath Miryala

    Wednesday, September 30, 2015 3:44 PM