Networks

Ask something
Discussion Locked

Cannot Log into Windows XP

0 helpful
2 replies

by captaintinfoil

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

When I try to log into my PC I get the following error:
"The system could not log you on. The server authentication you reported an error (0x00000BB). You can find further details in the event log. Please report this error to the system administrator."

The error results from any login attempt, both onto the domain and locally.

I am unable to access the system file share either (\\\c$). I get this message when I try:
?\\\c$ The specified server cannot perform the requested operation?

A similar message is shown when I try the FQDN or IP address.

When I try to remotely connect the Computer Management console, using MMC, I get this message:
?Computer cannot be managed. The network path was not found. Choose ?Connect to another computer? from the action menu to manage a different computer?

A similar message is shown when I try to connect using the NETBIOS name and the IP address.

Software Information:
Windows XP Pro SP2
Symantec Antivirus (9.0.5)
Internet Explorer 7

Hardware Information:
HP DX2400
Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
2 GB RAM

This PC is at allocation geographically separate from me, so I am waiting for the person who uses it to become available for further troubleshooting. My next test was going to be booting to Safe Mode and trying to log in. I do not think it will work, but if it does, I will run SFC or a virus scan.

Any other ideas???

2 replies

by captaintinfoil

It appears to be that the local Windows security files were corrupted and logging into Safe Mode allowed SFC to repair the damage. In any case the problem seems to be fixed for the time being.

by captaintinfoil

I had the user boot to Safe Mode and he was able to log in using the local administrator credentials.

I then had him boot to Safe Mode w/ Network Support and he was able to log in with his AD user account

I then had him boot to Normal mode and he was able to log in just fine.

It appears to be that the local Windows security files were corrupted and logging into Safe Mode allowed SFC to repair the damage. In any case the problem seems to be fixed for the time being.

This discussion is closed to new replies.