Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1182 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

Masq NAT IPs cant connect to HTTPS sites

rahman
Hi,

We have HTTP Proxy profiles enabled and all of them configured not to scan https traffic. We only porxy the nat network. We have a few host that has real public IPs. The real ips can connect to ssl sites as expected but none of the NAT IPs connect to a https site, they all timeout. There is also a "NAT_NETWORK -> any -> any: allow" package rule. I also monitor live package logs, there are no dropped packages. 

So where should be the problem is?


This thread was automatically locked due to age.
Parents
  • 0
    The real ips can connect to ssl sites as expected but none of the NAT IPs connect to a https site,

    Where are the hosts with public IPs - in a DMZ, or ???

    Please show your masq rule for the NAT_NETWORK.

    Where are the HTTPS sites you cannot reach?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    The real ips can connect to ssl sites as expected but none of the NAT IPs connect to a https site,

    Where are the hosts with public IPs - in a DMZ, or ???

    Please show your masq rule for the NAT_NETWORK.

    Where are the HTTPS sites you cannot reach?

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