Archived from groups: microsoft.public.win2000.advanced_server (
More info?)
Peter
Hi sorry for the later reply.
Okay Can we just review the situation here.
You had 1 domain with 1 domain controller as you have had some hardware
issues with it, so you recently added another and since then every 2 days
your getting a domain wide problem, that every client on the domain cannot
login. and they all report the same time error. is this correct ?
Now to clear the error you restart the newly promoted Domain Controller is
this correct, or are you restarting all of the domain controllers or the old
DC.
You say that you have now made the crippled DC the only dc in the domain and
the problem still exists is this also correct?
How did you achieve this did your demote the old domain controller or switch
it off ?
Did you have the problem before you added the new DC ?
I think that you now need to review the event logs on the Domain controller
/controllers and the clients and see what errors are reporting in the event
logs look in all of them to begin on both the DC's and at least 2 of the
affected clients they are bound to give you some clues.
You have a pattern forming so you just need to review the logs around the
time the problem occurs, if you look back you may find some information that
will help trace the cause of the problem.
Increase the size of all the logs if you don't have enough space to collect
at least 4 days worth of logs minimum to see if you can identify a pattern
(we keep at least 6 months work to review for trend analysis)
I would also think you will need to perform some tests such as running
DCDiag on the domain controllers, also check the dc promo log for any errors
from the promoting / demoting of the new DC. Also use Repmon to check your
AD replication, check to ensure all your FSMO roles are available and check
you have a working Global Catalog.
Ensure you have the support tools installed on the DC's also the Win2k
Server resource kit if you have it as these tools are a must.
If you need a help to identify any errors that are reported then just post
them back to the group for assistance.
rgds
Steve
<anonymous@discussions.microsoft.com> wrote in message
news:176e01c47c04$3e6bc4a0$a301280a@phx.gbl...
> the time is synchronized properly,
> i tried a lot of methods (NET TIME /SETSNTP: etc.)
> i tried to synchronoze server with external source
> i tried to not synchronize server with external source
> doesn't help
>
> it is the real problem, i cannot logon to any machine in
> my domain including the domain controller
> i recieve the same error
>
> i use the program called "poweroff" to restart my dc and
> then everything come to "ok state" but it is only a matter
> of time for it to get bad
>
>
>
>
> >-----Original Message-----
> >Peter
> >http://support.microsoft.com/?kbid=232386
> >is the error and KB article
> >
> >http://labmice.techtarget.com/windows2000/timesynch.htm
> >
> >resources on time sync
> >rgds
> >Steve
> >
> >"peter" <majcher@news.postalias> wrote in message
> >news:127b01c47bb1$2f6320f0$a301280a@phx.gbl...
> >> I installed win2k server on a new machine, ran dcpromo a
> >> made the computer an additional domain controller.
> >> there were no errors during that process
> >>
> >> the errors came later:
> >> i could not log on to the domain, the system
> >> gave me the message claiming that there are some
> >> time related problems (scrrenshot available here:
> >> http://www.wszim-sochaczew.edu.pl/piotrm/error.jpg)
> >>
> >> when i turned off that machine (so i had my old dc
> >> only) everything was ok
> >> when i restarted that machine everything was ok (for 2
> >> days. after that the situation occured again)
> >>
> >> i ensured that i have got synchronized time in my
> domain i
> >> checked the clients and they also have correct time
> >>
> >> i had a critical situation and i had to make
> >> "the crippled controller" the only controller
> >> in my domain. when i did so the situation now is as
> >> follows : everything is ok for about 48 hours after that
> >> no one can log on to a domain, when i restart dc the
> >> situation improves for 48 hours then the errors appear
> >> again.
> >>
> >> any ideas?
> >
> >
> >.
> >