<?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 s-series ST1206-0848-F6 randonlyrejects connection of an specific ip in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/s-series-st1206-0848-f6-randonlyrejects-connection-of-an/m-p/10183#M1211</link>
    <description>s-series ST1206-0848-F6 randonly - apparently - rejects connection of an specific ip&lt;BR /&gt;
&lt;BR /&gt;
3 weeks ago the switch ST1206-0848-F6 randonly started rejecting the connection of a server, we tried:&lt;BR /&gt;
&lt;BR /&gt;
- connecting the server in another vlan, not worked&lt;BR /&gt;
- replacing the ethernet cable, not worked&lt;BR /&gt;
- replacing the NIC card not worked&lt;BR /&gt;
- changing th ip of the interface from xxx.xxx.xxx.x15 to xxx.xxx.xxx.x14 and it worked, and is still working&lt;BR /&gt;
&lt;BR /&gt;
another strange thing is that when with the ip xxx.xxx.xxx.x15 till 8.40am-18:00pm it remains blocked but through 18:00pm to 08:40 the switch accepted the connections, we imagine that was the network load between the server and the switch that trigger this event, but with no confirmation&lt;BR /&gt;
&lt;BR /&gt;
this server is used for web proxy, so he carries the web traffic of the entire facility, we need to prevent that it wont happen again, can someone help me?&lt;BR /&gt;</description>
    <pubDate>Tue, 23 Oct 2018 17:32:00 GMT</pubDate>
    <dc:creator>Rafael_Silva</dc:creator>
    <dc:date>2018-10-23T17:32:00Z</dc:date>
    <item>
      <title>s-series ST1206-0848-F6 randonlyrejects connection of an specific ip</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/s-series-st1206-0848-f6-randonlyrejects-connection-of-an/m-p/10183#M1211</link>
      <description>s-series ST1206-0848-F6 randonly - apparently - rejects connection of an specific ip&lt;BR /&gt;
&lt;BR /&gt;
3 weeks ago the switch ST1206-0848-F6 randonly started rejecting the connection of a server, we tried:&lt;BR /&gt;
&lt;BR /&gt;
- connecting the server in another vlan, not worked&lt;BR /&gt;
- replacing the ethernet cable, not worked&lt;BR /&gt;
- replacing the NIC card not worked&lt;BR /&gt;
- changing th ip of the interface from xxx.xxx.xxx.x15 to xxx.xxx.xxx.x14 and it worked, and is still working&lt;BR /&gt;
&lt;BR /&gt;
another strange thing is that when with the ip xxx.xxx.xxx.x15 till 8.40am-18:00pm it remains blocked but through 18:00pm to 08:40 the switch accepted the connections, we imagine that was the network load between the server and the switch that trigger this event, but with no confirmation&lt;BR /&gt;
&lt;BR /&gt;
this server is used for web proxy, so he carries the web traffic of the entire facility, we need to prevent that it wont happen again, can someone help me?&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Oct 2018 17:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/s-series-st1206-0848-f6-randonlyrejects-connection-of-an/m-p/10183#M1211</guid>
      <dc:creator>Rafael_Silva</dc:creator>
      <dc:date>2018-10-23T17:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: s-series ST1206-0848-F6 randonlyrejects connection of an specific ip</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/s-series-st1206-0848-f6-randonlyrejects-connection-of-an/m-p/10184#M1212</link>
      <description>It would be best to open a case with GTAC to discuss options for tracking this down.&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Nov 2018 02:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/s-series-st1206-0848-f6-randonlyrejects-connection-of-an/m-p/10184#M1212</guid>
      <dc:creator>Daniel_Coughlin</dc:creator>
      <dc:date>2018-11-06T02:43:00Z</dc:date>
    </item>
  </channel>
</rss>

