Symptoms: MA5200 enables L2 web authentication services, and one external portal server is configured; the authentication policy is radius none. However, users drop offline after some seconds.
1. The client can prompt the web forced authentication page; enter the username and password, and the authentication succeeds, indicating that the configuration is normal.
2. Check the offline reasons, and it is because WEB AFF_ACK_AUTH timeout. It may be caused by MA5200F does not receive the AFF_ACK_AUTH from portal server.
3. Check the packet interaction process between MA5200F and portal server, and portal server does not respond the packet above in fact.
4. At the portal server, check the packet interacting process; before MA5200F sends the authentication success packet to potal server,the portal server has returned the timeout failure packet to MA5200F. In other words, when MA5200F sends the authentication success packet for users to portal server, the portal server has thought it as timeout (more than 5 seconds).
5.The authentication policy of users is radius none, and the radius server is down; MA5200F sets the times for retransmission of radius packets to 3, and the interval to 3 seconds. When the radius server does not respond the authentication reqeust from MA5200F, it has to take 9s to turn to non-authentication.
6. Up to now, the problem is located. The radius server is in down state, and the portal server sends the username and password to MA5200F, but MA5200F will wait 9s and then transmits authentication success packet to portal server. However, the portal server thinks it timeout.
7. Adjust the time for non-authentication at MA5200F if radius packet is not responded, and make it less than the time that the portal server thinks as timeout when MA5200F returns the authentication success packet. Test it again, and users can access network.
1. The configuration is problematic.
2. MA5200F cannot cooperate well with portal and radius servers.
3. The client is problematic.