Windows

Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion

Gravatar
0 Votes
Locked

NT clients randomly rejecting domain

By TechieRob ·
Hey all;

We run a multi OS environment with OS's ranging from 98 to windows XP pro (windows me thankfully excluded from this range ). We also run windows 2000 Advanced server as a primary DNS, DHCP and file server. What I have recently noticed is very odd. After some late night configuration (just windows updates really) on the server the NT clients wouldn't work; citing the following error message:

'The system cannot log you on to this domain bcause the system's computer account in its primary domain is missing or the password on that account is incorrect'

Now this message appeared with no direct system change on the NT machines at all. I have tried almost everything, including removing and adding the PC's to and from the domain; both from the workstation AND from the server... but to no avail.

I am also unsure of which specific windows update is the culprit; or why a windows update would cause such a hassle on these otherwise stable machines.

I swear these NT machines have a vendetta against me, has anyone encounted a similar problem?? Does anyone have any ideas?

Cheers

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

by CG IT In reply to NT clients randomly rejec ...

its a message from God.

NT is old, decrepid, ailing and time for its passage to the next life.

gravatar
Collapse -

by CG IT In reply to

just as I am for my bad spelling.

gravatar
Collapse -

by TechieRob In reply to

Poster rated this answer.

Even I could of said that

gravatar
Collapse -

by p.j.hutchison In reply to NT clients randomly rejec ...

What config are these NT machines? Service Pack ver? IS ADSI client installed? Do you use WINS?

gravatar
Collapse -

by TechieRob In reply to

Poster rated this answer.

Standard instal. Latest service pack. ADSI not installed. WINS is installed on the server.

gravatar
Collapse -

by sgt_shultz In reply to NT clients randomly rejec ...

steady, man. have you said any of this in front of the nt boxes? boy, i hope not. my ideas is to look in the event logs on the server see if you can see better error message about this. got ad? also check time and timezone is it synchronised on ntboxes and server? maybe the passwords expired? does the admin account work on the boxes?

gravatar
Collapse -

by TechieRob In reply to

Poster rated this answer.

Only the local admin account works on these boxes. Trying o log on with any domain account will not work. I have checked the logs and they have not revealled anything useful. Passwords are set to not expire. Time is set by a logon script which worked fine before.... We do have active directory and I can add / remove these PCs from it both from the server and from the workstations, but it still does not log in.

gravatar
Collapse -

by p.j.hutchison In reply to NT clients randomly rejec ...

Have you checked Group Policy for any changes to Security. NT4 does not directly support things like IPSec or Digital Signing, Kerberos, etc
which 2000/XP supports but not NT4.

gravatar
Collapse -

by TechieRob In reply to

Poster rated this answer.
There has been no major changes to our group policy regarding these security protocols. What would changing the WINS configuration do to the NT clients?? (thinking from a service pack prespective)

gravatar
Collapse -

by TechieRob In reply to NT clients randomly rejec ...

The problem with these machines is that they failed to initially auhenticate with the server. Once the user had logged in locally with the local admin account they could still gain access to network shares (with standard authorisation). I wrote custom batch scripts with a stack of "NET USE" commands and intergrated the authentication within these scripts. Though this method is a little lasp in the security department (clear text transmission of passwords)it has so far been successful in getting the clients working again. This method i think will be in place until these machines get replaced.
Moral of the story - NT sucks!

Back to Windows Forum

Start or search

Related Discussions

Related Forums