User Can't Authenticate to Domain

[skymut]

This a bit long, please bear with...

I am setting up a notebook on our network/domain. I've set up LOTS, and I believe that the problem is local, on the notebook itself, not a configuration issue.

Obviously, the notebook is running 2000 pro, and it is connected to a 2000 mixed domain.

I have all the protocols installed and configured correctly, and the address of the notebook is on the same segment as the domain controllers.

What is happening:

I can log-on to and get authenticated on the network using MY username and pass. The user of the machine cannot. I checked everything in regards to the user's credentials (id and password).

The notebook acts as if it isn't even trying to go out and authenticate the user's credentials. As soon as I put in the credentials and hit enter, it immediately comes up with the stupid, 'cannot log user on, no domain controller, check that caps lock isn't on, etc.....'.

What I have tried:

First, I checked all my config info, and everything is correct. As I am able to log-on, I don't think that is the issue.

Second, I put the address on the same segment as the dc's.

Third, I disjoined the computer from the domain, and subsequently rejoined the domain.

None of these worked.

So, has anyone run into this/know of the solution?

Thanks for any help. 'If at first you don't succeed, then skydiving isn't for you.'

 

[crisc]

What happens if this user tries logging into another PC? Same thing?

"...the notebook...is connected to a 2000 mixed domain."

What do you mean by this?

 

[skymut]

Mixed domain = Some of our DCs are 2000 Server, and some are NT 4.

Okay, I was able to log-on to the domain with the 'problem' users credentials on an NT workstation, BUT, I was unable to log-on to the domain with the same credentails from another workstation running 2000 pro..hhmmm.

Policy issue, maybe? 'If at first you don't succeed, then skydiving isn't for you.'