Logon Failure: The target account name is incorrect.

[Neko-]

Since yesterday afteroon I've expirienced a problem on two domain
controllers, both running Windows 2000 Server SP4 and holding all the
latest fixes. Up to yesterday communication between the two went off
without a hitch.

After adding Microsoft ActiveSync on DC2 (to facilitate connectivity
to an IPaq), it seems it's no longer possible for DC2 to connect to
DC1. It does work the other way around tho. DC2 to DC1 results in the
error, while DC1 to DC2 works without any problems.

The error generated is: Logon Failure: The target account name is
incorrect.

Googling for a solution I've located :
http://www.experts-exchange.com/Operating_Systems/Q_21018430.html

The workaround described (\\IPadress\share instead of \\PCname\share)
works, so I got a workaround. This however doesnt solve the problem
yet..

Renaming the offending PC (according to
http://www.computing.net/windows2000/wwwboard/forum/58467.html)
wouldn't work, seeing you cannot rename a Domain Controller that
easily.

I've checked the NetBIOS settings and they should be correct. I also
reapplied SP4 on both machines to eliminate any possibility of file
corruption somewhere. Pinging between machines (on both IP address and
name) works like a charm. All regular network/internet traffic seems
to work 100% aswell.

From the network the workstations can communicate with one another and
both DC1 and DC2 without any problems.

My guess is that on DC2 something changed that is causing the problem,
and the Microsoft ActiveSync (3..7.1) might be the cause of it. I
tried deinstalling it, but this did not solve the problem.

If anyone has any thoughts that might help in placing a solution with
this issue, I'd appreciate hearing from them.

Thanks in advance for any and all responses. .

Jurriaan van Doornik
jrvd(removethis)@xs4all.nl

 

[Neko-]

It seems the problem has just spread to other networked PC's (Windows
2000 Professional with SP4 and latest fixes installed).

If anyone has any clue how to solve this I'd appreciate the info...

Regards, J. van Doornik

 

[Neko-]

It seems the problem is restricting itself to Windows 2000 PC's. I'm
not running any Windows XP or NT machines, but an older Windows 98
machine within the network has absolutely no problem whatsoever to
connect to both machines.

It connects under both IP address and DNS name.

This shed any further light on the subject?

Thanks for the feedback

 

[Neko-]

Although no-one could appearantly help me through this group I got the
recommendation of using the netdiag and dcdiag applications for more
troubleshooting through the dutch W2K help group.

I wasn't aware of the existance of these programs, but they did help
me dig out the problem further.

IPConfig /regsister DNS did not work (I did not expected it to seeing
the netdiag already told me all DNS entries were properly registered.
Also rebuilding the DNS server couldn't solve the issue.

Adding a WINS server also did not resolve the issue.

When digging further through the dcdiag diagnosis, I managed to find
some entries on some forum (I can't recall which one) which pointed me
to http://support.microsoft.com/?id=288167 as having a solution for
the described problem.

I implemented this solution and am pleased to report that the problem
seems to be fixed at present. Workstations and servers can all connect
to one another normallty again.

Regards.