question

jatsmats avatar image
0 Votes"
jatsmats asked jatsmats commented

RDP to Azure VM shows Internal Error

Azure VM (classic), has Windows Server 2012 r2.

I downloaded long time ago a RDP file from Azure portal and I've been able to access the VM until now. No changes on the VM previous to this. I'm used to log in everyday to check everything inside is fine and the prevous day I could access it without a problem. All of a sudden I can't access the VM now, and it shows a simple error message:

 "Internal Error."

I tried redownloading the file and checking username and pwd but they were correct.

After minutes of trying to connect through RDP, I could access it once and tried to troubleshoot it. I've checked if the port is used by another program, resetted the credentials and renewed the certificate through Powershell, and restarted after each try. Then I got this other error like one or two times:

 "This computer can’t connect to the remote computer.
 Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."

And then the simple error came back.

How can I solve this RDP error issue? I circunvented the problem by installing AnyDesk to it the time I could access it but, well, it's not the solution.

azure-virtual-machinesremote-desktop-services
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
We are looking forward to your reply and ready for help.

---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. ---

0 Votes 0 ·
GraceHE-MSFT avatar image
0 Votes"
GraceHE-MSFT answered jatsmats commented

Hi,
Thank you for posting your query. According to your description, the key point to solve the problem is to figure out the erro message "Internal Error".
Here are some suggestions you may have a try.

Remove the check mark in this picture
![79426-image.png][1]

change settings in the Group Policy
![79427-image.png][2]

---If the suggestions above are helpful, please ACCEPT ANSWER. Really appreciate. This will also help others with similar issue to find this post quickly. ---
[1]: /answers/storage/attachments/79426-image.png
[2]: /answers/storage/attachments/79427-image.png


image.png (117.1 KiB)
image.png (255.2 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GraceHE-MSFT

Thank you for answering. Sorry I couldn't respond until today but I'm going to accept your answer. It did enter the VM after all. I'm going to have to tweak some things to make it more secure though.

Thanks a lot!

0 Votes 0 ·
ChristopherW-MSFT avatar image
0 Votes"
ChristopherW-MSFT answered jatsmats commented

Hi @jatsmats

'Internal Error' on a Virtual Machine can be a few things, but the underlying issue is because the RDService can't process your RDP request. Make sure your RDP port is secure and not open, you can change the port to something other than TCP/3389, and make sure the only IPs allowed to it are ones you know. Make sure you restart the machine after making these changes, to allow the RDService to reset all sessions that could be pending and causing issues. If you're unsure if it's secure, please attempt to RDP from a different IP, or attempt to block yours to verify the block rules are working correctly.

Steps for Internal Error: https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-rdp-internal-error

If the VM is still unable to RDP with an "Internal Error", then it could be Certificate or TLS related. These can be updated through the Virtual Machine's Serial Console, or 'Run Command' in the VM's settings.

If these changes can't be made through Serial Console, Run Command, or have not been effective, you may need to Stop the Virtual Machine, Snapshot the OSDisk, and repair the Virtual Machine by mounting it to a Repair Hyper-V VM, or pulling the image to a local machine.

Steps for Repair VM (Nested Virtualization): https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-vm-by-use-nested-virtualization


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @ChristopherW-MSFT

Thank you for your answer. I've seen the first link you sent before, when I mentioned I tried to troubleshoot the VM that's one of the searchs I've landed on.

I tried the steps that could apply to my problem, including Certificate renewal and TLS versions updated, except "Repair the VM Offline" because it seemed too extreme for something that happened so suddenly.

I didn't try changing the port though, do you think that something happened to the port to stop working? I'll have to try it anyways.

0 Votes 0 ·