Event Id 1053 on Windows Server 2003 SP2

[Lane]

After I reboot my server, everything is fine for about 3 days. After 3 days
it starts logging:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 11/11/2007
Time: 4:48:28 PM
User: NT AUTHORITY\SYSTEM
Computer: <server name>
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.

when that starts, I can't RDP into the server and if I try I get a pop-up
message stating "The system can not log you on due to the following error:
The RPC server is not avaiable." which causes the following event to be
logged in the System log:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 11/12/2007
Time: 1:51:17 PM
User: N/A
Computer: <server name>
Description:
This computer was not able to set up a secure session with a domain
controller in domain ACADEMIC due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your domain
administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.

Steps I've already taken to eliminate the problem:
Updated NIC drivers.
Deleted current DNS records and created new ones.
Hard set NIC speed to 100MB Full Duplex.
Turned of TOE on the NIC.
Changed out motherboard thinking it was a NIC hardware issue after Dell
support tried helping me.

The server is a Windows Server 2003 SP2 machine, firewall is turned off, no
special software loaded other than a language teaching software. The server
was running fine when we first put it into to production about 2 years ago
and then about a year later it start generating these errors.

Could there be any windows updates tide this issue? Any help would be
greatly appreciated.

[Meinolf Weber]

Hello Lane,

Please give some more info about the network. I assume it is a domain? Is
the server a domain controller or member? Please post an ipconfig /all from
DNS server and the one with the problem.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

[Lane]

The server is a member server.

I've verified the NIC settings are correct several times and that I'm
pointing to the correct DNS server.

[Meinolf Weber]

Hello Lane,

Is the machine multihomed? Please post an ipconfig /all from DNS server and

[jungblpe]

Don't want to hijack your post here, but I am experiencing the same issues as
Lane is. In my case I am running Windows Server 2003 SP2 in a VM, with two
nics. I, like Lane, feel the network settings are fine.

[Florian Frommherz [MVP]]

Howdie!

jungblpe schrieb:

> Don't want to hijack your post here, but I am experiencing the same issues as
> Lane is. In my case I am running Windows Server 2003 SP2 in a VM, with two
> nics. I, like Lane, feel the network settings are fine.

Running two network cards in a server/DC is called "multi homing" and is
known for causing some issues. Try to reconfigure the protocol binding
order of the two network cards so the internal DNS can be reached. Best
thing would be to - if possible - remove the second network card (if the
server you're talking about is a DC).

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.

[Meinolf Weber]

Hello jungblpe,

And if it is not the case like Florian wrote and helps you, post also an
ipconfig /all from the problem machine.

[jungblpe]

This is not a domain controller. I can post an ipconfig /all but I don't
think the net config is wrong. The problem happened again this morning and I
gathered some more statistics.

I ran a netdiag and two tests failed: get DC list and the trust
relationship. So it appears the secure channel between my server and the
domain is temporarily broke. I ran another test, nltest /sc_reset:domain. The
results came back with: I_NetLogonControl failed: Status = 8 0x8
ERROR_NOT_ENOUGH_MEMORY. I looked at the memory on the system and it appears
fine. Can anyone point me to another area to look. In the mean time I have
restarted this server, so the application is up and running for the users.

[jungblpe]

Found another posting with similar results of what I have been seeing:

http://blogs.technet.com/brad_rutkowski/archive/2007/08/16/domain-not-available-when-trying-to-ts-onto-a-windows-2003-server.aspx.

I am going to be monitoring my server for the handle count on a particular
process to see if this is what I am experiencing.