- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Web and Unmanaged
- >
- HP 1910 802.1x authenticates, then drops
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Community
Resources
Forums
Blogs
- 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
06-23-2015 01:55 PM
06-23-2015 01:55 PM
HP 1910 802.1x authenticates, then drops
I'm used to working with 5400, 2910 switches and the CLI. I've tried to set up our 802.1x/RADIUS on a 1910-8 switch in an outbuilding, and it almost works.
On a windows 7 client I connect cable, enter credentials and I get placed on the appropriate VLAN for my userID, get valid DHCP address for my subnet.
Everything works for about 100-120 seconds, then the switch puts the port back onto the unauth vlan number and client computer can no longer connect unless you release DHCP and renew, then it gets an IP on the unauth(quarantine) vlan.
plugging/unplugging usually restores authorized service - again for about 100-120 seconds.
The client doesn't appear aware that anything changed, but a continuous ping will fail after the 120 seconds.
The RADIUS/802.1x/AAA works on all our 5400/8200/29xx wired clients and our WiFi.
Any ideas?
Thanks