Logon Failure: The target account name is incorrect

Posted on 2008-11-18
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
    LVL 16

    Accepted Solution


    Author Comment

    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

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

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to improve team productivity

    Quip adds documents, spreadsheets, and tasklists to your Slack experience
    - Elevate ideas to Quip docs
    - Share Quip docs in Slack
    - Get notified of changes to your docs
    - Available on iOS/Android/Desktop/Web
    - Online/Offline

    On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
    Learn about cloud computing and its benefits for small business owners.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

    761 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

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now