Hi dncastro and Jonas,
Yes, the authentication method is EAP-PEAP, but the machine is only configured for "computer authentication", and not "user authentication", so if the machine is not a domain machine should be place directly in the quarantine VLAN, no authentication with AD user credentials.
The client side 802.1X configuration is ok, also de Radius certificate from ClearPass, because when is a domain machine it authenticates correctly, and is assigned the correct VLAN.
I attach the switch interface settings and ClearPass policy. The switch has also mac-authentication commands, because I am also authenticating phones and printers (VLAN 21), service which works correctly as well:
SWITCH INTERFACE
interface GigabitEthernet1/0/3
port link-type hybrid
port hybrid vlan 21 tagged
port hybrid vlan 1 50 55 untagged
mac-vlan enable
poe enable
dot1x
undo dot1x handshake
dot1x mandatory-domain dot1x-auth
undo dot1x multicast-trigger
dot1x unicast-trigger
mac-authentication
mac-authentication domain mac-auth
mac-authentication timer auth-delay 15
mac-authentication parallel-with-dot1x
#
I have tried also adding the "dot1x auth-fail vlan 50" command, but with the same result.
CLEARPASS
Roles Tab

Enforcement Tab

Default profile (quarantine VLAN)

I repeat, when the client is a domain machine, it authenticates correctly and is assigned the correct VLAN (VLAN 1 untagged), no timeout errors at all. Also the phones authenticate correctly by MAC authentication, and get assigned VLAN 21 tagged. Any tip?
------------------------------
Regards,
Julian
------------------------------
Original Message:
Sent: Sep 27, 2023 04:16 PM
From: jonas.hammarback
Subject: Timeout when setting a quarantine VLAN
Hi Julian
By your description I assume that the authentication method is EAP-PEAP and the machine that is not a domain machine tries to perform an authentication with the user credentials in Active Directory.
One problem, beside the fact that EAP-PEAP is an old protocol with flaws, is that the client side configuration can be a callange and if the client doesn't have correct 802.1x configuration it will not accept the Radius certificate from ClearPass and the request will time out. Another issue can of course be that the client doesn't have 802.1x configured at all, and in that case you need to provide a MAC authentication service to handle the authentication for unknown machines and send back the quarantine VLAN, or configure the VLAN in the switch as a VLAN that the unauthenticated client is placed on.
------------------------------
Best Regards
Jonas Hammarbäck
MVP 2023, ACCX #1335, ACX-Network Security, Aruba SME, ACMP, ACDP , ACEP, ACSA
Aranya AB
If you find my answer useful, consider giving kudos and/or mark as solution
Original Message:
Sent: Sep 27, 2023 10:24 AM
From: fjulianom
Subject: Timeout when setting a quarantine VLAN
Hi community,
I am setting up a wired 802.1X authentication scheme with ClearPass and H3C switches. My policy says:
- If the machine is in the corporate domain (machine authenticated), it gets assigned VLAN 1 untagged and have network access.
- If the machine is not in the corporate domain, it gets assigned the quarantine VLAN 50 and doesn't have network access.
Point 1 works perfectly. For point 2, when I plug in a PC which is not in the corporate domain, I have a timeout response, I don't know why:

And got the quarantine VLAN 50 (because of the Default Profile in Enforcement tab):

According to me, the behaviour should be to get the quarantine VLAN 50 with a Reject response, instead a Timeout response.
Any ideas?
------------------------------
Regards,
Julian
------------------------------