A
AQ
Has anyone had a Sylmar problem?
127.0.0.1 Session by "server name"$ on Windows 2000 SP3
domain controllers will cause server to stop responding to
log-on and print requests.
Event frequency varies from several times a day to once a
week. Task Manager shows less then 3% CPU utilization,
and ample free memory.
Closing 127.0.0.1 session temporary fixes problem, however
the problem always comes back.
Event log application error place from event as follows:
Event ID: 1000
Source Userenv
Category: None
Description:
Windows cannot obtain the domain controller name for your
computer network. Return value (2146)
Ran Dcdiag /v and found no errors or failures, also
checked replication using replmon all seems to be
working.
127.0.0.1 Session by "server name"$ on Windows 2000 SP3
domain controllers will cause server to stop responding to
log-on and print requests.
Event frequency varies from several times a day to once a
week. Task Manager shows less then 3% CPU utilization,
and ample free memory.
Closing 127.0.0.1 session temporary fixes problem, however
the problem always comes back.
Event log application error place from event as follows:
Event ID: 1000
Source Userenv
Category: None
Description:
Windows cannot obtain the domain controller name for your
computer network. Return value (2146)
Ran Dcdiag /v and found no errors or failures, also
checked replication using replmon all seems to be
working.