Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 4 subscribers
  • Views 7641 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

How to configure Sophos UTM 9 running in AWS to connect to internal (VPC) NTP server?

OmnerBarajas

Hello,

I have been trying to connect Sophos UTM 9 to a local NTP server inside VPC but interface keep showing failed status.

All other servers inside VPC are able to reach and connect the local NTP but Sophos.

Is there a special configuration that I need to complete in order to have the system update its clock from my server?

Thanks



This thread was automatically locked due to age.
  • 0

    Hi, Omner, and welcome to the UTM Community!

    What do you have configured in 'Network Services >> NTP'?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hi,

    I have a local NTP server. Status in web interface keep saying failed but when I log in to the system using ssh I can see the service is actually connecting and responding correctly.

    So I assume is a matter with the web interface that you probably want to remediate.

  • 0 in reply to OmnerBarajas

    Please insert a picture of the NTP configuration in your UTM.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0

    Hi Omner,

    Do you have a separate subnet for the UTM compared to the other servers? If so do you have ports TCP/UDP 123 open in your security group(s)?

    Regards,

    Peter

  • 0 in reply to PeterGordon

    Yes, it is in a separate subnet.Network access and security groups are open as needed.

     As I said above, system is able to connect. If I log in to the system using ssh I can see the system connected to my private-ip NTP server. 

    The problem is in the web interface that keep sending failed status.

    Note. I didn't make configuration changes in server cli. Same configuration in web worked correctly in the system so looks like the problem is the web interface not being able to catch response correctly.

Unfiltered HTML