I have been having this problem now for about a month. Everytime I add a new win2k or winxp computer to my windows2k network, after a day or so they all get this error message after trying to access a resource on the domain controller. "Logon Failure: The target account name is incorrect" The computer gets no error messages at logon but does not connect to anything. If i do a net view \\servername i get "error 5 access denied". I get that same error message from any net command i type. The only way to get that pc back on the domain is to either sysprep, or join a workgroup, change the pc name then rejoin the domain. I think the problem is in the computer account in the domain. I have also gone to AD users and comp and reset the computer account but that does not help. Can anyone throw some ideas at me or has anyone seen the same issue?

The user is not in your AD or in the wrong OU. The error 5 message is the one you get when the user is not know in the AD. The computer logs in locally when this happens. If you use ipconfig you can see the computer has no valid ip adress for your network. Insert the user in the good OU and give hem enough rights then you will see that everthing works fine

I dont think it is the user account that is causing the problem? I get the same results even if i log in as domain admin from the problem (win2k or xp) pc. I get an ip address, but i can not connect to anything. Some of my domain controlers even give the "error 5 access denied" when doing a "net view \\servername" to another domain controller in the same domain.

I am having the same problem too, so if anyone knows an answer please tell me..

I have just resolved a problem like this and though I can't guarantee the results here is the benefit of what was wrong in my system. Basically it was a DNS problem. When you are connecting to your domain controller ensure you are using the correct DNS address. I'd suggest doing a ping (i.e ping [servername]) and ensuring the IP address is what it should be. If it isn't then check where the incorrect address is coming from. It could be your DNS server or (in my case) an erroneous entry in the HOSTS file. You may want to see Microsoft Knowledge Base Article Q263208. Best of luck.