"Target Account Name is Incorrect"

Posted on 2009-12-18
Last Modified: 2012-08-13
Users in a Windows Domain are getting a "Target Account Name is Incorrect" when they are trying to access a folder share. They can access other folder shares fine but this particular one causes them issues, the issues just seem to begin the last week or so, this had worked fine previously. The folder share is part of DFS, other shares can be accessed fine through DFS. After rebooting their local workstations a few times the issue seems to go away but eventually comes back again. Three windows servers are part of DFS, they all reside in the same physical location as the users. Any assistance would be greatly appreciated?
Question by:talatalo
    LVL 7

    Assisted Solution


    This error normally comes when the secure channel of that particular server is broken.
    Please check  for any kerberos related events and run netdiag to verify the secure channel on the problem server where the folder is hosted.
    LVL 10

    Accepted Solution

    Also  It seems to be related to DNS as AD is dependent upon it ,
    Is the DNS is working fine?,  When you check the "A" name and "C" name records on these servers, do they show up with the correct IP addresses?

    If DNS is fine then check that File and Printer Sharing are ticked on your Server network adapter properties.

    For secure channel issue also try remove perticular workstation from the domain and put it back into the domain .


    Author Closing Comment

    Thank you for the help, the issue seems to be resolved once I cleaned up DNS.
    LVL 4

    Expert Comment

    Event Type:      Warning
    Event Source:      DNS
    Event Category:      None
    Event ID:      4013
    Date:            7/27/2011
    Time:            11:05:27 AM
    User:            N/A
    Computer:      DC01
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Join & Write a Comment

    Experts-Exchange users below are the steps you can follow to upgrade your Lync server to latest CU's or cumulative updates. Note: Perform it during non-production hours.   Step 1: Backup your lync and SQL server database. Follow below article: h…
    Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
    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 from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
    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…

    754 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

    25 Experts available now in Live!

    Get 1:1 Help Now