Our Windows 2003 Server refused to sync the clock via NTP. Main reason for this behaviour is the fact that as PDC it wants to change the NTP server’s clock as well, which is normally not permitted by the NTP server and the packet is discarded.
To change the preferred server of the Windows Time service (w32time), follow these steps:
w32tm /config /manualpeerlist:<server>,0x8 /syncfromflags:MANUAL
w32tm /config /update
net time /querysntp
(source: Meinberg Funkuhren – FAQ – Windows synchronisiert nicht mit NTP (German))
If you are using Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) you are supposed to decide if you are going to use “integrated windows authentification” only or if you are using “mixed mode authetication”. Latter is sometimes considered less secure but if you are developing ASP.NET applications it can be easier to use a non-NT user for the connection.
If you ever tried that you are surly familiar with the “login is not associated with a trusted connection” exception when trying to access the database. Today I had to install an ASP.NET application on a server with MSDE where mixed mode authentication was not available. A quick research on the net revieled a blog entry indicating how to change the authentication scheme of MSDE after the installation.
Unlike a comment on the page, value 0 will not work (at least it didn’t in my case).