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

Firewall not shown in ZTNA - Gateways

Hi all,

I've used ZTNA with FW as gateway for one year.
After a license-issue, i am able to activate the 3 free licences and are able to reach central-ZTNA-configuration again.
My old config is there, but my current/active firewall is no longer available as "gateway". I see there only an intermediate test-firewall.
Ideas or hints?


THX Dirk



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

    If I understand correctly, you had deployed a firewall as a ZTNA gateway previously. Now after activating this evaluation, you see your older gateway config but the previously chosen firewall serial number is not present in the gateway config? OR, are you unable to create a new gateway with a firewall? 

  • I see my older gateway config, but the previously chosen firewall serial number is not present in the gateway config. If i create a new gateway from type "firewall" it is the same. Only the "other" firewall-serial number ...


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • Hi Dirk,

    Is the firewall managed by firewall, not just registered? You can check the status on the Firewall management page. 

    If yes, would it be possible to delete the older stale entry and add a new firewall gateway? 

  • I had to completely remove the firewalls from central.
    After adding the firewalls again, i am able to use these firewall as ZTNA gateway again. :-(


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • Hi Dirk, Thanks for letting us know and glad its working now. We'll look into the reason behind this behaviour from our backend.