"system cannot log you on"

[Guest]

I had to revert to "Last Known" and after doing so the auto login I set up is
now an error stating "the system cannot log you on/check your domain, etc."
Strangely enough login will proceed if I hit "enter" and then I have to click
on the user for the boot to finalize.
Running CONTROL USERPASSWORDS2 reveals that the password box is unchecked.
In Tweak UI I set up the correct username and password, and still the error
occurs. The set domain is the name I gave my system - is that correct? I have
NET Framework 3.0.
Thanks,
Holly

 

[Malke]

I had to revert to "Last Known" and after doing so the auto login I
set up is now an error stating "the system cannot log you on/check
your domain, etc." Strangely enough login will proceed if I hit
"enter" and then I have to click on the user for the boot to finalize.
Running CONTROL USERPASSWORDS2 reveals that the password box is
unchecked. In Tweak UI I set up the correct username and password, and
still the error occurs. The set domain is the name I gave my system -
is that correct? I have NET Framework 3.0.
Thanks,
Holly

It is not correct. You only use a domain if your workstation is a member
of a domain. You must have a server running a server operating system
to have a domain.

Control Panel>System>Computer Name

If you don't have a domain, change back to Workgroup.

Malke

 

[Guest]

Thanks for your reply, Malke. Yes, this is a solitary system with one user.
At some point I changed the WORKGROUP name to SMITHGROUP in a fit of newbie
creativity. I can't change it back to WORKGROUP, as that section is now
greyed back and inoperable.
Is there another way besides system>computer name?

Holly

 

[Malke]

Thanks for your reply, Malke. Yes, this is a solitary system with one
user. At some point I changed the WORKGROUP name to SMITHGROUP in a
fit of newbie creativity. I can't change it back to WORKGROUP, as that
section is now greyed back and inoperable.
Is there another way besides system>computer name?

You can call the Workgroup name anything you want. It is a
cosmetic/organizational device only.

I'm afraid we need a bit more information. Why did you have to revert to
"Last Known Good"? What problems were you having? That could shed a
light on what is happening now.

Malke

 

[Guest]

Hi Malke,

I had to pay a tech to yank Norton SysWorks out by the teeth because it was
causing errors and crashes and wouldn't uninstall. Shortly thereafter my ATA
and floppy drives ceased to function. I mean dead. I was advised to do a
"Last Good" and that cured the problem. The only casualty was the auto logon.
A small thing, but I use memory-hungry programs, and the sys seems to work
better if I restart several times a day. The logon issue has become annoying.

Holly

 

[Malke]

Hi Malke,

I had to pay a tech to yank Norton SysWorks out by the teeth because
it was causing errors and crashes and wouldn't uninstall. Shortly
thereafter my ATA and floppy drives ceased to function. I mean dead. I
was advised to do a "Last Good" and that cured the problem. The only
casualty was the auto logon. A small thing, but I use memory-hungry
programs, and the sys seems to work better if I restart several times
a day. The logon issue has become annoying.

It would seem that the tech yanked a bit too hard in the registry. To
fix the logon problem, try:

1. System File Checker:
Start>Run>sfc /scannow [enter]
Have your XP install cd handy.

2. If SFC doesn't work, try a Repair Install:
http://www.michaelstevenstech.com/XPrepairinstall.htm

Make sure your data is backed up first. You should be doing this
regularly anyway and usually there will be no problem with a Repair
Install, but better safe than sorry.

Malke