Unable to connect by RDP after change the HOSTNAME

Question

_{Wednesday, November 7, 2012 8:12 AM}

Hi all! I hope someone can help me with this problem:

I have successfully attached and started my own Win 2008 VM Image (copy the VHD file to Windows Azure and so on). It was possible to connect via RDP and all was working fine.

To prepare this running System to integrate it into the "On-Premise" network i changed the hostname... after doing that i can't connect anymore to this VM.

• I've restartet this VM two times without any change
• I've deleted and recreated the RDP endpoint... no luck
• The management portal is showing the NEW host name and the status of the VM is up and running...

Any idea?! Thanks!

Andreas

All replies (11)

_{Thursday, November 8, 2012 9:23 PM ✅Answered}

Andreas,

Changing the hostname should have allowed the RDP functionality to continue to the new name. Have you deleted the Remote Desktop Connection endpoint and then see if you can remote in? In addition, can you RDP in via the IP address?

Thanks!

Patrick [MSFT]

_{Friday, December 14, 2012 7:10 PM ✅Answered}

I tested a host rename as did others and we found the operation to be successful. It is worth noting that a reboot is required for a host name change to take effect. It is likely that in this case there were other changes pending a reboot that caused the problem.

Users should feel confident in changing a host name if necessary. To be sure there are no other changes pending, reboot before changing the name, then change the name, and finally reboot again so that the name change will take effect.

-Steve

Please let us know if this information was useful to you.

_{Wednesday, November 7, 2012 9:22 PM}

Andreas,

Did you create a new endpoint to point to the revised network name?

Thanks!

Patrick [MSFT]

_{Thursday, November 8, 2012 10:54 AM}

Patrick,

i can't see any information to set a network name by adding an endpoint from the management portal?!

Maybe the firewall on the guest system is now blocking the rdp communincation?

Regards,

Andreas

_{Friday, November 9, 2012 5:27 AM}

Patrick,

I've deleted the endpoint and tried a connection -> it did not help

After that, i re-created a new endpoint on default rdp port 3389 (public and private) and tried a connection -> it did not help

I'am also already changed the VM Size from medium to small -> it did not help

No RDP connection is currenty working neither via hostname as well as via ip adress. At this time i can't working with my Virtual Maschine.

Thanks for your help!

Andreas

_{Friday, November 9, 2012 11:19 AM}

Patrick,

i've deleted my VM and create a new one (based on the same VHD Files). I've a new Virtual Public IP and a new DNS name.

The RDP connection is still not working. Any idea?

Thanks

Andreas

_{Monday, November 12, 2012 4:24 PM}

I'am working now since Wednesday, November 07 on this problem and it still exists. Is there another Microsoft support option i can use? (not a forum)

Oh yes i can delete my VM and create a new one to fix it ...maybe. But this is not an option for me. Cause i'am evaluating Windows Azure to check is it right for my customer... is it mhhhhh?!

Any idea? How can i connect to my VM if the network not working correctly... the Hyper V Manager on Windows Server 2008 can still connect if this happen, i think.

Thanks for your time!

Andreas

_{Tuesday, November 13, 2012 9:48 PM}

Andreas,

Send me the following:

Please send me an email to [email protected] along with the following information:

1. The title of this post in the subject line

2. Your first and last name and Live ID

3. A link to this forum post

4. Your subscription ID

5. The VM's info:

i) VM name

ii) VM DEPLOYMENT ID

iii) OS version of the VM

iv) Time Zone of the VM

I appreciate your patience with this one.

Thanks!

Patrick [MSFT]

_{Monday, November 19, 2012 11:33 AM}

Patrick, any news?

I still can't use my VM and unfortunately the costs are running...

Is it possible to open an official ticket for this bug?

Andreas 

_{Monday, November 26, 2012 8:41 PM}

Andreas,

I apologize for the delay. I was out of the office for a good part of the holiday. Let me check on this.

Thanks!

Patrick [MSFT]

_{Wednesday, January 23, 2013 9:14 AM}

Hello all, after some tests i found the reason why i can't connect to my VM after deploying into the cloud. I will describe it here just for your info:

It happend also on my Hyper-V Root Server, so it is not a general problem in the Windows Azure Cloud. But, if it happend on a "normal" Hyper-V Server i'am still able to connect with the Hyper-V Management Console on the root server. Any external RDP connection are not possible. Rename the Host was not the reason like Steve also says...

What must happend:

• The VM is in a Domain!
• Remove the VM from this Domain and create a Workgroup for testing
• After doing this, Windows disable the option to connect via RDP
• Connections over the Hyper-V Management Console are still possible

So what is todo to prevent this in the Windows Azure Cloud:

• Remove the VM from your Domain
• Connect via Hyper-V Manager an enable RDP again
• deploy to Windows Azure Cloud
• have fun ;-) 

Regards,

Andreas