server authenticating you reported an error (0XC00000BB)

[fox]

After the last Professional XP windows update proposed by Microsoft (friday 6
November), I can't connect my computer on the network. When I try to log, I
have this error "server authenticating you reported an error (0XC00000BB)".
To log on the network and ressources servers, I have to unplug the network
cable from my desktop. When I'm on the Microsoft office, I plug the cable and
all is ok.

I found anything to fix this case.

Thanks to help me.

 

[Amr Guenena]

I am facing the same problem with two of our client computers

 

[zybertop]

I got the same problem right now...anyone know the solution, there are about
10+ PCs having this problem.

 

[C-men]

Here also the same. Solution?

I got the same problem right now...anyone know the solution, there are about
10+ PCs having this problem.

 

[John John - MVP]

It might help if you guys tell us which updates you installed.
Uninstalling the offending update may fix things and serve as a
workaround until more is known about the problem. This is a Kerberos
error, one of the updates might have updated the kerberos.dll file which
in turn led to the error. Support for Security updates is always free
so you could try calling Microsoft @ 1 866-PCSAFETY and see what they
have to say about it.

John

 

[Jack P]

I'm also getting this error in conjunction with two other errors. Here's the
scenario:

When I attempt to logon to an XP domain PC, I get 'invalid access to memory
location.' When I try a second time, I get 'System could not log you on, the
server authenticating your computer reported error 0xC00000BB.' If I try to
logon locally after that, I get the same BB error. If I reboot and log on
locally first, it will let me logon. I have taken off domain and rejoined
and installed latest updates and still get nothing. My domain is a W2k3
server.

Thanks in advance.

 

[John John - MVP]

Something about the problem might be recorded in the Event Log. If,
like the others, you have only begun experiencing the problem after a
security update then identifying the update in question would (might) be
the first step in resolving the problem.

John

 

[Joao Silva]

I had the same issue and is was a Trojan virus , it was being load as a
multimedia driver , the registry key was:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"midi9"="C:\\WINDOWS\\stm.old 0yAAAAAAAA"


Stm.old is the virus file , 0yAAAAAAAA is same sort of parameter . To log
in i disconnected the network cable and logged in localy and resolved the
virus issue. Apparently this trojan was causing the kerberos to be disabled.

Hope it helps

Joao

 

[Ken Templin]

Thank you Joao. On the system I'm fixing, there was a trojan being loaded
under the same registry key, but the filename and its location was different.

Unfortunately, removing the trojan and registry key did not solve the login
problem (yet). still working on it...

I had the same issue and is was a Trojan virus , it was being load as a
multimedia driver , the registry key was:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"midi9"="C:\\WINDOWS\\stm.old 0yAAAAAAAA"


Stm.old is the virus file , 0yAAAAAAAA is same sort of parameter . To log
in i disconnected the network cable and logged in localy and resolved the
virus issue. Apparently this trojan was causing the kerberos to be disabled.

Hope it helps

Joao

Something about the problem might be recorded in the Event Log. If,
like the others, you have only begun experiencing the problem after a
security update then identifying the update in question would (might) be
the first step in resolving the problem.

John


.