Logon Failure: The Target Account Name is Incorrect

[Jeff Pryor]

Please help
I have two Win 2K servers in a single domain. Both running SP4.
One server has decided that it will not browse the other by name at
all.
All indications point to a DNS issue but I have gone through all DNS
settings with a fine toothed comb and nothing looks wrong. I have even
gone so far as to uninstall and reinstall DNS.
Here is my config

Server 1 - DC,DNS,WINS,File and Print,FSMO
Server 2 - DC, File and Print

Server 2 is pointed to Server 1 for DNS resolution. I can ping Server
1 from Server 2 all day and get immediate response with the correct
IP.
If I try to browse to share on Server 1 from Server 2 via Windows
Explorer I get the Logon Failure error. I get the same error if I try
to map a drive. If I map a drive via IP however, I get in without any
issue.
Server 1 can browse Server 2 without problem.
This causes multiple issues. Of course AD replication can't take
place. Also if a client happens to authenticate to Server 2 they
can't access resources on Server 1 with the same error.
Also I can't DCPROMO down Server 2 because it says the other DC is
unavailable.
Any help would be appreciated.

 

[Mtty]

This is almost exactly the same problem I've been having for the past
week or so. Unfortunately for me, it's not been limited to only one
machine. I've got four (so far) machines that have been driving me
nuts. And of course, the latest one to be hit happens to be mine. In
my case, server 1 is the file server for roughly 20 machines, a
mixture of 98, w2k, and XP, and server 2 is used as a proxy between
the 'Net and the rest of the network.

I've kept up to date with almost all patches and upgrades, only having
avoided SP4 as I heard there were some issues, and wanted most of
those to be found and cleared up before I attempted an install of it
(I did test it on a couple workstations, without any problems). I
thought that the proxy box had somehow gotten toasted, but when the
other systems began showing up it made me focus on the main server.

Now, one thing I did try was to change the password on the 2nd system
that was affected, and that seemed to do the trick. But when I tried
to change it back to the original pw, the error arose again.

Thinking about this at lunch, I came up with this hypothesis... I can
browse the other computers on the domain that's set up on it without
any issues (minus the one of course), so that makes me believe the DNS
is fine. I can browse the computer by putting in its IP addy in the
window instead of the computer name, so that makes me believe that any
routing is fine. And I can access the files on the machine as before
without issues, so that makes me believe that the domain security is
fine.

So that only leaves me thinking that it's either a local issue and not
a 'network' issue, or something locally is preventing the computer
name resolving to the IP address. Any ideas folks, this is driving me
up the wall and it's not like I don't have other work to do as well
And lord knows I'll flip out if the rest of the systems begin doing
the same thing.

I'm not a MCSE, just the 'lucky' one who happened to casually mention
during my job interview that I was pretty familiar with computers so I
got stuck looking after this mess. So please make any solutions easy
to understand and follow

Mtty