Re: \\computername error: The target account name is incorrect.

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 01/29/05 

Date: Fri, 28 Jan 2005 18:46:42 -0600

If you have not done such yet try running dcdiag on both of the domain
controllers to see if anything pertinent is reported. It may take a bit for
things to get back in synch and hopefully by now they are working
etter. --- Steve

"Sergey L" <SergeyL@discussions.microsoft.com> wrote in message
news:D9F94920-C856-4A69-B2B0-18A0934D6AE3@microsoft.com...
> Steven, thank you for your advice.
>
> This morning one of the users couldn't log in anywhere on the network. I
> linked it back night before when I tried following Microsoft article,
> disabling kerberos center and resetting netdom. But I ran netdiag /fix and
> it
> solved the problem. However old problem of not being able to access
> \\EXCHANGE remains.
>
> Couple more facts:
> When looking at \\DC2 DNS, first DNS server \\EXCHANGE has STOP sign next
> to
> it and said access is denied.
> DC2 DNS can be accessed ok.
>
> C:\>net use \\exchange
> System error 1396 has occurred.
>
> Logon Failure: The target account name is incorrect.
>
>
> after running netdiag /fix on \\DC2 the only warning message came up was
> this
> [WARNING] Failed to query SPN registration on DC
> 'exchange.domain_name.local'.
>
> But I'm not sure if it was there before and Microsoft article mentiones it
> as known but harmless warning.
>
> netdiag /fix ran fine on \\EXCHANGE second time
>
> I will monitor both DCs over weekend and keep searching for solution.