Stumped!

January 28, 2008

Hi All,

Hope someone has seen this problem and has a solution. I have a

Windows 2003 SP1 member server of a Windows 2003 domain. Every few

days the server will stop accepting connections to shares, printers,

RDP attempts, etc. The clients will receive an error message similar

to "Access Denied". When this happens, I am able to log on at the

console. Hoever, I cannot hit the Internet. If I run Netdiag, all of

the domain type tests fail. Netdiag is normal when the problem is not

occurring.

In the Event Viewer is an event 5719 that contains the following text:

"This computer was not able to set up a secure session with a domain

controller in domain Domain_name 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."

There is plenty of disk space on the box. So I am assuming this error

is referring to memory. I've set the pagefile to 1.5 times physical

RAM (1048 MB), I know that's weak. I have another gig on the way, and

that may cure the problem. If not, I'm not sure what else it could

be. I've also installed the latest firmware and driver for the NIC

and reset the TCP/IP stack. I've seen some KB articles that mention

the error, but nothing really applies. One more thing, when I first

starting looking at this, I found the clock was 7 minutes off from the

DC. I thought that was it, but I wasn't so lucky.

Any ideas?

January 28, 2008

Re: Stumped!

>Hope someone has seen this problem and has a solution. I have a

>Windows 2003 SP1 member server of a Windows 2003 domain. Every few

>days the server will stop accepting connections to shares, printers,

>RDP attempts, etc. The clients will receive an error message similar

>to "Access Denied". When this happens, I am able to log on at the

>console. Hoever, I cannot hit the Internet. If I run Netdiag, all of

>the domain type tests fail. Netdiag is normal when the problem is not

>occurring.

>

>In the Event Viewer is an event 5719 that contains the following text:

>"This computer was not able to set up a secure session with a domain

>controller in domain Domain_name 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."

>

>There is plenty of disk space on the box. So I am assuming this error

>is referring to memory. I've set the pagefile to 1.5 times physical

>RAM (1048 MB), I know that's weak. I have another gig on the way, and

>that may cure the problem. If not, I'm not sure what else it could

>be. I've also installed the latest firmware and driver for the NIC

>and reset the TCP/IP stack. I've seen some KB articles that mention

>the error, but nothing really applies. One more thing, when I first

>starting looking at this, I found the clock was 7 minutes off from the

>DC. I thought that was it, but I wasn't so lucky.

>

>Any ideas?

How about installing SP2? 1GB isn't that bad for RAM spec if it's a

lighter duty server. I don't know of any issues with SP2 and RDP and

there are no Known Issues with SP2 in

http://support.microsoft.com/kb/945977 that would affect you. It could

be a memory leak of some sorts but those have been addressed with

hotfixes, esp. the Non-paged Pool memory exhaustion issue. Most other

issues in the KB have fixes as well. I'd say get the server up to

speed in terms of SP2 and go from there.

- Thee Chicago Wolf

January 28, 2008