<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Kerberos-TCP violation in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233861#M45282</link>
    <description>&lt;P&gt;I would try what Phoneboy suggested, makes sense.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Tue, 26 Nov 2024 21:12:47 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-11-26T21:12:47Z</dc:date>
    <item>
      <title>Kerberos-TCP violation</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233830#M45274</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have one edge gateway that is giving this 'Connection alert' when some traffic is routing through here. No other gateway is having this issue. I'm still in touch with TAC but they are saying it might be a Identity Awareness issue with Kerberos but our identity awareness is setup identical throughout all gateways. Has anyone run into this error before and can give some guidance on what else it might be? I've personally not seen this before.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Firewall - Protocol violation detected with protocol:(Kerberos-TCP), matched protocol sig_id:(2), violation sig_id:(4). (500)&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 14:37:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233830#M45274</guid>
      <dc:creator>xLadyMorgana</dc:creator>
      <dc:date>2024-11-26T14:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos-TCP violation</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233860#M45280</link>
      <description>&lt;P&gt;You might try disabling the protocol signature for the Kerberos-TCP service.&lt;BR /&gt;This is done in the relevant service object in the Advanced section.&lt;BR /&gt;Curiously, the default Kerberos service (called Kerberos_v5_TCP in a default R81.20 installation) does not have this checked.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 21:07:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233860#M45280</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2024-11-26T21:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos-TCP violation</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233861#M45282</link>
      <description>&lt;P&gt;I would try what Phoneboy suggested, makes sense.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 21:12:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-TCP-violation/m-p/233861#M45282</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-11-26T21:12:47Z</dc:date>
    </item>
  </channel>
</rss>

