I had to change the admin password as it had expired via RDP. The server was working fine after the change.
Later I disconnected the session, and started it again, now we are getting the following error message:
An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote computer: **.cloudapp.net
This same error keeps coming up even after 2 server restarts. The password is defiantly correct as typing a different password gives a "Password Incorrect" error.
There is no other way for us to access this server.
I found the answer here.
Your machine should still have a local administrator account (e.g. MachineName\Administrator), in which case you can login with the administrator account. In the RDP login prompt, you'll need to put the full user account (e.g., "MachineName\Administrator" where MachineName is your computer's name, otherwise it will default to "PreviousDomainUsed\Administrator").
This happened to me with an Azure VM because the domain administrator account I was using had an expired password and the Azure VMs enforce Network Level Authentication, which prevents you from changing the password through RDP. I was able to update the password by logging into the domain controller's VM, but the VM I couldn't log into didn't receive the update because the DNS settings were incorrect. I RDP'd into the faulty VM with the local administrator account, updated the DNS settings and ran "gpupdate" in a Powershell command prompt and everything began working again.
Hope this helps.
I had same issue with local admin account and specifying user account as "machine name\Administrator" still did not work. There was only local admin account in Azure VM so I needed to solve this issue for local admin account.
I could reset password for local admin account by following step then now I can log in to Azure VM by local admin account.
Open Azure Portal web site.
Click "Virtual Machine" then click virtual machine name which issue having in the list.
Dash board for selected virtual machine is shown. Then click "Reset Password".
Following screen is displayed so specify local admin account name nand password, then click Update.
This uses the VMAccess extension to reset the built-in administrator account and reset the Remote Desktop service configuration. Learn more
Mode
You can perform a password reset, which will also reset the Remote Desktop service configuration, or choose to reset the configuration only.
Reset password
User name:
If you provide a different user name, then the built-in administrator account with be renamed. Also, the account will be enabled if it's currently disabled. (The name of local admin account is shown as default)
Password
Confirm password
here is an answer if you need it yet.
http://social.technet.microsoft.com/wiki/contents/articles/18710.troubleshoot-azure-vm-by-attaching-os-disk-to-another-azure-vm.aspx
Related
I have an Office 365 account where I am admin. I used that same account to create an Azure space or account, where I "believe" or "should" be admin as well. In both cases, I am the only user. Both work fine and I can log into both with same user name and password. I created an RDP connection to a VM that I create in Azure. The only user name and password that I would know of to use is the same one that I log into Azure with, but it never works. Seems to be connecting but just rejecting credentials. What username should I use? I can't use one that I create on the VM because I can't get on there yet.
When you create a VM you need to give it admin username and password. And you would use those to login, so check what you did input and use that.
You can reset the existing user password or create the new user/password from the 'Reset Password' option from the Azure Portal as well.
I needed to use the name of the domain of the VM in front of my username to get in.
I have created a Windows Server 12 VM on Azure platform. And I created Ftp server on IIS server in the VM. The Ftp server is publically accessible using all users accounts. Currently I have only admin user account. I am trying to create couple of more user accounts & Ftp servers and assign each user to specific Ftp server.
I tried to create user account via Control Panel\All Control Panel Items\Administrative Tools->Local Users and Group->New User, but it does not allow me to progress. It just throws unknown error.
Any idea over how shall I create new user account so that it can be publically used for Ftp service authentication?
I finally managed to create new user from Control Panel\All Control Panel Items\Administrative Tools->Local Users and Group->New User.
The unknown error was thrown because of password was not strong and entered invalid chars in Description, Full name textboxes. The error message from Win Server did not help at all.
When I click on connect button in Azure Portal, the RDP file is opened and it asks for credential,. not sure what credentials to give. Is it my login to azure portal or something else?
The RDP login prompt shows "MicrsoftAccount\PortalLoginUserName" as user name.What should be typed in password? Is it the portal password? If i try that it does not work.
When creating VM i have provided new username and new password is that what i need to use? if this what i need to use what would be domain?
You need to use the username and password you used when provisioning the VM. These credentials are not the same as your Azure account credentials. And every VM may have its own unique credentials.
When entering your username in the RDP client, either enter \username or localhost\username.
We have a service account defined for anonymous access which is used for several web sites hosted on the web server. This account has access to several network resources like report server, file servers and so on.
While deploying a new web site, we used the same service account for anonymous access. IIS takes the username/password for the account and then a dialog opens for confirm password.
Accidently, we gave a wrong password in both the text boxes, the new site with wrong password is working fine but all other previously hosted sites which were using the service account, started giving the unautorized access error.
Is it possible that when we entered wrong password for the new web site, the password of the account got reset and all sites stopped functioning?
If this was IIS5.x then yes it's possible that the password update you performed did indeed change the anonymous account password.
If this was IIS6 then there are a number of pre-conditions that must be met before changing the password in IIS manager changes the password for the anonymous account. This MS knowledgebase article covers this is detail:
IIS 6.0: HOW TO: Configure IIS to Control the Anonymous Password (MS KB:332167)
In IIS7 this capability was retired.
I have come across a strange problem in one of our applications on win2k8/Vista x64 with UAC enabled. It is a process which hosts the UI for our service and runs in the context of the logged on user.
When logged in as a domain user who is a member of the "Administrators" group, writing to the registry under HKLM fails due to UAC with access denied.
But when logged in as the local "Administrator" account (non-domain) then writing to the registry succeeds.
Both accounts are adminstrators - is there a distinction between domain and non-domain accounts with UAC? What gives?
Thanks... from further reading it seems that it does affect vista as well:
"Being part of the Local Administrator Group doesn't provide the same access as the Local Administrator Account (the same also applies to Windows Vista). With Windows Server 2K8, the administrator access token is split into 2 tokens when logged into the server. One of these is an administrator token and the other a standard user token. During the logon process, authorization and access control components that identify an administrator are removed, leaving a standard user token. The standard user token is used to start the desktop and, therefore, all applications that start run as a standard user."
not sure if this applies but by holding shift+control you can start applications in admin mode, even if youre logged in with a domain admin account. you can then use the application as a local admin