<?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: 802.1x protocol version issues with network printers in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357831#M337270</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marc:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I checked this on switch running 12.2.x and it was dot1x protocol version=2, so it looks like that protocol version was introduced from 12.2.x&lt;/P&gt;&lt;P&gt;onwards. There should not be any compatible issue but I have seen this issue in the past with 2950 running dot1x version 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EAPOL packet Protocol version field holds the version of the protocol supported by the sender of the EAPolpacket. It means the supplicant will try with a more secure protocol version with the server if server does not support that, then supplicant with try with the next/lower one available until both server and client negotiate on a common protocol version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;JK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Plz rate helpful posts-&lt;/P&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jan 2010 13:50:35 GMT</pubDate>
    <dc:creator>Jatin Katyal</dc:creator>
    <dc:date>2010-01-27T13:50:35Z</dc:date>
    <item>
      <title>802.1x protocol version issues with network printers</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357830#M337239</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;currently we are deploying Catalyst 3560 switches in our enviroment. These switches are working with dot1x protocol version 2. The old ones (2950) are with version 1. We have several networkprinters and it seems these combination does not work togehter. The printers are not authenticating. Port remains unauthorized. Mac Bypass is only working if 802.1x is disabled on these printers. Are these protocol version incompatible ??? Is any one out there who´s having the same issues or an idea how to fix this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:54:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357830#M337239</guid>
      <dc:creator>Marc Plagge</dc:creator>
      <dc:date>2019-03-10T23:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x protocol version issues with network printers</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357831#M337270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marc:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I checked this on switch running 12.2.x and it was dot1x protocol version=2, so it looks like that protocol version was introduced from 12.2.x&lt;/P&gt;&lt;P&gt;onwards. There should not be any compatible issue but I have seen this issue in the past with 2950 running dot1x version 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EAPOL packet Protocol version field holds the version of the protocol supported by the sender of the EAPolpacket. It means the supplicant will try with a more secure protocol version with the server if server does not support that, then supplicant with try with the next/lower one available until both server and client negotiate on a common protocol version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;JK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Plz rate helpful posts-&lt;/P&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2010 13:50:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357831#M337270</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2010-01-27T13:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x protocol version issues with network printers</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357832#M337312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i´ve read my first posting again. It´s may be a little bit confusing which switch is working. 2950 dot1x V1 --&amp;gt; Everything is fine! 3560 dot1x V2 --&amp;gt; not working with printers! In the debug log EAPOL seems not going down to V1 (EAPOL Version: 0x2&amp;nbsp; type: 0x0&amp;nbsp; length: 0x0005). Is there any way to force the 3560 to go to dot1x V1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2010 14:29:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-protocol-version-issues-with-network-printers/m-p/1357832#M337312</guid>
      <dc:creator>Marc Plagge</dc:creator>
      <dc:date>2010-01-27T14:29:15Z</dc:date>
    </item>
  </channel>
</rss>

