User Sign in Error ' domain not available???

[Guest]

I fired up the system and all of a sudden when I try to log into my user
account I get the message "system cannot log you on now because the domain
<my domain name> is not available." I haven't added any new software, made
any changes to the system in weeks. I have updated spyware, virus protection,
etc. and don't think that's the problem.

I am able to get into the system by hitting F8 while it starts up & going in
under safe mode, signing in under Admin.

I tried changing the password to my account, didn't help any.

I thought I'd just delete the need for a user name but can't figure out how
to do it and I'm not sure that would solve the problem, might make it worse.

I ran a checkdisk in dos mode, says there's some errors but can't discover
what they might be.

I'm Windows XP Home, latest and greatest.

I was going to go back and install older check point but somehow that's been
turned off so I don't have an older version to go back to.

I tried re-installing Windows XP, but it bombs right at the end.

I don't need to sign in, had it on there when having a lot of company and
wanted to keep that computer secure from kids. I have two computers, they're
linked with Linksys, am on broadband cable for Internet connection.

Any suggestions?

 

[GhostWrtr]

I fired up the system and all of a sudden when I try to log into my user
account I get the message "system cannot log you on now because the domain
<my domain name> is not available." I haven't added any new software, made
any changes to the system in weeks. I have updated spyware, virus protection,
etc. and don't think that's the problem.

I am able to get into the system by hitting F8 while it starts up & going in
under safe mode, signing in under Admin.

I tried changing the password to my account, didn't help any.

I thought I'd just delete the need for a user name but can't figure out how
to do it and I'm not sure that would solve the problem, might make it worse.

I ran a checkdisk in dos mode, says there's some errors but can't discover
what they might be.

I'm Windows XP Home, latest and greatest.

I was going to go back and install older check point but somehow that's been
turned off so I don't have an older version to go back to.

I tried re-installing Windows XP, but it bombs right at the end.

I don't need to sign in, had it on there when having a lot of company and
wanted to keep that computer secure from kids. I have two computers, they're
linked with Linksys, am on broadband cable for Internet connection.

Any suggestions?

Is the domain accessible when you log on using your second computer?



< "Old age ain't for sissies" ;-) >

 

[Guest]

I'm able to use my second computer, but I've never truly networked them so I
could get into the files, etc. I have them networked for Internet connection.

The one that is giving me the error message when I log in IS the main
computer.

I am able to get on the Internet and this computer is working fine, no
problems (knock on wood ;-).

 

[Guest]

I have exactly the smae problem (except I can't even boot in safe mode - I
get the same login problem).

A tech. company have removed my hard drive, scanned for viruses, repaird my
Windows XP installation, all to no avail. This happened 8-31-6 (this
morning) and i'ts looking like a format and clean install.

Any help would be appreciated to avoid this!

 

[Patrick Keenan]

I have exactly the smae problem (except I can't even boot in safe mode - I
get the same login problem).

A tech. company have removed my hard drive, scanned for viruses, repaird
my
Windows XP installation, all to no avail. This happened 8-31-6 (this
morning) and i'ts looking like a format and clean install.

Any help would be appreciated to avoid this!

This seems to be due to expired or removed account credentials. It's kind
of an oddly-phrased error because with XP Home, you can't join a domain in
the first place.

This page describes a hotfix that may now be available as another update -
or not. You could contact MS as described in the article to see if you do
actually need the fix or if it's covered in another update; they should be
able to waive support charges for a specific problem like this requiring a
hotfix you can't get otherwise. You can probably speed the call by citing
the KB article ID (824302).

http://support.microsoft.com/kb/824302/

Repair installs may not fix this, but a format and clean install certainly
should as the credentials would necessarily be created during the clean
install.

HTH
-pk