Comments on: How to deal with “Login Failure: the target account name is incorrect” on a Windows file share

By: Matthew

Matthew — Wed, 26 Oct 2011 13:29:33 +0000

Thank you Grant on November 6th, 2009.

I have only one domain with no children or trust relationships and had this error all over my domain when dealing with a particular server. Removing the Client for Microsoft Networks, Rebooting, adding it again, and rebooting fixed the issue.

By: Johnny

Johnny — Tue, 30 Aug 2011 18:56:27 +0000

Worked for me, I had a duplicate computer name from when it was joined to another trusted domain, deleted it and it worked.

By: Jen

Jen — Fri, 10 Jun 2011 09:26:34 +0000

Genius! Thanks for this post, I was baffled by this error!

By: Joe

Joe — Wed, 13 Apr 2011 21:22:30 +0000

I had a similar issue, trying to map a drive on a Windows 7 laptop in one domain to a Windows 2000 server in another domain. The answer was to enter the FQDN as the server name, e.g. \\server.domain.com\sharename and it worked fine after that.

By: Joey

Joey — Thu, 03 Mar 2011 17:55:22 +0000

nothing worked. still getting the same error that target name is incorrect. joined it to dev domain-success, removed from dev domain add to qa domain-error. there is no trust between dev and qa domains…object has been re created, deleted and added back to qa domain…not about to reimage teh server…

By: Rob

Rob — Mon, 17 Jan 2011 21:38:23 +0000

reinstalling the client for MS networks on the network adapter worked for me

By: Jenn

Jenn — Tue, 01 Jun 2010 21:43:40 +0000

Still a useful article, as well as useful comments. I followed Grant’s suggestion from Nov 2009. I had just one workstation with this issue. I removed it from network/AD, deinstalled ‘Client for Microsoft Networks’ from the network adapter, rebooted, reinstalled it and rebooted. Re-added to the domain, and now I can access the workstation’s shared drive. I was two seconds away from re-imaging the thing, so thanks!

By: Chalise

Chalise — Thu, 27 May 2010 15:27:56 +0000

I also had this problem, but it was occurring when a Powershell script was running WMI queries on a workstation that had recently been renamed. Turns out someone was adding a new machine to AD every time he was deploying a machine that was previously named something different on the domain instead of renaming it. A network connection repair and log on/off was all that was needed to fix it on the workstation and fix the problem.

By: Narayan

Narayan — Thu, 11 Feb 2010 06:18:15 +0000

Hi,

I faced same issue, but on a VM.
I have created a snapshot on Win 2k3 vm and tried to use the snapshot after 2 months.
My snapshot has a setup of web application so when ever I try to use it, I got “No authority could be contacted xxx ” message on browser and Login Failue if i try to access the HDD of the VM.

Fix:

My network admin said that, if snapshot is of 1 month old and we revert back to it then the VM is automatically kicked out of domain and we need to add it back again.

Regards,
Narayan

By: David

David — Fri, 08 Jan 2010 02:23:23 +0000

Thanks, I found the same thing. Some PCs on my network continued to work whilst others did not. All worked with FQDN. Removed from second domain. What was obviously happening was it was trying to connect to the box with the creds from the other domain. Thanks!