I have an Windows 2003 X64 SP2 DC that occasioanlly throws this event. I have been chasing it for quite sometime.
I have eliminated most of the things people often associate with this error. It passes DC Diag clean. There is no problem with DNS. What I have discovered recently is that it is in fact related to a terminal services session becoming/going inactive. (Without giving too much detail I have various debugging enabled and have been running netmon captures.)
However the RDP session is encrypted to it is difficult to actually determine exactly what is causing the error.
It is harmless but annoying. Has anybody tracked 1054 down to this cause, any ideas as what might
be happening? I know this error has been linked to various network errors as well, but I am reasonably
confident that it is not these as I would see some sort of error in the network captures.