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

Exchange attempting to connect to sophos via 443?

Yogi_Bear_79
So far today I have roughly 696 drops as seen below.  Everything works as far as I can tell. Perhaps something doesn't work as well as it should? 

Can you tell me what the exchange server is trying to do here?

Exchange: 10.10.0.16
Sophos Internal: 10.10.0.12

I presume I need to make a firewall rule, but not entirely sure as to what for.

Something like

10.10.0.16 -> 443 -> 10.10.0.12 (allow)

2015:10:15-13:05:30 sophos ulogd[3265]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60001" initf="eth0" srcmac="00:25:b5:1a:01:ff" dstmac="00:1a:8c:5f:24:58" srcip="10.10.0.16" dstip="10.10.0.12" proto="6" length="52" tos="0x00" prec="0x00" ttl="128" srcport="443" dstport="43720" tcpflags="ACK FIN"


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

    If anything, there might be an Ethernet latency issue in the segment between the UTM and Exchange, but there's no rule you can make in the UTM to accept traffic that it would have no idea what to do with.

    Cheers - Bob
Reply
  • 0
    Everything works

    If anything, there might be an Ethernet latency issue in the segment between the UTM and Exchange, but there's no rule you can make in the UTM to accept traffic that it would have no idea what to do with.

    Cheers - Bob
Children
No Data