Question : Logon Failure: the target account name is incorrect.

In the past 2 weeks I have had many Servers/workstations come up with the following error:

\\servername is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions.

Logon Failure: the target account name is incorrect


(that is from a windows 2003 standard server trying to access another server(global catalog server). If you browse to the resource using the IP address you are able to access it. Rebooting the machine frequently takes care of the problem also. I have read the previous post and have not had much luck. Any input would be great. Thanks!

Josh

Answer : Logon Failure: the target account name is incorrect.

The Event ID you just posted (DNS - 6702) can largely be ignored.  It has to do with services starting at different intervals and screwing up dependencies.  The quick and easy fix is to have your DNS servers point to each other for DNS resolution instead of themselves.  In other words, this probably isn't causing the problem.  However, there is an exception:  If your DNS SRV records never repopulated when you reinstalled the server, then your other DCs wouldn't be able to find the new server.  To make sure this has occurred correctly, make sure that your DNS zone is set to accept dynamic updates.  Then, on the DC that doesn't play well with others, restart your Netlogon service (which automatically repopulates these records in your DNS zone).  See if this fixes the problem.

If this doesn't work then, it still sounds to me like it's a trust/account issue.  Here are some things for you to look at.  Some of these are articles or suggestions for Windows 2000, but they'll work in 2003 as well:

1. You could be getting Kerberos authentication errors.  This is somewhat common when you're replacing FSMOs.  To fix it, you need to reset your computer account.  See KB article 260575:
        http://support.microsoft.com/default.aspx?scid=kb;en-us;260575
2.  Check your hard disk space on the hard drive that has the NTDS folder.
3.  A great article on troubleshooting NTFRS replication issues is KB article 327341:
        http://support.microsoft.com/default.aspx?scid=kb;en-us;327341
4.  Make sure that the SYSTEM account has Full Control on the SYSVOL folders.
5.  You can try to modify the JRNL_WRAP_ERROR registry value:
        >Stop the File Replication Service
        >Click on Start then Run and type REGEDT32 and hit ENTER
        >Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters
        >Click on Edit then New then DWORD Value
        >Make the value name Enable Journal Wrap Automatic Restore
        >Open the value.  Keep Base as Hexadecimal and enter a 1 for the Value Data.
        >Get out of Registry Editor
        >Restart your File Replication Service
6.  Make sure that you're not getting time synchronization errors.

If the servers are in the same site, check out KB article 249256 at http://support.microsoft.com/default.aspx?scid=kb;en-us;249256.

Let me know if this helps.

<-=+=->