[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Logon Failure: The target account name is incorrect

Posted on 2008-11-18
Medium Priority
Last Modified: 2013-11-25
Last night the primary domain controller lost its connection for some unknown reason and the secondary domain controller (both Win2003 servers) had problems also.  After fixing some problems, I got the PDC working (somewhat) and some PCs can access the network without any issues.  There are a handful of PCs that cannot access the network share.
One strage issue is that a share was removed on the domain controller which is also the file server that I had to re-add the share.

The PCs that cannot access the DC/File server share and I get "Logon Failure: The target account name is incorrect" when trying to access any of the shares on the DC/File server.  I can access the shares using the IP address of the file server.  I can also ping the server and the DNS appears to resolve correctly.

I ran Nbtstat -a  file2 and got the following response.
Local Area Connection:
Node IpAddress: [] Scope Id: []

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    FILE2          <00>  UNIQUE      Registered
    SFFAIR         <00>  GROUP       Registered
    SFFAIR         <1C>  GROUP       Registered
    FILE2          <20>  UNIQUE      Registered
    AladinHaspV01.2<30>  UNIQUE      Registered
    SFFAIR         <1E>  GROUP       Registered

can anybody help me get these other PC's connected?

Question by:flg8tor96
  • 2
LVL 16

Accepted Solution

speshalyst earned 1500 total points
ID: 22985190

Author Comment

ID: 23070300
I figured out what happened.  It was one of those problems that was caused by multiple things.  First problem was a hardware failure where the server lost connection.  This problem was solved by moving the drives to a spare server that was identical to the failed server.  This caused the second problem.  The Bios date on the spare server had not been updated and caused a Active Directory replication issue since the Bios date was off by more than 60 days. (tombstone).  This caused active directory not to load and since DNS loads from AD that had problems also.  SInce this server was the DNS server but not the master domain controller it could not replicate and load DNS as well several other issues.

Author Closing Comment

ID: 31517862
The middle link got me to go down the right path.  Thanks

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

High user turnover can cause old/redundant user data to consume valuable space. UserResourceCleanup was developed to address this by automatically deleting user folders when the user account is deleted.
It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question