Problems with Captive Portal authentication using Radius + Windows Server 2003
-
Hello,
I'm currently using version 2.0-RC3, until two days ago was working fine Captive Portal authentication with radius server windows server 2003. But today, when i try to access it asks Captive Portal username and password normally. But after a few minutes he again asked the same authenticated credentials. I looked in the event log of the radius server and always get the following error Message: "The malformed RADIUS message was received from client pfsenseprod. The date is the RADIUS message."
Any idea how to solve this problem?
-
Most common cause of that would be a mismatched secret, or maybe the IP changed on one side or the other. If you changed nothing on the firewall side and it's doing that, something changed on the RADIUS server.
http://technet.microsoft.com/en-us/library/dd316110%28WS.10%29.aspx
-
I've been having captive portal problems in the last few days, too!
Did you update from the July 1st to July 4th build?
-
I've been having captive portal problems in the last few days, too!
Did you update from the July 1st to July 4th build?
Jonalport,
I have two servers pfSense 2.0-RC3 on my environment.
- pfSense 2.0-RC3 built on Tue Apr 4 16:48:37 EDT 2011 (it has problems with my radius server).
- pfSense 2.0-RC3 built on Tue Jun 28 21:28:47 EDT 2011 (this i have no problems).
I did more tests using the same settings on both servers using pfsense captive portal to authenticate with the same radius server (win 2k3). In both tests only the server with the built (on Tue Jun 28) ancient works without problems.
What was your last update?
-
cmb,
Other information: use the same configuration of the failed server to authenticate users via vpn radius and they do not lose connection, now in the captive portal users need to authenticate again and that error Message appears in the server log radius.
-
Since I updated from July 1st build to July 4th build I've seen the CP wanting re-authentication every few minutes. I've rolled that back to July 1st now and all seem OK again.
-
Another user reported the same problem:
http://forum.pfsense.org/index.php/topic,38618.0.html
-
Fixed in newer snapshots.