[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 530
  • Last Modified:

Windows 2008 Time-Service Hiccups

We've had a Windows 2008 (x64) Server running as a Terminal Server for several months now without a problem.  Last night I installed some Windows Updates and now our users are being periodically disconnected throughout the day.  I looked through the Event Viewer but found nothing out of the ordinary.  I setup a ping to that server and let it run for a while.  Eventually I got a handful of missed packets before it all went back to normal.  I checked the System Event Log and at the exact time my pings dropped I got EventID 37 which looked something like this.

The time provider NtpClient is currently receiving valid time data from xxxx.xxxxxx.xxx (ntp.d|>

This really didn't sound like a problem but I went ahead and filtered the System Log for this particular event.  What I found was interesting.  Before I installed the Windows Updates, this event came up once every few days.  Sometimes, however, it would go weeks or even a month be occurrences.  Since the update, this message gets logged every hour.

I've already tried rebooting the server but that didn't help.  No hardware changes have been made.  I'm going to see about rolling back the recent updates.  We also have another similar server that's running SQL 2008 that I haven't checked yet.  Any ideas on what is causing this?
1 Solution

If the Windows Updates indicate this was caused, contact Microsoft PSS. If it is the updates which have caused this, they will resolve the issue for free. Remember that it ultimately depends on the updates as to whether they have rollback ability.

This is also common if you have any of the Symantec AV products installed. What Anti-Virus do you use? If it is Symantec (particularly SEP) contact Symantec and ask for the CleanWipe tool to remove it. Their AVs wreak havoc with Server 2008 and you need to use a different product, which would be a good move in any event.

Also, disable all the 'Checksum Offload' features on the NIC card.

I'd do each step one at a time, so you can be sure exactly what is causing it (or if it's a multitude of things).

ghfllcAuthor Commented:
In a previous Windows Update several weeks ago, both of our Windows 2008 Servers lost their Local Area Connection and were replaced with Local Area Connection #1.  This meant the static IP was replaced with a DHCP setup.  The updates mentioned in my question ended up reversing this process.  The Local Area Connection #1 disappeared and the Local Area Connection came back.  This meant another switch from static IP to DHCP.  Once I put the static IPs back in place, everything worked fine again.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now