• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

华三交换/AC/AP与Windows Radius无线动态vlan认证及配置

2019-02-15提问
  • 0关注
  • 1收藏,6578浏览
老池 二段
粉丝:1人 关注:9人

问题描述:

还是之前的问题,研究了好几天依旧没有解决。

需求为:  

针对无线用户,使用AD域用户验证后,获取对应vlan的IP地址。  

配置环境如下:

S5500核心+S5130POE+WX2560H AC+WA4320H AP+Windows AD/DNS/DHCP+Windows NPS(Radius)

目前配置完成后验证框能跳出,AD域用户验证后失败。

debugging、AC及核心配置见附件(贴配置乱行、配置挂附件怎么看不到呢?)

<WX2560H>*Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Processing RADIUS authentication. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Sent authentication request successfully. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: Got request data successfully, primitive: authentication. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: Getting RADIUS server info. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: Got RADIUS server info successfully. *Feb 15 09:55:13:666 2019 WX2560H RADIUS/7/EVENT: Created request context successfully. *Feb 15 09:55:13:667 2019 WX2560H RADIUS/7/EVENT: Created request packet successfully, dstIP: 192.168.20.2, dstPort: 1812, VPN instance: --(public), socketFd: 149, pktID: 221. *Feb 15 09:55:13:667 2019 WX2560H RADIUS/7/EVENT: Added packet socketfd to epoll successfully, socketFd: 149. *Feb 15 09:55:13:667 2019 WX2560H RADIUS/7/EVENT: Mapped PAM item to RADIUS attribute successfully. *Feb 15 09:55:13:667 2019 WX2560H RADIUS/7/EVENT: Got RADIUS username format successfully, format: 0. *Feb 15 09:55:13:667 2019 WX2560H RADIUS/7/EVENT: Added attribute user-name successfully, user-name: host/***.***. *Feb 15 09:55:13:668 2019 WX2560H RADIUS/7/EVENT: Filled RADIUS attributes in packet successfully. *Feb 15 09:55:13:668 2019 WX2560H RADIUS/7/EVENT: Composed request packet successfully. *Feb 15 09:55:13:668 2019 WX2560H RADIUS/7/EVENT: Created response timeout timer successfully. *Feb 15 09:55:13:668 2019 WX2560H RADIUS/7/PACKET: User-Name="host/***.***" Service-Type=Framed-User Framed-Protocol=PPP NAS-Identifier="WX2560H" NAS-Port=1 NAS-Port-Type=Wireless-802.11 NAS-Port- Calling-Station- Called-Station- Acct-Session- H3c-User-Vlan-Id=1 EAP-Message=0x0201002901686f73742f4d494e494e542d41524c344738532e636f72702e636f6e746f736f2e636f6d Message-Authenticator=0x00000000000000000000000000000000 Framed-MTU=1450 H3c-Ip-Host-Addr="0.0.0.0 c8:3d:d4:f0:79:99" NAS-IP-Address=192.168.10.252 H3c-Product- H3c-Nas-Startup-Timestamp=1550152201 *Feb 15 09:55:13:669 2019 WX2560H RADIUS/7/EVENT: Sent request packet successfully. *Feb 15 09:55:13:669 2019 WX2560H RADIUS/7/PACKET: 01 dd 01 52 1b 7d 6c 79 4b c3 d5 ec f9 87 dd 33 28 50 38 eb 01 26 68 6f 73 74 2f 4d 49 4e 49 4e 54 2d 41 52 4c 34 47 38 53 2e 63 6f 72 70 2e 63 6f 6e 74 6f 73 6f 2e 63 6f 6d 06 06 00 00 00 02 07 06 00 00 00 01 20 09 57 58 32 35 36 30 48 05 06 00 00 00 01 3d 06 00 00 00 13 57 0b 56 4c 41 4e 49 44 3d 31 3b 1f 13 43 38 2d 33 44 2d 44 34 2d 46 30 2d 37 39 2d 39 39 1e 1c 33 38 2d 41 44 2d 42 45 2d 35 38 2d 44 36 2d 41 30 3a 73 65 72 76 69 63 65 31 2c 28 30 30 30 30 30 30 30 34 32 30 31 39 30 32 31 35 30 39 35 35 31 33 30 30 30 30 30 30 30 66 30 38 31 30 30 31 39 32 1a 0c 00 00 63 a2 85 06 00 00 00 01 4f 2b 02 01 00 29 01 68 6f 73 74 2f 4d 49 4e 49 4e 54 2d 41 52 4c 34 47 38 53 2e 63 6f 72 70 2e 63 6f 6e 74 6f 73 6f *Feb 15 09:55:13:670 2019 WX2560H RADIUS/7/PACKET: 2e 63 6f 6d 50 12 fe e1 a8 43 04 2f 0c 16 b2 6a 8c 15 db 64 fb fd 0c 06 00 00 05 aa 1a 21 00 00 63 a2 3c 1b 30 2e 30 2e 30 2e 30 20 63 38 3a 33 64 3a 64 34 3a 66 30 3a 37 39 3a 39 39 04 06 c0 a8 0a fc 1a 13 00 00 63 a2 ff 0d 48 33 43 20 57 58 32 35 36 30 48 1a 0c 00 00 63 a2 3b 06 5c 65 72 09 *Feb 15 09:55:13:670 2019 WX2560H RADIUS/7/EVENT: Sent request packet and create request context successfully. *Feb 15 09:55:13:670 2019 WX2560H RADIUS/7/EVENT: Added request context to global table successfully. *Feb 15 09:55:13:670 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:17:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:17:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:221. *Feb 15 09:55:17:466 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 2, maxTries: 3. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Processing RADIUS authentication. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Sent authentication request successfully. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: Got request data successfully, primitive: authentication. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: Getting RADIUS server info. *Feb 15 09:55:18:758 2019 WX2560H RADIUS/7/EVENT: Got RADIUS server info successfully. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Created request context successfully. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Created request packet successfully, dstIP: 192.168.20.2, dstPort: 1812, VPN instance: --(public), socketFd: 149, pktID: 222. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Added packet socketfd to epoll successfully, socketFd: 149. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Mapped PAM item to RADIUS attribute successfully. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Got RADIUS username format successfully, format: 0. *Feb 15 09:55:18:759 2019 WX2560H RADIUS/7/EVENT: Added attribute user-name successfully, user-name: host/***.***. *Feb 15 09:55:18:760 2019 WX2560H RADIUS/7/EVENT: Filled RADIUS attributes in packet successfully. *Feb 15 09:55:18:760 2019 WX2560H RADIUS/7/EVENT: Composed request packet successfully. *Feb 15 09:55:18:760 2019 WX2560H RADIUS/7/EVENT: Created response timeout timer successfully. *Feb 15 09:55:18:760 2019 WX2560H RADIUS/7/PACKET: User-Name="host/***.***" Service-Type=Framed-User Framed-Protocol=PPP NAS-Identifier="WX2560H" NAS-Port=1 NAS-Port-Type=Wireless-802.11 NAS-Port- Calling-Station- Called-Station- Acct-Session- H3c-User-Vlan-Id=1 EAP-Message=0x0202002901686f73742f4d494e494e542d41524c344738532e636f72702e636f6e746f736f2e636f6d Message-Authenticator=0x00000000000000000000000000000000 Framed-MTU=1450 H3c-Ip-Host-Addr="0.0.0.0 c8:3d:d4:f0:79:99" NAS-IP-Address=192.168.10.252 H3c-Product- H3c-Nas-Startup-Timestamp=1550152201 *Feb 15 09:55:18:761 2019 WX2560H RADIUS/7/EVENT: Sent request packet successfully. *Feb 15 09:55:18:761 2019 WX2560H RADIUS/7/PACKET: 01 de 01 52 28 1f d8 f9 7f 1f 5e 09 8d 96 2e b3 a4 ae 38 6d 01 26 68 6f 73 74 2f 4d 49 4e 49 4e 54 2d 41 52 4c 34 47 38 53 2e 63 6f 72 70 2e 63 6f 6e 74 6f 73 6f 2e 63 6f 6d 06 06 00 00 00 02 07 06 00 00 00 01 20 09 57 58 32 35 36 30 48 05 06 00 00 00 01 3d 06 00 00 00 13 57 0b 56 4c 41 4e 49 44 3d 31 3b 1f 13 43 38 2d 33 44 2d 44 34 2d 46 30 2d 37 39 2d 39 39 1e 1c 33 38 2d 41 44 2d 42 45 2d 35 38 2d 44 36 2d 41 30 3a 73 65 72 76 69 63 65 31 2c 28 30 30 30 30 30 30 30 34 32 30 31 39 30 32 31 35 30 39 35 35 31 33 30 30 30 30 30 30 30 66 30 38 31 30 30 31 39 32 1a 0c 00 00 63 a2 85 06 00 00 00 01 4f 2b 02 02 00 29 01 68 6f 73 74 2f 4d 49 4e 49 4e 54 2d 41 52 4c 34 47 38 53 2e 63 6f 72 70 2e 63 6f 6e 74 6f 73 6f *Feb 15 09:55:18:762 2019 WX2560H RADIUS/7/PACKET: 2e 63 6f 6d 50 12 c0 d1 d1 27 48 01 81 26 ee 6d 04 de a5 c5 e2 db 0c 06 00 00 05 aa 1a 21 00 00 63 a2 3c 1b 30 2e 30 2e 30 2e 30 20 63 38 3a 33 64 3a 64 34 3a 66 30 3a 37 39 3a 39 39 04 06 c0 a8 0a fc 1a 13 00 00 63 a2 ff 0d 48 33 43 20 57 58 32 35 36 30 48 1a 0c 00 00 63 a2 3b 06 5c 65 72 09 *Feb 15 09:55:18:762 2019 WX2560H RADIUS/7/EVENT: Sent request packet and create request context successfully. *Feb 15 09:55:18:762 2019 WX2560H RADIUS/7/EVENT: Added request context to global table successfully. *Feb 15 09:55:18:762 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:20:466 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:20:466 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:221. *Feb 15 09:55:20:467 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 3, maxTries: 3. *Feb 15 09:55:22:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:22:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:222. *Feb 15 09:55:22:466 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 2, maxTries: 3. *Feb 15 09:55:23:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:23:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:221. *Feb 15 09:55:23:466 2019 WX2560H RADIUS/7/EVENT: Reached the maximum retries. *Feb 15 09:55:23:466 2019 WX2560H RADIUS/7/EVENT: Set status of server to block successfully. serverIP: 192.168.20.2, serverPort: 1812. *Feb 15 09:55:23:466 2019 WX2560H RADIUS/7/EVENT: Got next server failed. *Feb 15 09:55:23:466 2019 WX2560H RADIUS/7/EVENT: Sent reply error message to PAM. *Feb 15 09:55:23:467 2019 WX2560H RADIUS/7/EVENT: Sent reply message successfully. *Feb 15 09:55:23:467 2019 WX2560H RADIUS/7/EVENT: Received status of server changing event. *Feb 15 09:55:23:468 2019 WX2560H RADIUS/7/EVENT: Aaad sent notification about the change of server status to application process successfully. Server state: block. *Feb 15 09:55:23:640 2019 WX2560H RADIUS/7/EVENT: Application process reveived the notification about the change of server status from aaad process. Server state: block. *Feb 15 09:55:23:702 2019 WX2560H RADIUS/7/EVENT: Application process reveived the notification about the change of server status from aaad process. Server state: block. %Feb 15 09:55:23:768 2019 WX2560H DOT1X/5/DOT1X_WLAN_LOGIN_FAILURE: -Username=host/***.***-UserMAC=c83d-d4f0-7999-BSSID=38ad-be58-d6a0-SSID=service1-VLANID=1; A user failed 802.1X authentication. *Feb 15 09:55:23:967 2019 WX2560H RADIUS/7/EVENT: Application process reveived the notification about the change of server status from aaad process. Server state: block. *Feb 15 09:55:24:465 2019 WX2560H RADIUS/7/EVENT: Application process reveived the notification about the change of server status from aaad process. Server state: block. *Feb 15 09:55:25:466 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:25:466 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:222. *Feb 15 09:55:25:467 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 3, maxTries: 3. *Feb 15 09:55:28:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:28:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:222. *Feb 15 09:55:28:466 2019 WX2560H RADIUS/7/EVENT: Reached the maximum retries. *Feb 15 09:55:28:466 2019 WX2560H RADIUS/7/EVENT: Set status of server to block successfully. serverIP: 192.168.20.2, serverPort: 1812. *Feb 15 09:55:28:466 2019 WX2560H RADIUS/7/EVENT: Got next server failed. *Feb 15 09:55:28:466 2019 WX2560H RADIUS/7/EVENT: Sent reply error message to PAM. *Feb 15 09:55:28:467 2019 WX2560H RADIUS/7/EVENT: Sent reply message successfully. *Feb 15 09:55:28:467 2019 WX2560H RADIUS/7/EVENT: Received status of server changing event. *Feb 15 09:55:35:606 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Processing RADIUS authentication. *Feb 15 09:55:35:606 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Sent authentication request successfully. *Feb 15 09:55:35:606 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:35:606 2019 WX2560H RADIUS/7/EVENT: Got request data successfully, primitive: authentication. *Feb 15 09:55:35:606 2019 WX2560H RADIUS/7/EVENT: Getting RADIUS server info. *Feb 15 09:55:35:607 2019 WX2560H RADIUS/7/EVENT: Got RADIUS server info successfully. *Feb 15 09:55:35:607 2019 WX2560H RADIUS/7/EVENT: Created request context successfully. *Feb 15 09:55:35:607 2019 WX2560H RADIUS/7/EVENT: Created request packet successfully, dstIP: 192.168.20.2, dstPort: 1812, VPN instance: --(public), socketFd: 149, pktID: 90. *Feb 15 09:55:35:607 2019 WX2560H RADIUS/7/EVENT: Added packet socketfd to epoll successfully, socketFd: 149. *Feb 15 09:55:35:607 2019 WX2560H RADIUS/7/EVENT: Mapped PAM item to RADIUS attribute successfully. *Feb 15 09:55:35:608 2019 WX2560H RADIUS/7/EVENT: Got RADIUS username format successfully, format: 0. *Feb 15 09:55:35:608 2019 WX2560H RADIUS/7/EVENT: Added attribute user-name successfully, user-name: CORP\it01. *Feb 15 09:55:35:608 2019 WX2560H RADIUS/7/EVENT: Filled RADIUS attributes in packet successfully. *Feb 15 09:55:35:608 2019 WX2560H RADIUS/7/EVENT: Composed request packet successfully. *Feb 15 09:55:35:608 2019 WX2560H RADIUS/7/EVENT: Created response timeout timer successfully. *Feb 15 09:55:35:609 2019 WX2560H RADIUS/7/PACKET: User-Name="CORP\\it01" Service-Type=Framed-User Framed-Protocol=PPP NAS-Identifier="WX2560H" NAS-Port=1 NAS-Port-Type=Wireless-802.11 NAS-Port- Calling-Station- Called-Station- Acct-Session- H3c-User-Vlan-Id=1 EAP-Message=0x0201000e01434f52505c69743031 Message-Authenticator=0x00000000000000000000000000000000 Framed-MTU=1450 H3c-Ip-Host-Addr="0.0.0.0 c8:3d:d4:f0:79:99" NAS-IP-Address=192.168.10.252 H3c-Product- H3c-Nas-Startup-Timestamp=1550152201 *Feb 15 09:55:35:609 2019 WX2560H RADIUS/7/EVENT: Sent request packet successfully. *Feb 15 09:55:35:610 2019 WX2560H RADIUS/7/PACKET: 01 5a 01 1c 69 27 65 81 b1 8b 60 ae 9a ee a1 01 7c 20 47 6a 01 0b 43 4f 52 50 5c 69 74 30 31 06 06 00 00 00 02 07 06 00 00 00 01 20 09 57 58 32 35 36 30 48 05 06 00 00 00 01 3d 06 00 00 00 13 57 0b 56 4c 41 4e 49 44 3d 31 3b 1f 13 43 38 2d 33 44 2d 44 34 2d 46 30 2d 37 39 2d 39 39 1e 1c 33 38 2d 41 44 2d 42 45 2d 35 38 2d 44 36 2d 41 30 3a 73 65 72 76 69 63 65 31 2c 28 30 30 30 30 30 30 30 34 32 30 31 39 30 32 31 35 30 39 35 35 33 35 30 30 30 30 30 30 31 30 30 38 31 30 30 31 39 32 1a 0c 00 00 63 a2 85 06 00 00 00 01 4f 10 02 01 00 0e 01 43 4f 52 50 5c 69 74 30 31 50 12 70 d2 f9 e9 fa cb 67 1c 35 d5 48 e9 80 e6 5f ce 0c 06 00 00 05 aa 1a 21 00 00 63 a2 3c 1b 30 2e 30 2e 30 2e 30 20 63 38 3a 33 64 3a 64 34 3a 66 *Feb 15 09:55:35:610 2019 WX2560H RADIUS/7/PACKET: 30 3a 37 39 3a 39 39 04 06 c0 a8 0a fc 1a 13 00 00 63 a2 ff 0d 48 33 43 20 57 58 32 35 36 30 48 1a 0c 00 00 63 a2 3b 06 5c 65 72 09 *Feb 15 09:55:35:610 2019 WX2560H RADIUS/7/EVENT: Sent request packet and create request context successfully. *Feb 15 09:55:35:610 2019 WX2560H RADIUS/7/EVENT: Added request context to global table successfully. *Feb 15 09:55:35:610 2019 WX2560H RADIUS/7/EVENT: Processing AAA request data. *Feb 15 09:55:39:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:39:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:90. *Feb 15 09:55:39:466 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 2, maxTries: 3. *Feb 15 09:55:42:465 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:42:465 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:90. *Feb 15 09:55:42:466 2019 WX2560H RADIUS/7/EVENT: Retransmitting request packet, currentTries: 3, maxTries: 3. *Feb 15 09:55:45:466 2019 WX2560H RADIUS/7/EVENT: Response timed out. *Feb 15 09:55:45:466 2019 WX2560H RADIUS/7/EVENT: Found request context, dstIP: 192.168.20.2; dstPort: 1812; VPN instance: --(public); socketfd: 149; pktID:90. *Feb 15 09:55:45:467 2019 WX2560H RADIUS/7/EVENT: Reached the maximum retries. *Feb 15 09:55:45:467 2019 WX2560H RADIUS/7/EVENT: Set status of server to block successfully. serverIP: 192.168.20.2, serverPort: 1812. *Feb 15 09:55:45:467 2019 WX2560H RADIUS/7/EVENT: Got next server failed. *Feb 15 09:55:45:467 2019 WX2560H RADIUS/7/EVENT: Sent reply error message to PAM. *Feb 15 09:55:45:467 2019 WX2560H RADIUS/7/EVENT: Sent reply message successfully. %Feb 15 09:55:45:468 2019 WX2560H DOT1X/5/DOT1X_WLAN_LOGIN_FAILURE: -Username=CORP\it01-UserMAC=c83d-d4f0-7999-BSSID=38ad-be58-d6a0-SSID=service1-VLANID=1; A user failed 802.1X authentication. *Feb 15 09:55:45:468 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Processing RADIUS authentication. *Feb 15 09:55:45:468 2019 WX2560H RADIUS/7/EVENT: PAM_RADIUS: Fetched authentication reply-data successfully, resultCode: 3 *Feb 15 09:55:45:469 2019 WX2560H RADIUS/7/EVENT: Received status of server changing event. 




组网及组网描述:

拓扑如下



windows NPS Radius配置截图如下:












最佳答案

已采纳
粉丝:127人 关注:3人

 Retransmitting request packet, currentTries: 2, maxTries: 3. 

大致问题是在于AC发出了radius 认证请求报文 但是没有收到服务器的回应。

按照经验很容易发生的错误是在于radius认证的时候需要指定nas ip 在radius scheme里配置。也就是通过这个nas ip去收发radius报文与服务器通信,在你贴出的服务器配置上显示IP为192.168.30.1;那么AC上必须要用192.168.30.1去做radius报文收发作为nas ip。可以通过ping -a 192.168.30.1 AAA_IP 作为检测手段是否能通,另外中间网络不能开启端口拦截 比如防火墙设备ACL的策略,或者windows server自己的防火墙。


按照这个思路去判断,逐步解决。 

192.168.20.2是radius服务器,192.168.10.252是AC,192.168.30.1/2是AP。radius scheme 中的 nas-ip 应该是AC的地址还是AP的地址呢?

老池 发表时间:2019-02-15

nas-ip必须是AC 的地址

skylar 发表时间:2019-02-15

radius scheme rd01 primary authentication 192.168.20.2 key cipher $c$3$H/oG+QiqvYDHlrCjYQtLXoWoKXbOf9mSuU1N primary accounting 192.168.20.2 key cipher $c$3$4/xA5b5wob1GLTAt+J4pxJJf8NuaSzQOiYn2 key authentication cipher $c$3$bCmB/bA01ZFxZnpa1xxpBCLeIZnQ2uhhp4Ee key accounting cipher $c$3$NXsfRNwLjlhQw0YMKdmAgf2L2oQFVFGGIGpp user-name-format without-domain nas-ip 192.168.10.252 # radius dynamic-author server client ip 192.168.20.2 key cipher $c$3$GRXfDjXnWehlelAEC7r8/UOIFw9OYwzfwvZd # domain dm01 authentication lan-access radius-scheme rd01 authorization lan-access radius-scheme rd01 accounting lan-access radius-scheme rd01

老池 发表时间:2019-02-15
回复skylar:

那我配置没错啊

老池 发表时间:2019-02-15

具体原因看不出来,只知道服务器没有回应,至于服务器为什么没回应就不清楚了,因为涉及第三方服务器,我们只清楚无线侧设备的行为,微软服务器的行为不清楚啊,只能再多检查配置了

skylar 发表时间:2019-02-15
回复老池:

nas-ip 192.168.10.252 你这个是AC上配置的nas ip;但是你的NPS上配置的IP地址难道不是192.168.30.1? 我看截图是这个IP 应该改成192.168.10.252 意思是 nps在确认谁给他发radius报文。

肉夹馍再了解一下 发表时间:2019-02-15

最终的问题确认了,是windows radius配置中的radius客户端添加的不对,之前添加的是ap的地址,改为AC的地址后验证成功。 之所以添加的是AP的地址,是因为之前使用UBNT的设备配置时添加的是AP的地址。

老池 发表时间:2019-02-18
2 个回答
skylar 九段
粉丝:42人 关注:0人

首先我们看不到你说的配置附件。从debug看AC 发起了认证请求,但是服务器未回应导致的认证失败


嗯,这个信息看到了,但没找到服务器侧是什么问题

老池 发表时间:2019-02-15
老池 二段
粉丝:1人 关注:9人

debugging提交后为啥行都乱了呢?

编辑答案

你正在编辑答案

如果你要对问题或其他回答进行点评或询问,请使用评论功能。

分享扩散:

提出建议

    +

亲~登录后才可以操作哦!

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作

举报

×

侵犯我的权益 >
对根叔社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 pub.zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明