« May 2004 | Main | July 2004 »

06/30/2004

More W32Time Errors

Error ID 12 was happening to my Windows 2000 Web Servers, so I had to reconfigure a time source. The previous time source - A Cisco Catalyst Switch was replaced, messing up my time sync. So here is what you do to get rid of that error.

1) Set a chain of SNTP servers to synchronize with via “net time /setsntp: servername”. You can get a list of local servers to synchronize to from the link below.
2) Run the command “w32tm /config /syncfromflags:MANUAL /reliable:YES /update”. This directs Windows to think that the time is reliable on the local server. The only way to get it reliable is to synchronize with the servers as in step 1.

W32Time Errors on your Windows 2003 Domain Controllers

Recently I have been recieving W32Time errors with Event ID 50. Tried setting the net time a couple times but that was pointless. Then i noticed there was a patch available for this particular error. I went ahead, called up Microsoft, and they issues the patch time me immediately. It worked ..got rid of all my W32Time errors.

If you like a copy of this patch ( UNTESTED!! ) please feel free to email me and I will have it available to you.

06/16/2004

Akamai blames 'global DNS attack' for disruptions

There as been alot of dispute the last day or so as to what caused the outage of several sites and search engines. Here is the updated scoop from COMPUTERWORLD

06/01/2004

Applying Service Pack 1 to your Exchange 2003 Cluster

Evan gives an insight on one possible way to apply Service Pack 1 for Exchange 2003 Cluster. I've seen it done differently as well, and will post my experiences when I do the same this week.

HOTFIX AND PATCHES

IM me

Sponsors

Search

  • Google

My Online Status

Sponsor

.