Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 40 subscribers
  • Views 5234 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

Fritzbox am WAN Port. Connection refused

Ric Sng

Hallo ,

folgendes Problem.

Sophos LAN 192.168.1.1

Sophos WAN Port 192.168.0.254

Fritzbox hängt am wan Port und hat die IP 192.168.0.1

Wie komme ich auf das webinterface der fritzbox.

Ich bekomme immer die Meldung. Connection  refused.

Ich habe bereits eine SNAT Regel ausprobiert.

From Internal(Network) -> Any -> 192.168.0.1

Quellen ändern in WAN Adress.

Bringt nichts.

Ausserdem habe ich auch schon die URL mal bei Web protection unter Richtlinien zugelassen.

Hat auch nichts gebracht..

Hat einer noch einen Tipp ?



This thread was automatically locked due to age.
Parents
  • 0

    Hallo Ric,

    Erstmal herzlich willkommen hier in der Community !

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    I followed your explanation, but "the devil is in the details" and it's easier to get an intuitive feel for what might be the root cause of an issue if one sees pictures of the Edits of the related configuration items.  Also, for context, a picture of "Connection refused" and the relevant line(s) from the Web Filtering log if the connection attempt was handled by Web Protection.

    Just to eliminate some of the common issues, what do you learn from doing #1 in Rulz?

    MfG - Bob (Bitte auf Deutsch weiterhin.)

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

    Hallo Ric,

    Erstmal herzlich willkommen hier in der Community !

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    I followed your explanation, but "the devil is in the details" and it's easier to get an intuitive feel for what might be the root cause of an issue if one sees pictures of the Edits of the related configuration items.  Also, for context, a picture of "Connection refused" and the relevant line(s) from the Web Filtering log if the connection attempt was handled by Web Protection.

    Just to eliminate some of the common issues, what do you learn from doing #1 in Rulz?

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML