conectivity problem with port based authentication

m_meraj — Sun, 10 Mar 2019 21:12:17 GMT

HI,

I could not able to autheticate through acs 3.3 on windows xp client, ACS is connected to core sw 4006 and my client is also connected to same sw.

when I debug dot1x I got this message. could anybody tell me where is the problem.

" 4w0d: dot1x-ev:Delaying initial EAP-Request/Identity packet

4w0d: dot1x-ev:Received pkt saddr =000e.7f61.25db , daddr = 0180.c200.0043 ,

pae-ether-type = 34958

4w0d: dot1x-ev:Received AuthStart from Authenticator

4w0d: dot1x-ev:Managed Timer in sub-block attached as leaf to master

4w0d: dot1x-ev:Going to Send Request to AAA Client on RP for id = 1 and length =

4w0d: dot1x-ev:Got a Request from SP to send it to Radius with id 112

4w0d: dot1x-ev:Couldn't Find a process thats already handling the request for this id 1

4w0d: dot1x-ev:Found a free slot at slot 0

4w0d: dot1x-ev:Created a New process with Id 62

4w0d: dot1x-ev:Successfully created a process to handle this aaa request

4w0d: dot1x-ev:Inserted the request on to list of pending requests

4w0d: dot1x-ev:Request id = 112 and length = 9

4w0d: dot1x-ev:The Interface on which we got this AAA Request is GigabitEthernet 4/7

4w0d: dot1x-ev:Username is test

4w0d: RADIUS: ustruct sharecount=1

4w0d: RADIUS: EAP-login: length of radius packet = 73 code = 1

4w0d: RADIUS: Initial Transmit GigabitEthernet4/7 id 111 10.102.10.6:1812, Access-Request, len 73

4w0d: Attribute 4 6 0A6603FE

4w0d: Attribute 61 6 00000000

4w0d: Attribute 1 6 74657374

4w0d: Attribute 12 6 000003E8

4w0d: Attribute 79 11 02010009

4w0d: Attribute 80 18 093B78F5

4w0d: RADIUS: Received from id 111 10.102.10.6:1812, Access-Reject, len 56

4w0d: Attribute 79 6 04000004

4w0d: Attribute 18 12 52656A65

4w0d: Attribute 80 18 702E0914

4w0d: RADIUS: EAP-login: length of eap packet = 4

4w0d: RADIUS: EAP-login: got reject from radius

4w0d: dot1x-ev:going to send to backend on SP, length = 4

4w0d: dot1x-ev:Received VLAN is No Vlan

4w0d: dot1x-ev:Enqueued the response to BackEnd

4w0d: dot1x-ev:The process does its job, so killing itself

4w0d: dot1x-ev:Received QUEUE EVENT in response to AAA Request

4w0d: dot1x-ev:Dot1x matching request-response found

4w0d: dot1x-ev:Length of recv eap packet from radius = 4

RIY-CC-IT-CORE#

4w0d: dot1x-ev:Received VLAN Id -1

4w0d: dot1x-ev:dot1x_bend: Sending Radius Response to Supplicant of length 4"

Re: conectivity problem with port based authentication

jafrazie — Wed, 29 Jun 2005 02:41:29 GMT

Not enough info. Doesn't look like the complete transaction. Why does ACS tell you the service attempt has failed?

topic conectivity problem with port based authentication in Network Access Control

conectivity problem with port based authentication

Re: conectivity problem with port based authentication