Win2k Server Denies Logon Attempts... 1

[IanGlinka]

Ever since we installed our Windows 2000 Server, users logging onto the network are frequently getting the message you get when you type your password incorrectly. However, the passwords are not incorrect. It's as if the server is just refusing the logon attempt for no reason at all. Does anyone know why this might happen?

Thanks

Ian

 

[CostaRica]

I am having a similiar (or the same) problem. Users repeatedly get the message about the server not being able to validate their password, and then after a few tries it logs on (even without having to retype the password).

I thought it was faulty network card, but replacing it does not solve the problem. Any suggestions welcome.

 

[N0ktar]

It has to do with TCP/IP, not sure why, but if you install an additional protocol on both client and server it will solve your problem.

 

[Jpoandl]

I've never seen this problem. What types of clients do you have? Is your domain in mixed mode or native 2000?

Are there any event viewer error messages on the client? Are there any event viewer error messages on the server?

(I would not suggest adding a network protocol to your clients and server...this does not sound like a reasonable workaround... This would place uneeded overhead on the network..and probably slow network access...)
Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.esavio.com

 

[GlenJohnson]

I had the exact same problem and found the nic on my server was going bad. I have 3 W2K servers, and I re-booted all of them at different times. When I re-booted the server with the bad nic, the users logged on with no problem. When I had them log on after the server with the bad nic was up, they couldn't log on again. Monitor your nic for bad packets and see what you find. Good luck Glen A. Johnson
Microsoft Certified Professional

"To know, is to know that you know nothing.
That is the meaning of true knowledge."
Confucius (c. 551-479 B.C.) Chinese philosopher

 

[CostaRica]

I found the problem with mine. There was a second NIC in the server with the range x.x.2.x when we use only x.x.1.x
The card was plugged in alright, but not configured to do anything. Like Glen said, the packets were doing something screwy. I second the opinion of checking for bad packets.