When trying to logon to the domain from a client PC, I recently got the following error message in Windows:
What was strange was that it was only occurring for one particular user account in Active Directory and not other accounts. When I tried a different account, I was able to log onto the server.
You may also receive this error message in other situations, such as when you type the UNC path to a share in Windows Explorer. If you are getting the Logon Failure message, here are a few things you can try to solve the problem.
What is Dameware Logon Failure Error 1219 error? The Dameware Logon Failure Error 1219 error is the Hexadecimal format of the error caused. This is common error code.
Method 1 – Reset Machine Account Passwords using Netdom.exe
You can run the Netdom command on the domain controller that is responsible for accepting login requests from the PC you are having trouble with.
First, you need to install the Windows Server Support Tools from the CD-ROM. Once installed, you have to stop the Kerberos Key Distribution Center service and set the Startup Type to Manual.
Then restart the server and open a command prompt. You have to restart in order to remove the Kerberos ticket cache. You can also remove this by using the KLIST or KerbTray tools.
Finally, type in the following command at the command prompt:
The /s:server is the name of another domain controller in which the KDC service is running. That server will be used for setting the machine account password.
The other two parameters are simply the username and password for a domain administrator account.
Note that this method basically is fixing a problem with replication between two domain controllers. Sometimes replication can fail because the secret password between the domain controllers gets out of sync.
Make sure replication between your domain controllers is actually working!
Method 2 – Fully Qualified Domain Name
Sometimes, depending on how your DNS is setup on the server, you may have to use the fully qualified domain name (FQDN) of the server rather than just the server name.
So if you are trying to access a network share using a UNC path name or in a logon script, try using servername.domain.lan and it might end up working fine.
If this works, you can change the DNS settings so you don’t have to use a FQDN by going to the DNS settings under Advanced TCP/IP Settings when you go to the Properties for the Network card.
Make sure that the DNS suffix specified in the Append these DNS suffixes (in order) box is correct.
Method 3 – Delete Old Computer Account
Another reason you can get the “target account name is incorrect” error is if a domain controller was recently migrated from a parent domain to a child domain.
In this case, the old computer account for the domain controller may still exist in the child domain. All you would have to do is delete the account from the parent domain and you would be good to go.
Another way to fix it is to remove the server from the domain and rejoin it back to the domain so that the computer account gets reset.
Those are pretty much all the reasons I’ve ever seen for this error, so if you are still having problem with Logon Failure, post a comment here and I’ll try to help! Enjoy!
I am trying to connect to a remote server and deploy a service there, through a deploy script.
I start by stating 'Net use' and send the credentials for the server.
But here I get system 1219 error:
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
I am not aware that I have any connections other than this one to the server.
I have tried net 'use /delete' but was told that no connections were open to the server.
What gives?
khebbiekhebbie6 Answers
1. Fire up a command prompt
2. View current network shares
3. Remove zombie mounts
4. Mount the share as another user
You can also try for more details on how to operate the net command.
use IP address instead of server name? (see Multiple Credentials in a Single Windows NT Session http://support.microsoft.com/kb/q173199/ )
This seemed to help:'net use * /del'
Still i do not know what was my initial mistake...
khebbiekhebbieI have found that if I mount a drive, disconnect, and then try to reconnect with different credentials, this error pops up.
net use * /del
did not help.
net use
shows no connections (checked with both a regular and an elevated prompt)
ipconfig /renew
did not help either
I had to log out and log back in. I wonder where these credentials are cached :(
I had the same problem... a connection had been removed, and did not show up in a net use
list was preventing a new connection.
Running net use * /del
and then answering 'N' seemed to clear it!
I found this required a combination of net use * /del
and disconnecting any previous shared folder sessions on the target server