2003 domain controller problems

We have a small domain with 2 DC's both running 2003 server SP1. One of
our DC is acting very strangely. I cannot open users and computers and
when I try to run DCdiag it comes back with LDAP search failed with
error 58, meaning that it cannot connect to AD. Upon running netdiag I
get this error:

DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to "our DC FQDN" (10.1.10.2).
[ERROR_OUTOFMEMORY]

Nothing much in system logs but application has this repeating every
few minutes and it started right around the time we started having the
problem:

Userenv error 1053:
Windows cannot determine the user or computer name. (Not enough storage
is available to complete this operation). Group Policy processing
aborted.

I have searched the groups thoroughly on these errors and have found
little. If I reboot the problem goes away but then comes back. So it
seems like some kind of memory leak, as the "out of memory" and "not
enough storage" are suggesting. We have not installed any security
patches for about 3 weeks.
Any advice on how to fix this would be greatly appreciated.

.

Relevant Pages

  • warning cannot call DSBind error_outofmemory
    ... I cannot open users and computers and ... Group Policy processing ... seems like some kind of memory leak, as the "out of memory" and "not ...
    (microsoft.public.windows.server.active_directory)
  • Re: USERENV errors 1058 on all clients since installation of SCE
    ... MCSE, MVP Directory Services ... clients on my domain (single domain, simple switched network). ... Center Essentials All Computers Policy" the other policies don't seem to ... usually have to be resolved before Group Policy processing can continue. ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 domain controller problems
    ... our DC is acting very strangely. ... I cannot open users and computers and ... when I try to run DCdiag it comes back with LDAP search failed with ...
    (microsoft.public.windows.server.general)
  • Re: .Net is more memory safe?
    ... > memory leak. ... Yes, it is a memory waste, in your definition. ... "Not even computers will replace committees, ...
    (borland.public.delphi.non-technical)
Loading