Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 38 subscribers
  • Views 1247 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

SD RED NOT CONNECTED ANYMORE CASE ID : 06123090

Ste cospharma

HI , 

CASE ID : 06123090

 i've recently set up a new temporary schema for my network , where i added a new FIREWALL 2  to an existing LAN with FIREWALL 1 . ( no configuration were made on the FIREWALL 2 , only LAN 1 wich i'e configured it so the firewall can be apart of distant LAN ( 192.168.1.0/24)

Before this schema the red and VPN were working fine , here's the new shema with ip addresses configured .

Can you help me understand why after adding a second FW  to lan the red and vpn stopped working 



This thread was automatically locked due to age.
  • 0

    Hello there,

    Thank you for contacting the Sophos Community.

    For this type of scenario, your Sales Engineer or PS is the best team to reach out to; Support is usually for working no-working scenarios where no changes in the physical network were made. 

    I believe it might be due to overlapping networks in your network, how do both Firewalls connect with each other?

    Note: Try avoiding using the network 192.168.1.x/192.168.0 in your enterprise networks as these two networks are used by home users, so it might cause routing issues down the road for you.

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Unfiltered HTML