GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Communications and Wireless
- >
- CP-2W Problems being ignored?
Communications and Wireless
1856446
Members
4266
Online
104113
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2003 10:30 PM
08-18-2003 10:30 PM
CP-2W Problems being ignored?
Are those of us that are having problems with the CP-2W wireless access point being ignored?
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.
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.
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.
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.
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP