- Products
- Learn
- Local User Groups
- Partners
- More
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
Join our TechTalk: Malware 2021 to Present Day
Building a Preventative Cyber Program
Be a CloudMate!
Check out our cloud security exclusive space!
Check Point's Cyber Park is Now Open
Let the Games Begin!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
I have an Exchange 2013 DAG which is connected over a Site-to-Site VPN. Replication works without issue and there is communication between the DAG members on numerous UDP and TCP ports. The only issue is the cluster heartbeat on UDP 3343. This is blocked and shows in the security log as "Connection contains real IP of NATed address". It also shows as the WAN interface and being blocked by the firewall. All other traffic from the blocked server shows as the LAN interface and being allowed by VPN. It appears that the UDP 3343 traffic is not being sent over the VPN, although my expertise is limited and I may be misinterpreting that.
I'm fairly certain this is a configuration issue as I didn't have this issue before I upgraded the Checkpoint software and reconfigured the appliance.
Any assistance is appreciated. Please don't be too technical as it will go over my head 🙂
Thanks.
I just had this problem - Support figured out that it's because I bridged my WiFi into the same IP range as my LAN which made UDP traffic mysteriously disappear. Cleared out that configuration and put WiFi back to separate networks and it fixed everything. Just in case anyone else has that same issue. Good luck!
>> Please don't be too technical as it will go over my head
I would suggest to involve TAC here, so the issue could be resolved instantly !
Did you succeed in resolving the issue yet ? Just because you never did reply...
I just had this problem - Support figured out that it's because I bridged my WiFi into the same IP range as my LAN which made UDP traffic mysteriously disappear. Cleared out that configuration and put WiFi back to separate networks and it fixed everything. Just in case anyone else has that same issue. Good luck!
Thanks for sharing
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY