<?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 802.1x wired timeout in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/802-1x-wired-timeout/m-p/69055#M18630</link>
    <description>I have been using 1x at our high school for a few years.  I cannot be sure if it's related to XOS updates or Windows updates, but when we came back to school this summer I ran into problems with clients (mostly win7) reverting to an unauth state (preauth topology/vlan) mid day.&lt;BR /&gt;
&lt;BR /&gt;
the problem is that the connection does not reset when that topology changes, so my users are left with a DHCP address from the authenticated topology, which is no longer egressing on the port.&lt;BR /&gt;
&lt;BR /&gt;
My work around had been to ask my users to unplug/replug the network cable in these cases, but now I have just made the auth topology be the same as the unauth topology.&lt;BR /&gt;
&lt;BR /&gt;
There are a number of windows hotfixes related to 1x from Microsoft released going back to 2013.  I know some take care of a problem at startup that is causing 1x timeouts due to Windows not acknowledging a successful auth.&lt;BR /&gt;
&lt;BR /&gt;
Have anyone figured the best mix of hotfixes to apply to windows clients to make 1x stable?&lt;BR /&gt;
&lt;BR /&gt;
Thanks!</description>
    <pubDate>Tue, 08 Oct 2019 18:17:33 GMT</pubDate>
    <dc:creator>Keith_Obermeie1</dc:creator>
    <dc:date>2019-10-08T18:17:33Z</dc:date>
    <item>
      <title>802.1x wired timeout</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/802-1x-wired-timeout/m-p/69055#M18630</link>
      <description>I have been using 1x at our high school for a few years.  I cannot be sure if it's related to XOS updates or Windows updates, but when we came back to school this summer I ran into problems with clients (mostly win7) reverting to an unauth state (preauth topology/vlan) mid day.&lt;BR /&gt;
&lt;BR /&gt;
the problem is that the connection does not reset when that topology changes, so my users are left with a DHCP address from the authenticated topology, which is no longer egressing on the port.&lt;BR /&gt;
&lt;BR /&gt;
My work around had been to ask my users to unplug/replug the network cable in these cases, but now I have just made the auth topology be the same as the unauth topology.&lt;BR /&gt;
&lt;BR /&gt;
There are a number of windows hotfixes related to 1x from Microsoft released going back to 2013.  I know some take care of a problem at startup that is causing 1x timeouts due to Windows not acknowledging a successful auth.&lt;BR /&gt;
&lt;BR /&gt;
Have anyone figured the best mix of hotfixes to apply to windows clients to make 1x stable?&lt;BR /&gt;
&lt;BR /&gt;
Thanks!</description>
      <pubDate>Tue, 08 Oct 2019 18:17:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/802-1x-wired-timeout/m-p/69055#M18630</guid>
      <dc:creator>Keith_Obermeie1</dc:creator>
      <dc:date>2019-10-08T18:17:33Z</dc:date>
    </item>
  </channel>
</rss>

