- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Wired 802.1x with Procurve and NPS - Problem
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
05-05-2014 06:53 AM
05-05-2014 06:53 AM
Wired 802.1x with Procurve and NPS - Problem
I have followed this guide:
The computer just ends up in the un-auth VLAN and there is no entries in the NPS servers Event Viewer.
Anyone got any ideas why it won't authenticate against the NPS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2014 11:18 PM - edited 05-06-2014 05:24 AM
05-05-2014 11:18 PM - edited 05-06-2014 05:24 AM
Re: Wired 802.1x with Procurve and NPS - Problem
I just sniffed for traffic in the firewall and no traffic from the switch can be found.
Why doesn't the switch send any authentication-traffic towards the NPS?
-EDIT-
Tried with my MacBook and I got a login request. Correct credentials=auth VLAN, otherwise unauth VLAN. Looks good in Event Viewer.
One thing that caught my eye is that the server certificate that is presented as server certificate is not the one I chose in the NPS. How come?
-EDIT2-
It now presents the correct server certificate.
Sniffed when connecting with the MacBook and I can see RADIUS-traffic back and forth. When connecting the windows client no traffic is seen.
This indicates that the client doesn't even try to authenticate. Why is that?
-EDIT3-
Now I found out that the client does authenticate and ends up in the correct VLAN, but it takes 15 minutes after login. What could be causing that delay?
(Found a fix http://blogs.technet.com/b/jeff_stokes/archive/2013/01/24/20-minute-delay-deploying-windows-7-on-802-1x-fix-it-here.aspx)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2015 07:04 AM
05-01-2015 07:04 AM
Re: Wired 802.1x with Procurve and NPS - Problem
Hello, I had to set up a test environment to authenticate client computers that are connected to a switch, using an NPS server as a RADIUS server.
The problem is that client computers when attempting to authenticate an authorized user I get "Failed to authenticate" and Event Viewer NPS server I get the request for access was denied to use an unknown user name or password wrong, but when I put a user name and password of a user who is not authorized then I get access not meet the conditions of the network policy was denied. I do not understand why this error is coming because the username and password if you are correct. No problem if certificates if customer problem radius (the switch) or that may be the problem.
Here is documented step by step everything I've done -> https://drive.google.com/file/d/0B-x4Iph-KSEjYVZVYTJscmJhYlU/view?usp=sharing
If you can take a look and see where the problem may be, I would be very grateful.