Hello,
Thanks for your post.
I understand when you try to map a drive, you receive the following error:
"Login failure: The target account name is incorrect."
If I misunderstood your concern, please feel free to let me know.
First, please help me know more about your network topology:
1. Do you have multiply DCs in your network? Is the DC you want to map
drive located in the different sites?
2. Does the issue occur on every client?
3. What is the result if you use UNC \\servername\shares to visit the DC
drive, do you encounter the same error?
Based on my research, this issue is caused by the replication between
multiply DCs. I found following KB articles related it and I will give a
main gist of every article:
Cause1:
====================
This error message can occur if two computers have the same computer name.
One computer is located in the child domain; the other computer is located
in the parent domain.
Please rename computer in parent that has same name as DC in child. For
more details, please refer to the following article:
310340 Error Message: Logon Failure: The Target Account Name Is Incorrect
http://support.microsoft.com/?id=310340
Cause 2:
==========
This issue may occur if the Service Principle Name (SPN) for the domain
that is hosting the replica has not been propagated to the domain that
contains the account that you use when you run Dcpromo.exe. This
propagation may have been delayed because of replication latencies.
Please logon with domain admin of child domain, or wait for replication to
complete and use root admin account. For more details, please refer to the
following article:
296993 "Logon Failure: The Target Account Name Is Incorrect" Error When
Promoting Domain Controllers or Creating Replicas
http://support.microsoft.com/?id=296993
Cause 3:
=========
If this error is being reported for Active Directory replication between
two domain controllers of different domains which have a parent/child or
tree root trust relationship, this error may be due to an absent critical
object that represents the trust relationship between the two domains. This
object is known as a "trustedDomain" object (TDO) and is found in the
System container in the Active Directory Users and Computers tool. This
type of object directly relates to the trust relationships displayed in the
Active Directory Domains and Trusts administrative tool. If this object is
not present in the Active Directory, cross-domain authentication will not
be able to succeed contributing to the errors described above.
Please reset the trust between parent and child with netdom. For more
details, please refer to the following article:
257844 Active Directory Replication and Knowledge Consistency Checker Fail
without Trusted Domain Object
http://support.microsoft.com/?id=257844
Cause 4:
=========
This issue also maybe caused by DNS, you can use the following method to
fix DNS:
Run "netdiag -v" from a command prompt, which will create a netdiag.log
file in the same directory that Netdiag was run. Resolve any DNS errors in
the netdiag.log before proceeding. Netdiag is in the Windows 2000 Support
Tools on the Windows 2000 CD-ROM or downloadable here:
http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/supporttools
..asp
For more information on configuring DNS for Active Directory, review the
following Knowledge Base article:
291382 Frequently Asked Questions About Windows 2000 DNS and Windows Server
http://support.microsoft.com/?id=291382
If the issue persists after performing the above steps, please help me
collect the following information and send to me at (e-mail address removed)
so that I can perform further research on this issue:
1. Screen shot of the detailed error information
To take a screen shot
---------------------
a. Press the Pr Scrn key once on the keyboard when the error message
appears.
b. Click Start, go to Run, enter MSPAINT in the open dialog box, and then
Click OK.
c. Use Ctrl + V to paste the screenshot to the canvas.
d. From the File menu, go to Save and save it as a JPG file.
e. Send the JPG file to me as an attachment.
2. To collect the Network MPSReport as following steps on both the client
and the server side:
a. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE. to download the file.
b. Run the MPSRPT_NETWORK.EXE
c. Wait for 10~15 minutes.
d. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\Network\Reports\cab\
e. Send the .cab file directly to me.
HTH!
Thanks & Regards
Amanda Wang [MSFT]
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
====================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================================
--------------------