Welcome, Guest. Please login or register.
September 06, 2008, 04:52:51 PM

Login with username, password and session length

189131 Posts
22039 Topics
52852 Members

Latest Member: maden

Search:     Advanced search | Tag Cloud
+  Welcome to the Comodo Forum
|-+  Desktop Security Products
| |-+  Comodo Firewall
| | |-+  Help for v2
| | | |-+  Elusive Windows Time Synchronisation
« previous next »
Pages: 1 [2] 3 Go Down Print
Author Topic: Elusive Windows Time Synchronisation  (Read 5078 times)
Soyabeaner
Global Moderator
Comodo's Hero
*****
Online Online

Posts: 7018



« Reply #15 on: April 01, 2007, 02:41:55 PM »

Easy enough to confirm.  Just disable proxy and see what happens.
Logged
gibran
Forum Member
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 3447


Sometimes words are meaningless indeed...


« Reply #16 on: April 01, 2007, 03:28:15 PM »

I'm puzzled... Huh

w32time service does work with .gov time server or not?

Look at this list of pooled severs
My reccomendation is to run a traceroute to find the server nearest to you.
« Last Edit: April 01, 2007, 03:42:10 PM by gibran » Logged

jasper2408
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 651


« Reply #17 on: April 01, 2007, 07:56:54 PM »

You might try making a rule to:

ALLOW UDP 123 OUT to time.windows.com

This is what I use and I never have any trouble

jasper
Logged

CFP 3.0.22.327beta  CMF   Avast Pro  SAS Pro Sandboxie Win XP PRO SP2 (x32)
ocky
Comodo Loves me
****
Offline Offline

Posts: 110



« Reply #18 on: April 02, 2007, 03:12:21 AM »

Have tried the works and now giving up. Too many computer reboots shorten life of HDD   Wink  Grin

Am quite OK using time-a.nist.gov or one of the other servers per my Query App. screenshot posted before. They all use port 123.
time.windows.com is the only one I can't get (same on wife's laptop), even with localhost Proxomitron disabled. Maybe it's one or other security setting .. but it did not occur before when running Sygate. 
Logged
Soyabeaner
Global Moderator
Comodo's Hero
*****
Online Online

Posts: 7018



« Reply #19 on: April 02, 2007, 05:19:47 AM »

« Last Edit: April 02, 2007, 05:42:56 PM by Soya » Logged
ocky
Comodo Loves me
****
Offline Offline

Posts: 110



« Reply #20 on: April 03, 2007, 08:19:16 AM »

Soya, I didn't recognise your post - new avatar again.
You see what I don't understand is that time.windows.com (default) uses the same ports (UDP 123) for in/out as the other time servers, like the one I have now time-a.nist.gov.
There are no probs. with any of the others and no rules are necessary in App. Mon. yet they use the same ports and protocol. Only time.windows.com and the other default time.nist.gov don't work; always "error connecting.." Please see screenshot to prove that the other time servers work.

Logged
jasper2408
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 651


« Reply #21 on: April 03, 2007, 10:08:04 AM »

You might try making a rule to:

ALLOW UDP 123 OUT to time.windows.com

This is what I use and I never have any trouble

jasper

I just checked my rule and I had to make the source and destination ports both 123 in my rule. "Any" for the source port should work but for some reason I used port 123 as the source. Evidently I had to use source port 123 to get it to work. You might try that to see if it makes a difference.

jasper
Logged

CFP 3.0.22.327beta  CMF   Avast Pro  SAS Pro Sandboxie Win XP PRO SP2 (x32)
Soyabeaner
Global Moderator
Comodo's Hero
*****
Online Online

Posts: 7018



« Reply #22 on: April 03, 2007, 10:18:24 AM »

set the security level to Allow All and then see if it works.  If it does then we know it's a rules problem.

  • It's not a problem with rules if the 'Allow All' didn't work...
Logged
gibran
Forum Member
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 3447


Sometimes words are meaningless indeed...


« Reply #23 on: April 03, 2007, 01:57:08 PM »

Well for time sincronization is better to use servers with a low latency.

I'would like see a list of time server not working for you and the result pinging them (a tracert would be a nice addition to, only the number of hops)
Logged

ocky
Comodo Loves me
****
Offline Offline

Posts: 110



« Reply #24 on: April 04, 2007, 02:30:09 AM »

(a tracert would be a nice addition to, only the number of hops)
OK - no wonder the default time.windows.com does not synchronise. After the 10th hop the errors start. Also cannot be pinged. So the server* is down - I just wonder how all the other posters can possibly successfully synchronise given the trace and ping results. I also know now that no rules at all have to be made to allow UDP 123 In/Out (see my screenshot in previous post). See trace below:

