Time issues?

I am having a lot of problems on my network. A few days after the daylight
savings change, I started having trouble with clients having issues with
incorrect times, and some not able to hit their e-mail.

Then one of my application servers started having problems. First we had
errors saying that it couldn't locate a time server, and that it was out of
sync with the network. We worked on syncing the time, but now I am getting
frequent net logon errors (event id 5719) stating that no domain controllers
were available, and some user environment errors, which say that group
policy couldn't be applied.

I'm pretty sure that we did all of the DST patches back when the gov changed
the dates of the DST change. As soon as I get one server synced with the
network, another one starts having problems. I have a couple that I've
never been able to get fully logged in.

Anyone have any suggestions?

Thx,
SA

By any chance, have you decommissioned or redeployed a domain controller
somewhere on your network that could have been the original DC from the
past?

The first DC in a domain is made the (FSMO) PDC emulator. It is, basically,
the keeper of the time. If you removed this original box without manually
moving the PDC emulator role to another DC, this might account for various
time related issues.


"SA" <(E-Mail Removed)> wrote in message
news:Bhwwl.88677$(E-Mail Removed)...
> I am having a lot of problems on my network. A few days after the
daylight
> savings change, I started having trouble with clients having issues with
> incorrect times, and some not able to hit their e-mail.
>
> Then one of my application servers started having problems. First we had
> errors saying that it couldn't locate a time server, and that it was out
of
> sync with the network. We worked on syncing the time, but now I am
getting
> frequent net logon errors (event id 5719) stating that no domain
controllers
> were available, and some user environment errors, which say that group
> policy couldn't be applied.
>
> I'm pretty sure that we did all of the DST patches back when the gov
changed
> the dates of the DST change. As soon as I get one server synced with the
> network, another one starts having problems. I have a couple that I've
> never been able to get fully logged in.
>
> Anyone have any suggestions?
>
> Thx,
> SA
>
>

In news:Bhwwl.88677$(E-Mail Removed),
SA <(E-Mail Removed)>, posted the following:
> I am having a lot of problems on my network. A few days after the
> daylight savings change, I started having trouble with clients having
> issues with incorrect times, and some not able to hit their e-mail.
>
> Then one of my application servers started having problems. First we
> had errors saying that it couldn't locate a time server, and that it
> was out of sync with the network. We worked on syncing the time, but
> now I am getting frequent net logon errors (event id 5719) stating
> that no domain controllers were available, and some user environment
> errors, which say that group policy couldn't be applied.
>
> I'm pretty sure that we did all of the DST patches back when the gov
> changed the dates of the DST change. As soon as I get one server
> synced with the network, another one starts having problems. I have
> a couple that I've never been able to get fully logged in.
>
> Anyone have any suggestions?
>
> Thx,
> SA

In addition to SuperK's suggestions, I would recommend to go through your
servers one by one at this point, to determine their current time settings
and make sure they have the latest DST patch. If you have MOM, you can
create a report of installed hotfixes, as well as using something like
HFNET, or automate by script a query to all servers. But either way, it
appears there is a bit of inconsistency with time going on that needs to be
addressed. This also has to be done on ALL machines, laptops and desktops,
to insure that all have the updated DST patch and are up to date and
synched.

You can also script in a logon or computer startup script to manually synch
time with it's time source (by default, as SuperK mentioned, it is the PDC
emulator of a domain). But then again, if that client machine doesn't have
the DST fix, then the sync wouldn't work anyway.

Or you can just wait for the two weeks to pass, albeit with problems, until
the old Daylight Savings Time schedule gets caught up.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"SA" <(E-Mail Removed)> wrote in message
news:HUkHl.55345$(E-Mail Removed)...
>I have checked each server, and they are all patched. I'm using my pc as a
>test, and it has the dst patch applied. I can get the pc time to match the
>network time, but all of the appointments in the Outlook calendar are one
>hour behind. But our e-mail server is synced with the network time, and
>has the dst patches applied.
>
> Thanks

I think at this point, since the DST issue has passed us more than a month
ago, that the calendar appt times are all skewed at this point because the
patch was either not installed prior to the issue, or running TZMOVE caused
the issue by running it on all calendar items, where it wasn't required to
be run. At this point it will take a little time on how to reset them, or
possibly rerunning the TZMOVE utility.

Please take a look at these articles to see if they can better assist you.

Outlook 2003 Day Light Savings Patch making appointments 1 hour behind its
original time.
http://www.experts-exchange.com/Soft..._22434432.html

Meeting Requests and Appointments are off by one hour
http://www.slipstick.com/calendar/onehour.htm

How to address time zone changes by using the Time Zone Data Update Tool for
Microsoft Office Outlook
http://support.microsoft.com/kb/931667

Calendar appointments showing 1 hour later on recipients' calendar
appointments
http://blogs.technet.com/dst2007/arc...ointments.aspx

Ace

I have checked each server, and they are all patched. I'm using my pc as a
test, and it has the dst patch applied. I can get the pc time to match the
network time, but all of the appointments in the Outlook calendar are one
hour behind. But our e-mail server is synced with the network time, and has
the dst patches applied.

Thanks

"Ace Fekay [Microsoft Certified Trainer]" <(E-Mail Removed)>
wrote in message news:%(E-Mail Removed)...
> In news:Bhwwl.88677$(E-Mail Removed),
> SA <(E-Mail Removed)>, posted the following:
>> I am having a lot of problems on my network. A few days after the
>> daylight savings change, I started having trouble with clients having
>> issues with incorrect times, and some not able to hit their e-mail.
>>
>> Then one of my application servers started having problems. First we
>> had errors saying that it couldn't locate a time server, and that it
>> was out of sync with the network. We worked on syncing the time, but
>> now I am getting frequent net logon errors (event id 5719) stating
>> that no domain controllers were available, and some user environment
>> errors, which say that group policy couldn't be applied.
>>
>> I'm pretty sure that we did all of the DST patches back when the gov
>> changed the dates of the DST change. As soon as I get one server
>> synced with the network, another one starts having problems. I have
>> a couple that I've never been able to get fully logged in.
>>
>> Anyone have any suggestions?
>>
>> Thx,
>> SA
>
> In addition to SuperK's suggestions, I would recommend to go through your
> servers one by one at this point, to determine their current time settings
> and make sure they have the latest DST patch. If you have MOM, you can
> create a report of installed hotfixes, as well as using something like
> HFNET, or automate by script a query to all servers. But either way, it
> appears there is a bit of inconsistency with time going on that needs to
> be addressed. This also has to be done on ALL machines, laptops and
> desktops, to insure that all have the updated DST patch and are up to date
> and synched.
>
> You can also script in a logon or computer startup script to manually
> synch time with it's time source (by default, as SuperK mentioned, it is
> the PDC emulator of a domain). But then again, if that client machine
> doesn't have the DST fix, then the sync wouldn't work anyway.
>
> Or you can just wait for the two weeks to pass, albeit with problems,
> until the old Daylight Savings Time schedule gets caught up.
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> (E-Mail Removed)
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
>