Time sync - Port 123, 13

[SlowJet]

Hi,

Some have noticed that the time sync is falling after SP2.

I have tightened up my 3rd party firewall and in doing I looked up soom
programs and what ports they needed.

For the time it says that it tries port 123 and if no go it tries port 13
(which is the main clock in Bolder, CO?)

I have these ports set in and out on My FW. The WFW should let it out by
opening the port and waiting for the response.

It still doesn't work, so I am wondering if it is a time out problem and the
WFW closes the port?

I see on the ICMP A check box for
"Allow incoming timestamp request"
Is that the clock?
And another check box,
"Allow outgoing time exceeded"
Is the the time out problem?

????
Now give me a real answer not a new clock program, ok.

SJ

 

[Jon]

The application "svchost.exe" (Generic Host Process for Win32 Services)
needs access to 207.46.130.100 ( = time.windows.com), using UDP Port 123

Jon

 

[SlowJet]

Tanks, Jon,

The MS KDB article didn't say UDP.

I will try that but there is still the question(s) of what was causing the
time sync to fail after SP2 in the first place when these ports would be
open on most computers.
My only guess is a time out from the WFW and the port is closed.
Got me?

SJ