Trying to Trace time.windows.com
-------------------------
  1    0 ms    0 ms    0 ms    192.168.XXX.XXX
  2    27 ms    27 ms    28 ms    dsl-XXXX.telkomadsl.co.za [XXXX]
  3    28 ms    28 ms    28 ms    wblv-ip-er-1-fe-11-1-0-1.telkom-ipnet.co.za [XXXX]
  4    27 ms    27 ms    27 ms    wblv-ip-er-1-fe-11-1-0-1.telkom-ipnet.co.za [XXXX]
  5    296 ms    297 ms    298 ms    lon-ip-dir-telecity-pos-6-0.telkom-ipnet.co.za [XXXX]
  6    342 ms    343 ms    344 ms    213.228.228.214
  7    343 ms    343 ms    343 ms    ge-6-3-0-55.sjc-64cb-1b.ntwk.msn.net [207.46.37.197]
  8    400 ms    419 ms    446 ms    pos6-1.tuk-76cb-1b.ntwk.msn.net [207.46.34.170]
  9    360 ms    360 ms    361 ms    ten2-1.tuk-76c-1a.ntwk.msn.net [207.46.36.197]
  10    366 ms    367 ms    369 ms    po16.tuk-65ns-mcs-1b.ntwk.msn.net [207.46.35.142]
  11    *    *    *    Error:11010
  12    *    *    *    Error:11010
  13    *    *    *    Error:11010
  14    *    *    *    Error:11010
  15    *    *    *    Error:11010
  16    *    *    *    Error:11010
  17    *    *    *    Error:11010
  18    *    *    *    Error:11010
  19    *    *    *    Error:11010
  20    *    *    *    Error:11010
Trace complete.



Trying to resolve time.windows.com  - done!
-------------------------
Host Name: time.windows.com
IP Address: 207.46.232.182

* I mean one of the servers en route from here.

Regards.
« Last Edit: April 04, 2007, 05:55:59 AM by ocky » Logged
gibran
Forum Member
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 3447


Sometimes words are meaningless indeed...


« Reply #25 on: April 04, 2007, 07:56:54 AM »

A strange error indeed...

Error 11010 WSA_QOS_ADMISSION_FAILURE
Error due to lack of resources. Insufficient resources were available to satisfy the QOS bandwidth request.

Just to satisfy my curiosity would you like to do the tracert again and report only related blocked icmp in the log if any?
Try this also ping -i 11 time.windows.com and copy&paste the error messege.

Then you can get rid of those time servers using adequate low-latency ones

Choose from the Stratum-2 Server lst but please note that the list does not indicate any of the servers to be public access servers get the correct one by trial-and-error and choose the low latency ones.

To change default windows time server refer to this Microsoft page titled  "Microsoft Windows XP - Change the clock synchronization server"
« Last Edit: April 04, 2007, 08:28:00 AM by gibran » Logged

ocky
Comodo Loves me
****
Offline Offline

Posts: 110



« Reply #26 on: April 04, 2007, 09:03:09 AM »

bandwidth request.

Just to satisfy my curiosity would you like to do the tracert again and report only related blocked icmp in the log if any?
Try this also ping -i 11 time.windows.com and copy&paste the error messege.

Then you can get rid of those time servers using adequate low-latency ones

Choose from the Stratum-2 Server lst but please note that the list does not indicate any of the servers to be public access servers get the correct one by trial-and-error and choose the low latency ones.

The ping produces request timed out. ICMP Trace :-

ICMP Traceroute to 207.46.232.182 (time.windows.com)

Hop 01:    192.168.xx.xx   [Unknown]
Hop 02:   XXxxx.XXX       dsl-XXXX.telkomadsl.co.za
Hop 03:    196.43.10.138     wblv-ip-er-1-fe-11-1-0-1.telkom-ipnet.co.za
Hop 04:    196.43.10.138     [Unknown]
Hop 05:    196.43.18.94      lon-ip-dir-telecity-pos-6-0.telkom-ipnet.co.za
Hop 06:    213.228.228.214   [Unknown]
Hop 07:    207.46.37.173     ge-6-3-0-54.sjc-64cb-1a.ntwk.msn.net
Hop 08:    207.46.34.162     pos4-1.tuk-76cb-1a.ntwk.msn.net
Hop 09:    207.46.35.65      ten1-1.tuk-76c-1a.ntwk.msn.net
Hop 10:    207.46.35.134     po14.tuk-65ns-mcs-1a.ntwk.msn.net
Hop 11:    ---
Hop 12:    ---
Snipped  - nothing up to hop 30

As mentioned in my post on page 1, I already use time-a.nist.gov   It's S2, and works pefectly. Thanks for your tip on changing it .
Logged
Pedro*
Comodo's Hero
*****
Offline Offline

Posts: 785


« Reply #27 on: April 04, 2007, 09:08:31 AM »

I don't use this, but for curiosity, i tried it and
Sometimes the win32time service complain about a rpc error is this the case?
yes, i get RPC server is not available Huh
(what did i disable...lol)
Logged
bluesjunior
Comodo Loves me
****
Offline Offline

Posts: 135


« Reply #28 on: April 04, 2007, 09:57:37 AM »

Have read through this whole thread as I found out I have the same problem. Tried both servers and got errors both times. Not being very PC technical I am not sure how to use a different server as mentioned. What exactly is Internet Time Synchronization anyway?. Do I need it, and what would be the consequences if I just switched it off as mentioned in the Windows helpline page?.
Logged
Soyabeaner
Global Moderator
Comodo's Hero
*****
Online Online

Posts: 7018



« Reply #29 on: April 04, 2007, 10:09:35 AM »

Internet Time Synchronization is to ensure that your PC's time at the bottom right corner of your system tray is up-to-date with the internet's time server, which is supposedly the most accurate.  I notice that my PC's time is faster if left on its own after a few weeks.  You don't need it if you don't mind manually changing the time every once in a while.
Logged
Tags:
Pages: 1 [2] 3 Go Up Print 
« previous next »
Jump to:  

SSL Firewall
Page created in 0.372 seconds with 19 queries.
Powered by SMF 1.1.5 | SMF © 2006, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks
Design by 7dana.com