I created two VMs in a virtual network. One of them has AD and the other is just a member server. During the course of setting up these VMs, I restarted them few times and was able to RDP.
I then installed Exchange 2013 binaries on the member server and shutdown both VMs last night and started them this morning. I can RDP to the domain controller, but not to the member server. (I know Exch 2013 is not supported on Azure, but I just want to play with it. There are several people who has done this successfully. So I don't think this is related to Exch 2013. This is purely a bug in Azure IaaS)
On the quick glance, "HOST NAME" is empty. It is showing just a hyphen.
STATUS: Running
DNS NAME: xxxxxx.cloudapp.net
HOST NAME: -
PUBLIC VIRTUAL IP (VIP) ADDRESS: xxx.xx.xxx.xxx
INTERNAL IP ADDRESS: 102.20.11.4
So far, I have tried the following and I am losing my trust in Azure rapidly.
- I have no restrictions on my network since I can RDP to several other Azure VMs
- Both the VMs are based on OOTB gallery image - 'a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-Datacenter-201311.01-en.us-127GB.vhd'
- I have restarted the problematic VM several times
- I changed the RDP endpoint public port and also re-created it.
- I resized the problematic VM few times (medium to small, then to medium, then to large). nothing helped
- I deleted and recreated the VM using the existing vhds
- RDP file does not have cached credentials
- I cannot ping/RDP the member server from the domain controller. Tracert, PSPing also times out.
I have spent a day configuring my test lab, but spent another day just trying to troubleshoot rdp. Please help!