Lately I'm getting errors in the eventlog of the Directory Service. The
message suggested to run DCDIAG. I did and the result was that the service
ISMSERV stopped on both the PDC and the BDC.
What does this mean and how can I correct this? I could not find any answers
I could understand.
Our system is (was) running smoothly for over a year now.
1 SBS 2003 SP1 server, 1 Windows 2003 member server as a BDC, 15 clients XP
Pro SP2
Many thanks in advance.
Dieter
--
Had ik maar naar m'n moeder geluisterd, dan had ik een echt vak geleerd.
Any other errors in the event logs?
Is the time sync between servers (and clients) working perfectly?
Did you run netdiag, too?
>
> Our system is (was) running smoothly for over a year now.
>
> 1 SBS 2003 SP1 server, 1 Windows 2003 member server as a BDC,
Minor terminology correction - it can be a member server, or it can be a DC,
but not both (and there's no such thing as a PDC/BDC in Active Directory;
all DCs are peers).
I have no connected errors AFAIK
The timesync is working like it should
I ran Netdiag on both the SBS server as on the DC
After running NETDIAG /DEBUG everything passed, no failures
DcDiag still fails on IsmServ. Is there anything else I should try?
Thanks for your time
Dieter
"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:%234$QcuzMH...@TK2MSFTNGP02.phx.gbl...
For some reason the error msgs do not show up again in the eventlogs. When I
run DCDIAG IsmServ still fails. Should I wait for something serious to
happen or is this a minor hickup?
Working for a 24/7 business, I'm the guy who get called out of bed when
something happens. I 'd rather prevent that.
Lanwench, please shed some light on this.
Thanks in advance
Dieter
"Dieter Visser" <k...@nospam.nl> wrote in message
news:%23a%232Xu8M...@TK2MSFTNGP06.phx.gbl...