Alright, this was an interesting issue! so thought of sharing with you all. It might come in handy!
I built my private domain controller and forest in Windows Azure IaaS named CORP. I created Affinity groups and a private network which helped with assigning static DNS IP for the DC. I also installed two member servers (VMs in Azure) with Windows 2012 R2 and SQL 2014 image from the Azure gallery. Attached them to the CORP domain and assigned the static DNS IP of the DC to the member server as it’s DNS Entry, though I kept DHCP IP for the member servers to use their own IP’s.
I had this limitation of 20 Procs in my subscription and I was running few Oracle, SQL and Windows VM’s, result I could only create the new SQL 2014 VM’s with minimum processors, and hence had to be satisfied with the bare minimum CPU cores and memory (2 Cores and 3.5 GB RAM).
Lately, I was asked to deliver a session on SQL 2014 In-Memory, MOA, Resource Governor and Cardinality Estimator for which I had no choice other than uplifting the infrastructure for one of the SQL 2014 VM’s (16GB RAM and 8 Cores).
Indeed it was easy to change right. Just go to the VM configuration and change the Virtual Machine size (See Figure 1):
So, I made the changes and the server was rebooted once the infrastructure uplift was done, and after the server came up I couldn’t connect with my domain credentials CORP\useraccount
I kept getting the following error:
[Window Title] Remote Desktop Connection
[Content] The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.
Here is how the error looks like pictorially:
So, what is the solution? You will see numerous posts in the public domain asking for updating your RDP Client etc. and indeed that may apply (please verify if the above conditions are true to apply this solution
For Azure VMs, when you increase the size of the VM (adding CPU and Memory), the network configuration is reset. This means that if you have a static DNS defined inside the VM, it would be set to DHCP assigned which is the public DNS in Azure.
Use local admin account to log on to the virtual machine and set the DNS to point to your DC. Alternatively, assign the IP address of the DC/DNS under DNS servers of virtual network.
Please let me know if you have any questions or concerns around this.