- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Rule with custom service being dropped by the fire...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rule with custom service being dropped by the firewall
Dear Mates
I have a service that runs on port TCP 50400, I created a custom service object for this port, but when I use the custom tcp service in the rule, it doesnt work, the traffic goes to the clean-up rule. But when I use ANY, it works fine, and in the logs I can see that the service is using TCP 50400.
Any idea on how I can overcome this issue, as I do not wish to leave the Service Colum with ANY.
Thanks
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What precise version/JHF level?
Are you absolutely sure that the source/destination seen in the logs would otherwise match the rule?
Are you absolutely sure that the source/destination seen in the logs would otherwise match the rule?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Phoneboy
we have R80.20 take 103.
Yes the source/destination seen in the logs would match the rule
we have R80.20 take 103.
Yes the source/destination seen in the logs would match the rule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Highly recommend a TAC case here.