<?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 CP-2W Problems being ignored? in Communications and Wireless</title>
    <link>https://community.hpe.com/t5/communications-and-wireless/cp-2w-problems-being-ignored/m-p/3051509#M1691</link>
    <description>Are those of us that are having problems with the CP-2W wireless access point being ignored?&lt;BR /&gt;&lt;BR /&gt;I can accept a formal notice from HP about them not supporting this product any longer, PROVIDED they fix the problem they appear to have introduced in 2.08 or 2.09 of the firmware.&lt;BR /&gt;&lt;BR /&gt;For those that don't know, accessing the cp.home admin pages of the WAP after a couple of hours, or longer, of it being active causes the WAP to lock up. It stops all traffic in or out of the WAP. Only way to get connectivity restored is to power cycle the thing. This means, any time you need to do anything ADMIN related means power cycling and disrupting the network.&lt;BR /&gt;&lt;BR /&gt;This problem appears to have been introduced in 2.08 or 2.09. The only problem is that 2.08 or 2.09 also fixes another problem that appears to pop up when using cable modems.&lt;BR /&gt;</description>
    <pubDate>Tue, 19 Aug 2003 05:30:05 GMT</pubDate>
    <dc:creator>gregory youngblood</dc:creator>
    <dc:date>2003-08-19T05:30:05Z</dc:date>
    <item>
      <title>CP-2W Problems being ignored?</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/cp-2w-problems-being-ignored/m-p/3051509#M1691</link>
      <description>Are those of us that are having problems with the CP-2W wireless access point being ignored?&lt;BR /&gt;&lt;BR /&gt;I can accept a formal notice from HP about them not supporting this product any longer, PROVIDED they fix the problem they appear to have introduced in 2.08 or 2.09 of the firmware.&lt;BR /&gt;&lt;BR /&gt;For those that don't know, accessing the cp.home admin pages of the WAP after a couple of hours, or longer, of it being active causes the WAP to lock up. It stops all traffic in or out of the WAP. Only way to get connectivity restored is to power cycle the thing. This means, any time you need to do anything ADMIN related means power cycling and disrupting the network.&lt;BR /&gt;&lt;BR /&gt;This problem appears to have been introduced in 2.08 or 2.09. The only problem is that 2.08 or 2.09 also fixes another problem that appears to pop up when using cable modems.&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Aug 2003 05:30:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/cp-2w-problems-being-ignored/m-p/3051509#M1691</guid>
      <dc:creator>gregory youngblood</dc:creator>
      <dc:date>2003-08-19T05:30:05Z</dc:date>
    </item>
  </channel>
</rss>

