Logon Failure: The target account name is incorrect
I'm managing a small business domain with a W2K R2 server. I've got 2 Windows 7 Pro PCs on the domain as well as 4 XP Pro PCs. One of the Windows 7 PC is giving me fits. It's got a printer that needs to be shared out. Up until 2 days ago, the printer was working fine. Then all of a sudden, no one can connect to it. If you try to browse to the PC by \\pcname, you get the "Logon Failure: The target account name is incorrect". I've tried removing the PC from the domain, deleting the PC name and renaming the PC, and then putting it all back. And then it works for about 15 to 20 minutes, and the stops working again. I shared out the c:\Windows\System32\spool\PRINTERS directory and gave domain user full control of that folder. That worked for about another 15 minutes, and the quite again. The folder is still shared out, but no one can access it. Not even the domain admin.
March 25th, 2010 4:48pm

Hi, Based on my research, please refer to the following article to troubleshoot the issue first. Logon failure: the target account name is incorrect Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. If the issue persists, please also temporarily turn off firewall on the machine and create a new domain account to login on the machine for a test. Thanks, Novak
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2010 2:01am

disable IPv6 in Local Area connection Properties and delete IPv6 Host (AAAA) in DNS server Manager.
June 15th, 2011 8:40pm

disable IPv6 in Local Area connection Properties and delete IPv6 Host (AAAA) in DNS server Manager.
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2011 8:40pm

Try using the full path for instance instead \\pcname put in \\pcname.domain.local
February 10th, 2012 6:49pm

If you are stil not fixed: Check the machines DNS Suffix and NETBIOS Computer Name dialog (Under Computer Domain Changes dialog, which is under System Propteries) and make sure it is NOT blank and that the Change Primary DNS Suffix when domain membership changes check box is checked. If both of these are blank the Service Principal Name (SPN) of the machine will only be the short name. Setspn -l computername will show you the current status of the SPN (pronounced Spins). If you don't see any with FQDN's, that is a problem. A common machine should look something like this: setspn -l rodney-hp Registered ServicePrincipalNames for CN=RODNEY-HP,OU=Workstations,DC=domain,DC=com: RestrictedKrbHost/RODNEY-HP HOST/RODNEY-HP RestrictedKrbHost/RODNEY-HP.domain.com HOST/RODNEY-HP.domain.com Add in the DNS Suffix, check the box, reboot. BAM you can now get to UNC paths on the computer. Setspn -l computername wil now show double the number of entires, one short name based, one FQDN based. Rodney R. Fournier - Microsoft.com Senior Premier Field Engineer Active Directory Platforms - SecurityGive me NNTP or give me death
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 3:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics