• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2183
  • Last Modified:

"Target Account Name is Incorrect"

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?
0
talatalo
Asked:
talatalo
2 Solutions
 
himvyCommented:


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.
0
 
abhijitwaikarCommented:
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 .




0
 
talataloAuthor Commented:
Thank you for the help, the issue seems to be resolved once I cleaned up DNS.
0
 
dude02Commented:
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
Description:
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.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now