Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About LC_IT
LC_IT
Here to help
Member since Mar 17, 2022
yesterday
Community Record
11
Posts
0
Kudos
1
Solution
Badges
Dec 1 2022
4:04 AM
You must use "Click-through" option and configure a "Custom splash URL" under Wireless > CONFIGURE > Splash page
... View more
Oct 11 2022
5:00 AM
Hi Brash. I don't have MX, just Access Point Meraki MR, ISE and Anyconnect with System Scan module running on endpoint.
... View more
Oct 10 2022
7:03 PM
Hi! Please, can someone please help me? It's possible run posture on Windows endpoint connected to MR33 using Cisco Anyconnect + ISE solution?
... View more
Mar 31 2022
5:09 AM
Sim, aumentei o Radius Timeout de 1 para 10 conforme esse doc: https://documentation.meraki.com/MR/Access_Control/MR_Meraki_RADIUS_2.0#Server_Timeout_and_Retry_Count
... View more
Mar 23 2022
1:16 PM
Increase the Radius Timeout solved the problem! Thank you so much!
... View more
Mar 18 2022
11:38 AM
Yes, I did a capture. Time from first radius package: 16:04:45,239667 Time from last radius package: 16:04:49,287265 Almost 5 seconds... Unfortunately I am not able to test now, but I will try to increase the timeout and verify if solve the problem @RaphaelLDid you try increase radius timeout?
... View more
Mar 18 2022
8:05 AM
In my case, the both logs are similiar: Connection Log==> Client made an 802.1X authentication request to the RADIUS server, but it did not respond.auth_mode='wpa2-802.1x' vlan_id='11' radius_proto='ipv4' radius_ip='172.16.x.x' reason='radius_timeout' radio='1' vap='1' channel='149' rssi='30' Timeline==> Client 9a:b0:xx:xx:xx:xx had a failed connection to SSID Y on AP Z during authentication because the auth server did not respond.
... View more
Mar 17 2022
8:23 AM
Hi, let me see if anyone saw a situation like this: 802.1x PEAP MSCHAPv2 authentication using a laptop windows and a smartphone. The Radius Server is Cisco ISE and it reply the MR AP with a Access-Accept packet. Cisco ISE and Access Point are connected to the same L2 domain, same subnet and there is not a firewall on that communication. The Access Point was added on ISE as NAD and there is not logs of problem on ISE side. I did a packet capture on wired interface of Access Point MR46E and the Access-Accept is delivered but in dashboard I see this error: "Client 5c:cd:5b:a2:40:ab had a failed connection to SSID Corp on AP POC01 during authentication because the auth server did not respond." How auth server did not reply if I see the access-accept arriving on AP? Someone saw this behavior?
... View more
Mar 17 2022
6:54 AM
Time, estou com situação curiosa. O cenário é de uma simples autenticação 802.1x PEAP MSCHAPv2 com máquina windows e smartphone. O Radius Server é Cisco ISE que responde a solicitação com Access-Accept. Cisco ISE e Access Point estão no mesmo domínio L2, mesma rede, não tem firewall nessa comunicação. O Access Point está cadastrado no ISE como NAD (dispositivo confiável) e não tenho logs de problema no lado do ISE. Na captura de pacotes eu vejo o Access-Accept chegando até a porta do Access Point MR46E porém na dashboard eu tenho a mensagem: "Client 5c:cd:5b:a2:40:ab had a failed connection to SSID Corp on AP POC01 during authentication because the auth server did not respond." Como o auth server não respondeu se eu vejo na captura de pacotes que a resposta do ISE chegou no AP? Alguém já viu algo semelhante?
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 1578 | Mar 31 2022 5:09 AM |
© 2024 Cisco Systems, Inc.
