When I checked the Application log in the event viewer I was presented with the error:

Source: Active Server Pages
Event ID: 5
Level: Error

Error: File <url to upload.asp> <line number> Operation not Allowed.

The error indicated that there was an issue with the ASP configuration for the website hosting the application so I had a quick look at the ASP settings in the IIS Manager:

In the settings for ASP I noticed the following option:

Limits Properties --> Maximum Requesting Entity Body Limit

The default value for this property is 200000 bytes which is just under 0.2 megabytes. The file I was trying to upload was just over 3 megabytes so I needed to increase this value. I changed it to 10485760 bytes which is 10 megabytes. Upon retrying to upload the document through the ASP application I was successful. No restart of IIS was necessary.

As far as W32Time (the Windows time service) is concerned, at the topmost level within the domain is the domain controller on which the PDC Emulator Flexible Single Master Operation (FSMO) role resides. This can be configured to synchronize it's time with a reliable external time source. By default all other domain controllers internally synchronize their time with the PDC Emulator. Similarly all domain member client computers synchronize their time with the domain controller that authenticates them.

Configuring the domain controller where the PDC Emulator role resides should be the only computer in the domain that requires any manual intervention to have the precise time on all domain client computers.

To find out which server the PDC Emulator role resides on open the Active Directory Users and Computers (ADUC) snap-in. Then right click on your domain and select 'Operations Masters'. Browsing the PDC tab will show you where the PDC Emulator role currently resides.

On the domain controller where the PDC Emulator resides you can configure it to synchronize its time with an external source by using the following command:

net time /setsntp:<ip/dns>

Use the following example to set multiple external time sources to sync with:

net time /setsntp:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org"

You can also configure this manually by modifying the following registry key:

HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

NtpServer=<ip/dns>
Type=NT5DS change this to Type=NTP

After making the above changes restart the W32Time service by issuing the following commands at a command prompt:

net stop w32time
net start w32time

NOTE: If you don't configure the PDC Emulator to synchronize its time with an external source it will simply use its own (CMOS) clock. Doing so will occasionally cause an error to appear in the event log on the server that resembles the following:

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 12

Event description: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.

NOTE: If you experience a client with time synchronization problems ensure that it has the correct time zone set. If needed, the time service can be reset using the following commands:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync