Discussion Locked

NT Profile

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

my users got a error when they logon to NT4 server although they can log in and everything fine--but how i can get rid of this error--
``A domain controller for your domain couldnot be contacted.you have been logged on using cached account information. changes to your profile since you LAST logged on may not be available.``

9 replies

by robertp

Your user is not actually logged onto the server. They are logged onto the machine through local security. I would first check the network connection. try to ping internally first 127.0.0.1. If that worked, ping your server. I will get that message if I have no connection to the server. Could be a cable or a NIC. Let me know what happens.

by bill cassada

This sounds like a connectivity issue. Have you removed and then added this wkstn to the domain? If so, the SID is different - meaning that although the computer looks and feels the same, it isn't. You'll have to do the following:

1) remove theworkstation from the domain and place it in a workgroup (I use CHANGEME for this)
2) delete the computer acct from the user manager for domains on the PDC
3) RESYNC the domain!!! this is important!!
4) manually add the computer acct back to the domain using the user manager for domains, and once again RESYNC THE DOMAIN.
5) finally, go to the workstation and add it back to the domain thru network properties. At this point it is not necessary to create the account.

Good luck!

by tuck46

That's usually just a time out error when the system has been rebooted and it wont usually affect anything. It can be fixed in the registry by changing the time out from (I belive) 250ms, however, if you log off and log back on you wont get the error.

by lin

If the above responses do not work (which they should because they are very good solutions), try going into a command prompt and typing:

ipconfig /release

ipconfig /renew

I've had a similar situation where the computer got a bad subnet maskand that was the reason why it got the message that you're getting.

This discussion is closed to new replies.