<?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: APPID signature  for Zebra Printers showing unknown-tcp or insufficient data in Custom Signatures</title>
    <link>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150651#M166</link>
    <description>&lt;P&gt;Mario,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please read the documented process for new App-ID coverage here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Request-a-new-App-ID/ta-p/60834" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Request-a-new-App-ID/ta-p/60834&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But before you go....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like most of the Zebra printer traffic is being recognized as a known App-ID. Is that true? If so are you expecting that this one printer model should also show up as the same App-ID? If so a Support Case might be appropriate to fix the existing App-ID.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're interested in creating a custom signature for this traffic then please share some pcaps and other helpful contextual information that we might use to guide your efforts.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All the best,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Benjamin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 31 Mar 2017 19:30:21 GMT</pubDate>
    <dc:creator>bpappas</dc:creator>
    <dc:date>2017-03-31T19:30:21Z</dc:date>
    <item>
      <title>APPID signature  for Zebra Printers showing unknown-tcp or insufficient data</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150650#M165</link>
      <description>&lt;P&gt;I am seeing that traffic that goes to an specific vendor/model (Zebra LP&amp;nbsp;2844-z) of labeling printers is being categorized as APPid&amp;nbsp;unknown-tcp or insufficient data on port 2001 TCP. I would like to know if there is a way to get this added to your APPID database so when traffic matching this signature is automatically tagged.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;M&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 19:27:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150650#M165</guid>
      <dc:creator>LCMember25117</dc:creator>
      <dc:date>2017-03-31T19:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: APPID signature  for Zebra Printers showing unknown-tcp or insufficient data</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150651#M166</link>
      <description>&lt;P&gt;Mario,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please read the documented process for new App-ID coverage here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Request-a-new-App-ID/ta-p/60834" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Request-a-new-App-ID/ta-p/60834&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But before you go....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like most of the Zebra printer traffic is being recognized as a known App-ID. Is that true? If so are you expecting that this one printer model should also show up as the same App-ID? If so a Support Case might be appropriate to fix the existing App-ID.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're interested in creating a custom signature for this traffic then please share some pcaps and other helpful contextual information that we might use to guide your efforts.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All the best,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Benjamin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 19:30:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150651#M166</guid>
      <dc:creator>bpappas</dc:creator>
      <dc:date>2017-03-31T19:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: APPID signature  for Zebra Printers showing unknown-tcp or insufficient data</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150653#M167</link>
      <description>&lt;P&gt;I did submit a request previously. I didn't get any reply so far on my inbox.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure, but the traffic for this specific model is&amp;nbsp;recognized as UNknown-tcp or insufficient data. At the moment we are allowing traffic for the service port 2001 TCP instead with ANY APPID. I am not sure for other Zebra printers. Do you mean appid ZPL?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have also just opened a support case to work on this already for further inverstigation. PCAPS, traffic logs, putty session logs and tech support file was submited.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As per customer needs, no custom AppIDs are added to fix these kind of &amp;nbsp;issues. They state that the same printer model and various of the same vendor's traffic has no APPID assigned to them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 20:13:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/150653#M167</guid>
      <dc:creator>LCMember25117</dc:creator>
      <dc:date>2017-03-31T20:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: APPID signature  for Zebra Printers showing unknown-tcp or insufficient data</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/161620#M178</link>
      <description>&lt;P&gt;Mario,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ZPL is the App-ID for Zebra.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've talked to the case owner and he will request some packet captures of the mis-identified traffic and then it should be possible to update the ZPL App-ID.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Benjamin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 16:55:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/appid-signature-for-zebra-printers-showing-unknown-tcp-or/m-p/161620#M178</guid>
      <dc:creator>bpappas</dc:creator>
      <dc:date>2017-06-16T16:55:31Z</dc:date>
    </item>
  </channel>
</rss>

