Quantcast
Channel: Network Access Protection forum
Viewing all articles
Browse latest Browse all 1875

NPS Discarding RADIUS request from Cisco switch (802.1x)

$
0
0

Last few weeks I've been busy to get the following to work:

- Cisco 2960 switch as the suppliant
- Another Cisco 2960 as the authenticator switch
- The supplicant is only able to send MS-EAP MS-ChapV2 requests
- The NPS server is Windows 2008 R2 (and also tested on 2012 R2)

This is called "NEAT" by Cisco; which does seem to work with Cisco ISE (http://www.cisco.com/c/en/us/support/docs/lan-switching/8021x/116681-config-neat-cise-00.html) but I'd like to get it to work with Windows NPS.

Within NPS I've setup the following Connection Request policy:
- NAS Port Type: Ethernet

I'm using the following Network Policy:
- User Group: DOMAIN\Switches (the useraccount used by the switch is part of this group)
- NAS Port Type: Ethernet
- Autehntcation Type: EAP

Now the request sent by the switch is discarded. The actual error is the following (excluded irrelevant information):

User:
	Account Name:			Rotterdam-Switch-8-1
	Account Domain:			DOMAIN

Authentication Details:
	Connection Request Policy Name:	Secure Wired Connections
	Network Policy Name:		Switches Allowed
	Authentication Provider:	Windows
	Authentication Server:		SERVER.DOMAIN.local
	Authentication Type:		EAP
	EAP Type:			-
	Account Session Identifier:	-
	Reason Code:			1
	Reason:				An internal error occurred. Check the system event log for additional information.

Wireshark on the NPS server shows:
1. The RADIUS Access-Request (1) being received by the NPS Server
2. The NPS Server sending out a RADIUS Access-Challenge (11) to the authenticator switch
3. Another RADIUS Access-Request (1) is beging received by the NPS Server

Packet 2 has an t=EAP-Message(79) with type MS-EAP-Authentication [Palekar](26) and MS-CHAPv2-ID set to 2 and OpCode 1 (Challange)
Packet 3 has an t=EAP-Message(79) with type MS-EAP-Authentication [Palekar](26) and MS-CHAPv2-ID set to 2 and OpCode 2 (Response)

I've also tried the following:
- I've also tested with an invalid username/password. The request is correctly denied
- I've also tested by added ALL EAP Types as condition to the Network Policy. The request isn't pickup by this policy anymore.

Any help would be greatly appriciated ofcourse.

Kind regards,
Peter


Viewing all articles
Browse latest Browse all 1875

Trending Articles