Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 40 subscribers
  • Views 1514 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NTP issue

Phaser

Lost my time.windows.com ntp sync on clients.  Using SFOS 18.0.4 MR-4 on 86w box. Read all can find and tried a few rules recommended and no change.

Actually any other NTP time source address fails behind the firewall.  If I put these addresses in the xg ntp under administration they work just not from other clients. Any words of wisdom?



This thread was automatically locked due to age.
Parents Reply Children
  • +1 in reply to LHerzog

    Hello. they do not. And the logs on the rules I setup are always empty and firewall log shows nothing, administration etc. I noticed that NTP spec says out above ports 1024 but the ntp spec starts at port 1 to 65535. Seems so strange their NTP works fine with these sources but behind the box no. Will just have to work it. Had to use the IP and see it sent it to Microsoft but there is no return on the inbound rule.

  • +1 in reply to Phaser

    Hi,

    the inbound rule is only for traffic originating outside of your network. All traffic originating inside your network is shown against the initiating connection.

    NTP definition will be something like tcp/udp 1:65535 to 123

    Ian

    XG115W - v20 GA - Home

    XG on VM 8 - v20 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Thanks, certainly seems like it is working just that windows times out every time i try and use the sync button. Said not since 12/2 have had an successful sync.  Will keep thinking on solving it. 

Unfiltered HTML