Guest User!

You are not Sophos Staff.

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

WebAdmin fails after addition of second public IP address

I have had a Sophos UTM running in my home office for some time now with a fixed IP address on the WAN/public side. I recently decided to enable a second ISP supplied dynamic IP to my firewall so that I could host a few more family services.

The setup originally was the following:

WAN1 - Public_1 fixed IP

LAN - internal IP set (192.168.x.x)

All was working fine. I could log on remotely to the user portal and the WebAdmin interface at my Public_1 from anywhere while traveling

Updated setup:

WAN1 - Public_1 fixed IP (no change)

WAN2 - ISP provided DHCP address

LAN - no change

I can no longer log onto the WebAdmin from any external IP location.

The problem occurred immediately and when I remove the second WAN connection, I still can no longer access the WebAdmin interface.

Any suggestions?



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

    I suspect that the Web Admin access port is changed. Are you able to ping the UTM on static IP? If you are able to take SSH to UTM with root privileges, run the command "/etc/init.d/httpd restart", this will restart httpd services which is responsible for WebAdmin GUI.

    Thanks

  • The problem seems to be a little more complex than that. I had rebooted the system in case any services had stopped.

    From the internal network (192.168.x.x), I am able to access the WebAdmin and all of it's functions using the internal IP AND the WAN_1 external IP. So routing within the Sophos region is working. I am also able to access the internet without any problems.

    I can even access my personal server from the internet when I am not on my internal network. It seems only the WebAdmin access from an external source is the problem.

    It has stumped me because I do not recall making any changes to routing that would affect port 4444.


    BTW, I can still access the User Portal ... go figure!

Reply
  • The problem seems to be a little more complex than that. I had rebooted the system in case any services had stopped.

    From the internal network (192.168.x.x), I am able to access the WebAdmin and all of it's functions using the internal IP AND the WAN_1 external IP. So routing within the Sophos region is working. I am also able to access the internet without any problems.

    I can even access my personal server from the internet when I am not on my internal network. It seems only the WebAdmin access from an external source is the problem.

    It has stumped me because I do not recall making any changes to routing that would affect port 4444.


    BTW, I can still access the User Portal ... go figure!

Children