Local profile corrupt?

[Eoin O'Beara]

Hi all,
I am having an issue with XP SP2 clients (about 5 out of over 100) on a
Windows 2000 domain. When the user goes to login with their correct Username
and password, it says, "The system could not log you on. make sure your user
name and domain are correct, then type your password again....". the clients
only have one domain configured, the computer account and user account are
on the domain and are enabled. User account is not locked out (otherwise I
would get a different error). I can login as a Domain Admin, and I can login
locally. The domain user account has local Admin rights (part of the local
Admins group).

If I remove the machine from the domain and add it back in, it is ok. But,
if they reboot, it fails with the same error again. I tried to create a
different user on the domain and they can login with that (but that causes
other issues...desktop...shared drive permissions!). I can then login as a
domain admin and copy the original profile data to the new profile and it
still works. Anyone any ideas why the users can't login with their own name?
There are no spaces in the names, or numbers. At the moment I have to remove
all of the effected machines and re-add them to the domain every day, bit of
a pain!



--
Thanks,

Eoin.

Eoin O'Beara,
Technical Manager,
CompuDoc
01-8254117
www.compudoc.ie

 

[Guest]

Hi all,
I am having an issue with XP SP2 clients (about 5 out of over 100) on a
Windows 2000 domain. When the user goes to login with their correct Username
and password, it says, "The system could not log you on. make sure your user
name and domain are correct, then type your password again....". the clients
only have one domain configured, the computer account and user account are
on the domain and are enabled. User account is not locked out (otherwise I
would get a different error). I can login as a Domain Admin, and I can login
locally. The domain user account has local Admin rights (part of the local
Admins group).

If I remove the machine from the domain and add it back in, it is ok. But,
if they reboot, it fails with the same error again. I tried to create a
different user on the domain and they can login with that (but that causes
other issues...desktop...shared drive permissions!). I can then login as a
domain admin and copy the original profile data to the new profile and it
still works. Anyone any ideas why the users can't login with their own name?
There are no spaces in the names, or numbers. At the moment I have to remove
all of the effected machines and re-add them to the domain every day, bit of
a pain!



--
Thanks,

Eoin.

Eoin O'Beara,
Technical Manager,
CompuDoc
01-8254117
www.compudoc.ie

 

[Guest]

Hello

Have you tried a format and rebuild on one of the problem PCs?
That should generate a new SID for the client. Although it's probably got
nothing to do with it as you can logon successfully as Network Admin and
stuff.
Have you tried just renaming a profile directory, or deleting the profile
directory, of one of the users with the problem? That way when they logon on
again a new profile should be generated automatically. Sounds to me like
there is something wrong with the .DAT file...only a guess though!

Cheers

 

[Eoin O'Beara]

Hi there,
I haven't tried the first option, but I think its more related to the
user account as a pose to the computer account.

If I give them a different username they can logon, so by that reasoning I
would say that if I were to rename\delete their profile folder under Docs &
Settings it would have the same effect. Anyone know whats causing this??

--
Thanks,

Eoin.

Eoin O'Beara,
Technical Manager,
CompuDoc
01-8254117
www.compudoc.ie

 

[Guest]

Probably a knackered .DAT file.
It accesses the dynamic part of the systems registry and does fancy things
to load the specific users profile, like the desktop and how that's
configured so the user can load apps.

Rename the profile and see how you get on, a new .DAT file is created and
you can always logon as admin and copy the old profile to the new one...just
leave the old .DAT file behind and old .INI file too. Just stick with the
fresh files created by the OS.

Hope thats a fix for you

 

[Guest]

eh..rename the old faulty profile I meant to say

Probably a knackered .DAT file.
It accesses the dynamic part of the systems registry and does fancy things
to load the specific users profile, like the desktop and how that's
configured so the user can load apps.

Rename the profile and see how you get on, a new .DAT file is created and
you can always logon as admin and copy the old profile to the new one...just
leave the old .DAT file behind and old .INI file too. Just stick with the
fresh files created by the OS.

Hope thats a fix for you