R
Rico
I have a win2k server running AD. It is a DC running DNS,
DHCP and is a print server. Two weeks ago an issue
surfaced with the symptom of no one was able to print.
after rebooting, the problem was gone. the next day, the
same thing happened, and every day since. Another symptom
was that DNS on this server did not seem to be working,
what I mean by that is that there was no internet
connectivity, but the computers that used that as the DNS
server did not have that problem. Today I went into AD
sites and services, and received the error message
that "this server is not operational" and the AD sites
and services icon was x'd out in red. I rebooted the
server and AD sites and services was back to normal,
until tomorrow. Any ideas or solutions would be greatly
appreciated.
I have all of the patches installed. The only error
message that shows up in event veiwer that corresponds to
the time of problem is Userenv ID 1000 "windows could not
contact the domain "domainname". Netdiag passed, but
dcdiag failed to run, because AD is not functioning. This
just occurred and I rebooted and AD Sites and Services is
up and running again. Could it be a hardware failure?
There is only one domain. I have a second DC for
failover. I installed SP4 one week ago hoping that would
help, but it did not. Thanks for the input.
DHCP and is a print server. Two weeks ago an issue
surfaced with the symptom of no one was able to print.
after rebooting, the problem was gone. the next day, the
same thing happened, and every day since. Another symptom
was that DNS on this server did not seem to be working,
what I mean by that is that there was no internet
connectivity, but the computers that used that as the DNS
server did not have that problem. Today I went into AD
sites and services, and received the error message
that "this server is not operational" and the AD sites
and services icon was x'd out in red. I rebooted the
server and AD sites and services was back to normal,
until tomorrow. Any ideas or solutions would be greatly
appreciated.
I have all of the patches installed. The only error
message that shows up in event veiwer that corresponds to
the time of problem is Userenv ID 1000 "windows could not
contact the domain "domainname". Netdiag passed, but
dcdiag failed to run, because AD is not functioning. This
just occurred and I rebooted and AD Sites and Services is
up and running again. Could it be a hardware failure?
There is only one domain. I have a second DC for
failover. I installed SP4 one week ago hoping that would
help, but it did not. Thanks for the input.