I have an Azure Cloud Service (classic) that I am trying to enable RDP access on. Enabling it requires having a username, password, and a preexisting encryption certificate. I supply all of the information for those fields, but receive an error "Failed to save Remote Desktop settings" with the following error: "Failed to update extensions for following rules DemoWorkerRole. ajaxExtended call failed". How do I resolve this error?
I'm assuming there is something wrong with my certificate - it's CN is the same as the cloud service's Site URL without the http:// prefix and the / suffix.
It was an incorrect RDP configuration, thank you Jason Pan!
Related
I have multiple VM's on Azure, all enabled for AAD Authentication.
From my PC, I can RDP into any of them using my AAD creds successfully.
However, if I RDP into one of them, and then from there try to RDP into a different one, it fails with a generic "your credentials did not work" message.
Any ideas why this doesn't work? I would like to use one of them as my daily workstation VM, and be able to RDP into the others as needed.
For the error "Your Credentials Did Not Work"
Please check if below are the reasons for getting the error,
Windows Policy: Maybe Windows Security Policy is preventing non-admin users from signing in.
Username change: If you rename your user account of other VM, it doesn't get change for the RDP connection
To know more in detail please refer this link: Your Credentials Did not Work in Remote Desktop
To troubleshoot the error, please follow below steps,
Try running Network Adapter Troubleshooter
Try changing the network profile from public to private
Try changing account Username
Try editing windows security policy
Try using the group policy editor
To know how to perform all these in detail please refer link.
I am trying to serve static files from a file server running Windows Server 2016. I would like to use a group managed service account for the connection.
I have attempted configuring IIS on Windows Server 2012 to use the gmsa. The Test-ADServiceAccount cmdlet returns True for the gmsa I am attempting to use on the IIS host. I have gone under the basic settings option of the IIS site configuration and used the "connect as" button and set it to the gmsa account with no password. The prompt then says "Connect as 'gmsa-foo$'". However, when I attempt to press "ok", I get an error that the specified password is invalid.
Can I use a gmsa to allow access to the remotely hosted static files that I want to serve? Do I need to use a particular version of Windows Server to do so?
Make sure you added the gMSA account in the application pool identity.
It should be noted that this account may show unexpected behavior in IIS manager. For example, if you click on “Basic Settings” for an application that uses this account for its application pool, “Test Settings” may give you an error indicating “the user name or password is incorrect”. Usually, this can be ignored. Browsing any page in the application would be a better test – as long as you don’t receive a 503 response, the application pool username/password is fine.
You could get more information from the below document:
Windows Server 2012: Group Managed Service Accounts
We're using cloud service to host a MVC web application, we want to access the remote desktop to do some settings. We deploy this application by uploading the packages and configuration file. When we click on the "Connect" button on the cloud service dashboard, we got the error:
"Failed to download the file Error details: error 400 Bad Request"
I think that the 400 Bad Request is a generic response when the Azure RDP configuration is bad. When I went to the old portal and tried to RDP from there I received a better explanation
The supplied cscfg file can not be parsed. Got exception
Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword
Turns out the real issue was that the thumbprint I provided for my cert did not match the cert I had uploaded to Azure. The quick fix was to
Go to the old portal and select my cloud service
Select the 'Configure' tab
Select 'Remote' on the bottom bar
Re-configure the remote desktop settings
It cycled my roles, but when they came back I was able to successfully RDP. The real fix would be to put the correct information in the Cloud Service configuration as you are deploying.
I am not able to connect to Azure via a webapp deployed in tomcat.
I am getting the below error though i am sending the correct input for the keystore pwd.
"Keystore was tampered with, or password was incorrect"
Plz comment.
When you try connecting to Windows Azure Management Portal, using Service Management API, the connectivity is created over SSL tunnel and a certificate is used to create the SSL tunnel.
I would suggest first that, it is not a Windows Azure specific problem, it is more of a Java/Tomcat related issue mainly happening because while selecting the certificate to create the SSL tunnel the code met with some problem.
To solve this problem, I can suggest the following:
In your VM/Physical machine, where Tomcat web application is running try to locate the physical keystore file first and delete it.
After that try creating keystore with correct password and setup that password properly in your Tomcat configuration
Trustcacerts password was supplied wrongly ! Now it works
I'm following the Connecting Apps with Windows Azure Connect lab in the Azure Training Kit.
I've followed the instructions to set up the Groups and Roles, and the Activated EndPoints.
I've updated the SQL Express settings and restarted the service
I've installed the local endpoint, which gives the following text.
I've added a new Windows Firewall rule
This endpoint is configured to
connect, and can connect to other
resources in Windows Azure Connect.
I still get this error displayed in the browser.
Sorry, an error occurred while
processing your request.
Message: The underlying provider
failed on Open. Inner Message: A
network-related or instance-specific
error occurred while establishing a
connection to SQL Server. The server
was not found or was not accessible.
Verify that the instance name is
correct and that SQL Server is
configured to allow remote
connections. (provider: TCP Provider,
error: 0 - No such host is known.)
Any ideas on why this might be or suggestions on finding out where it is failing?
Thanks.
Update
I found this link "Windows Azure Connect and Symantec Endpoint Protection" describing a similar problem; as the title suggests Symantec EndPoint Protection could be the problem.
Although in this case, removing Symantec did not fix the problem
Update 2
some messages from Event Viewer - this set is repeated every 2 mins, they dont appear connected to a web page request.
at 9:29:40 [Information]
The user SYSTEM has successfully
established a link to the Remote
Access Server using the following
device: Server address/Phone Number =
sydrelay4.windows.azure-test.net
also at 9:29:40 [Information]
The link to the Remote Access Server
has been established by user SYSTEM.
at 9:29:41 [Error]
The user SYSTEM dialed a connection
named Windows Azure Connect Relay2 1
which has failed. The error code
returned on failure is 798.
at 9:29:45 [Information]
The user SYSTEM dialed a connection
named Windows Azure Connect Relay2 1
which has terminated. The reason code
returned on termination is 631
I had the exact same issue, Symantec et al. I was able to resolve it by adding the .cer certs I used in the Azure portal for the Hosted Services -> Management Certificates to my personal certificates collection via MMC and then rebooting my computer.
Hope that helps.
If you’re receiving a message like that, it’s possible that your current location has an outgoing port blocked.
Check this thread:
SQL Azure : Connection to SQL Azure throws exception
Is your machine behind a proxy? If so try to run the following commands to set proxy for the local system account:
bitsadmin /UTIL /SETIEPROXY LOCALSYSTEM NO_PROXY
bitsadmin /UTIL /SETIEPROXY LOCALSYSTEM MANUAL_PROXY a.b.c.d:80 NULL