I am using a Cloud services running a single worker role with two instances. For almost a year I have been able to connect using RDP.
This week I wanted to connect, but couldn't. The remote desktop connection display the wrong credentials displaying: "Use the following credentials to connect: Password for Admin"
When an deployment is uploaded to the staging environment, I am able to connect. After swapping to the production environment, I cann't connect.
But the old deployment can be connected in the staging environment.
When I set up the connection from another PC, I am able to connect.
I think there is something going on with my PC, but no idea where to look.
Can somebody help me?
It turned out I have checked "Save my credentials" by accident. There was an entry in the Windows Credential Manager.
Deleted the entry, I can connect again.
After creating the RDP account, I had to reimage the webrole (Roles And Instances -> WebRole -> Reimage). After the reimage I was able to connect.
Related
we have the virtual machine:
account: xxxxxxxxx#xxxxxxx.xxx,
account type: Personal account,
subscription: Microsoft Partner Network,
resource group: xxxxxxxxxxx,
virtual machine: xxxxxxxxxxx,
public ip address: xx.xxx.xx.xx:xxxx and
OS: Windows Server 2012 R2 Datacenter.
I downloaded the xxxxxxxxxxx.rdp from Azure portal.
If I clicked on the RDP I had got error:
Remote Desktop Connection: An internal error has occurred.
Do you know cause?
Thank you very much.
I managed to fix my issue with these 3 steps. To do so, you need to be able to connect to your machine with RDP. I can do that, if I am connecting while it is starting up, then my RDP somehow works.
The permanent fix for me was these steps.
1: remove the checkmark
2: change group policy setting
3: delete machine keys
One option is to use an alternative RDP client, such as the Microsoft Remote Desktop Windows Store app or even FreeRDP.
Edit to add: RDP access had been misconfigured leaving open access to the public internet and there were multiple dead connections leftover from brute force attempts to login. Cleaning up the firewall to restrict access meant no more invalid login attempts and the problem seems to have gone away without any VM configuration changes.
The internal error may be caused by several reasons and you can follow the steps here to troubleshoot and solve it. Take care, backup the VM OS disk is an important action and should be done before doing other actions.
I have an Azure Virtual Machine connected with Azure Active Directory. A user from this AD is added to this machine as an admin. Other people can successfully RDP to the machine with this user's credential, but I get error saying "The user account used to connect to remote PC did not work. Try again". Well, I am trying the whole day. Does anyone know what can cause this?
The fun fact is, I can RDP to the machine using the local admin, but again it fails with AD user.
I tried connecting with Microsoft Remote Desktop for Mac, mstsc for Windows and with Remote Desktop Connection Manager. The same result everywhere.
I tried different usernames format:
alex.sikilinda#mydomain.com - other people can successfully login using this format
AzureAD\alex.sikilinda#mydomain.com - for windows client getting the same error, for Microsoft Remote Desktop for Mac getting "Your session ended because of an error. If this keeps happening, contact your network administrator for assistance. Error code: 0x807"
AzureAD\AlexSikilinda mstsc error - "Remote machine is AAD joined. If you are signing in to your work account, try using work email instead", Mac - "Your session ended because of an error. If this keeps happening, contact your network administrator for assistance. Error code: 0x807"
Microsoft Remote Desktop for Mac version 10.2.3 (1343)
Windows 10 version 16299 (also tried with 1803 on another machine, the same result).
I also came across the same error for the win10 that is AAD join, and I tried the following way to solve this:
Change VM Remote desktop settings same as the picture
Create a new RDP config file
Open mstsc.exe, click on Show Options and then click Save As(give it a new name such as AzureAD_RDP, save it somewhere easy to find).
Open the saved file using Notepad. Verify that the following two lines are present, if not, add them, and save.
enablecredsspsupport:i:0
authentication level:i:2
RDP to the target VM
Open the RDP config file that you just edited, enter the IP address of the VM, do not enter any username, and then connect.
Here you could use AzureAD\UPN or username to log in.
I haven't tried disabling the NLA (and wouldn't recommend), however in my case was the legacy MFA getting in the way of getting into the VM, even if only enabled for the account, and not forced.
In my case, we're using the Conditional Access with MFA, but we have to exclude the VM from the cloud apps (Azure Windows VM Sign-In), because we're not using Windows Hello (thanks Microsoft for a half baked solution!).
See Login to Windows virtual machine in Azure using Azure Active Directory authentication for more details.
I have created a test lab in Azure utilizing the guides below:
https://www.microsoft.com/en-us/download/details.aspx?id=41684
and
http://social.technet.microsoft.com/wiki/contents/articles/24277.test-lab-guide-install-exchange-server-2013-on-the-windows-2012-r2-base-configuration.aspx#Step_4_Install_and_configure_EX1
I have a server named EX1 that's running Exchange. Last night I was able to connect to it just fine but this morning I am unable to connect to it via the Azure portal. Here is the error that I get:
The machine is Running as shown under status. I've tried resetting the remote desktop connection which didn't work. I switched the endpoints for Remote Desktop to 3389 for the public port but still can't get in. Any suggestions?
Have you tried deleting the endpoints and re-creating them?
Help! When I try to creat a web site on Azure, I receive the following error message:
There was no endpoint listening at https://geomaster.azurewebsites.windows.net/subscriptions/2762018c-1ace-4b11-a55d-7b69d004cca3/webspaces/eastuswebspace/sites that could accept the message.
I was able to create 2 sites about 3 months ago without any problem. My subscription is an active pay as you go account. I'm not trying to do anything advanced, just a web site connected to a SQL DB. The SQL DB creates without a problem. I was also able to create a virtual Win2008 machine. Azure reps have said my account is fine. I don't know where else to look. Thanks
-ph
If your development machine is behind a proxy server, the problem could be caused by the machine's proxy server settings. Have a look at them via Control Panel / Network and Internet / Internet Options / Connections tab / Lan Settings and try checking the box for 'Automatically detect settings' if it isn't.
Solved: Azure Problem - There was no endpoint listening at that could accept the message
Windows Azure Package Deployment Failed with Error - "There was no endpoint listening"
Same for me. Seems they simply do not have enough recourses atm.
refs:
http://social.technet.microsoft.com/Forums/windowsazure/en-US/611545bc-a061-4107-9240-597b60131b8b/error-creating-azure-website
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/389cba4f-8943-4f56-8b0e-9f9066154337/error-creating-azure-website
On a project I’m working on at my current job, we need to enable the RDP on azure web role. I've enabled the RDP but client is not being able to connect. We confirmed RDP port is opened as well.
Doesn't client needs to install certificate on his/her machine as well?
No the client doesn't need to install a certificate on their machine. When you deploy a cloud service from Azure you can opt to have an RDP account created at the point of deployment, this will automatically configure the endpoints for 3389 on the instance. Are you sure the client is using the correct case on the password and has their firewall open on 3389?
No it does not. If you're having problems try to download the assistant file that will set up everything BUT your firewall, leaving you to just hit "Connect"