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

Additional Address on external interface of UTM stopped responding

Hello, hope you are well.

Today, a customer raised an incident that Outlook Web Access was not working. After investigating the problem, I found that the IP Address used for publishing the service was not responding.

This IP Address is an "Additional Address" of the external primary address on the Interface.

To resolve the problem, I had to switch off the "Additional Address" and then switch it back on.


No doubt I am going to by asked to contribute to an incident report and be requested to investigate what the root cause was. Since I have no alerts about the issue, where could I look for any clue about why it stopped working and also has anybody else had a similar problem.

Thanks in advance

Dave



This thread was automatically locked due to age.
Parents
  • Hi Dave,

    Had a similar problem yesterday.  In my case I added a new IP address to the external interface and assigned it to a virtual web server. The WAF stopped for about 10 minutes and then restarted. The UTM CPU went to 100% and all websites were unavailable externally. The following entry was in the WAF log referring to the IP address I added: 2016:09:21-14:55:02 utm-cpc-2 reverseproxy: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address.  I have opened a case with Sophos.

  • Hi David, hope you are well.

    Thanks for the info in your reply. I will do a search in the WAF log to see if I have any similar entries as yours.

    Regards,

    Dave

Reply Children
No Data