- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: 4500 radius port authentication
Comware Based
1752295
Members
4560
Online
108786
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
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
05-12-2009 02:09 AM
05-12-2009 02:09 AM
4500 radius port authentication
hello,
i have 2 problems.
1) when logging in through terminal. the user I'm using(any from the active directory) doesn't get admin privilleges(level 3). and when logging in through the webinterface/http. I can just use the standard username and password... how can I configure the 4500 to also use authentication throuch the http login
2)port 1 is set on auto to authorize the pc that connects to that port. everything works perfectly. when using user: example1 the access to the network is restricted and when using user: example2, the access to the network is granted. I even get nice logs wether the user is granted or denied. However, after approx. 25 seconds the computer/client starts demanding a new ip-address and says that the authentication has failed, no ip address is received. and I also don't get any logfiles about it.
any hints are welcome.
greetings Thierry
i have 2 problems.
1) when logging in through terminal. the user I'm using(any from the active directory) doesn't get admin privilleges(level 3). and when logging in through the webinterface/http. I can just use the standard username and password... how can I configure the 4500 to also use authentication throuch the http login
2)port 1 is set on auto to authorize the pc that connects to that port. everything works perfectly. when using user: example1 the access to the network is restricted and when using user: example2, the access to the network is granted. I even get nice logs wether the user is granted or denied. However, after approx. 25 seconds the computer/client starts demanding a new ip-address and says that the authentication has failed, no ip address is received. and I also don't get any logfiles about it.
any hints are welcome.
greetings Thierry
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2009 03:21 AM
05-12-2009 03:21 AM
Re: 4500 radius port authentication
edit 10:18 12 may 2009
problem 2 seems to be solved. the problem was that the handshake timeout period was set to 15 seconds... which is too short. so the clients gets an authentication timeout. when setting the handshake timeout to 60 sec it works fine. now i've set the timeout to the maximum of 1024... because i don't want to see the annoying balloon "connected" every minute!
greetings Thierry
problem 2 seems to be solved. the problem was that the handshake timeout period was set to 15 seconds... which is too short. so the clients gets an authentication timeout. when setting the handshake timeout to 60 sec it works fine. now i've set the timeout to the maximum of 1024... because i don't want to see the annoying balloon "connected" every minute!
greetings Thierry
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP