Windows 2003 Server Time Sync Issues

I have an ISA server but the rule is enablded for the ports udp and tcp port 123.  
Here is one of the events  on one fo the servers:EventID:50
The time service detected a time difference of greater than 128 milliseconds  for 90 seconds. The time difference might be caused by synchronization with  low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update  the system clock. When a valid time stamp is received from a time service  provider, the time service will correct itself.  

You can also use PortQry that will tell you the exact reason - if its being blocked by a firewall or an application.

Check out here:

http://support.microsoft.com/kb/832919

Let us know.

Here are todays new logs.  Just a side note:  
Event ID:12
The NTP server %1 isn't sync'd, time not set
Event ID:11
The NTP server \\fs2.ppct.world didn't respond

How can I configure the PDC to not sync with it self so I can avoid the message below:

When the PDC master runs without using an external time source, the following event is logged in the Application log:

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. It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

Check out here:

How to configure an Authoritative Time server in Windows 2000:

http://support.microsoft.com/kb/q216734/

Im using windows 2003 server standard,  The article that I am refering to is:
http://support.microsoft.com/kb/816042

I notice that on step 4:  I did not see the option for NtpServer in the registry, so i crated that value and entered the two times servers that I want to synchronize to. How can I test to see if the time server is working?  I decided to not use my Primary DC as a time server and use an external time server.

timeserver.cs.umb.edu,0x1
bonehed.lcs.mit.edu,0x1
ntp.usno.navy.mil,0x1  

4. Specify the time sources. To do this, follow these steps:a.  Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer
b.  In the right pane, right-click NtpServer, and then click Modify.
c.  In Edit Value, type Peers in the Value data box, and then click OK.

Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique. You must append ,0x1 to the end of each DNS name. If you do not append ,0x1 to the end of each DNS name, the changes made in step 5 will not take effect.
 

I already configurded the server for time syncronization and it keeps throwing the same darn message. What do I do???????????

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.  It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source.  Otherwise, this machine will  function as the authoritative time source in the domain hierarchy.  If an external  time source is not configured or used for this computer, you may choose to disable  the NtpClient.