mmorgensen
MIS
We are having problems with two of our intranet servers. Both server have been loosing communication with the windows 2000 domain controllers over the past few weeks, but we can not pin point the issue.
Here is a summary of what we know.
Event Logs:
NETLOGON error at 8:51pm PST: “No Windows NT or Windows 2000 Domain Controller is available for domain XXXX. The following error occurred: Not enough storage is available to process this command.”
To fix the problem we restart the IIS service, and Bang! Everything is back to working.
The intranet site is running in a 'low' application protection mode.
My question is this...How is IIS causing a loss of DC communication?
Here is something from our IS group about the ASP app running on the intranet site.
====
RE: Changing from Low App. Mode to Medium / High.
High would be difficult there since several classic ASP pieces of functionality that will limit us to Medium (some separate apps do run in High now). Even Medium will run IIS separately, so that should get us what we need from the standpoint of this issue.
-Unfortunately, Application impersonation for classic ASP “requires” running in Low, so the best we can do is segment the application requiring that to JUST that application.
====
Help!
mm
Here is a summary of what we know.
Event Logs:
NETLOGON error at 8:51pm PST: “No Windows NT or Windows 2000 Domain Controller is available for domain XXXX. The following error occurred: Not enough storage is available to process this command.”
To fix the problem we restart the IIS service, and Bang! Everything is back to working.
The intranet site is running in a 'low' application protection mode.
My question is this...How is IIS causing a loss of DC communication?
Here is something from our IS group about the ASP app running on the intranet site.
====
RE: Changing from Low App. Mode to Medium / High.
High would be difficult there since several classic ASP pieces of functionality that will limit us to Medium (some separate apps do run in High now). Even Medium will run IIS separately, so that should get us what we need from the standpoint of this issue.
-Unfortunately, Application impersonation for classic ASP “requires” running in Low, so the best we can do is segment the application requiring that to JUST that application.
====
Help!
mm
