If you had said this at the start, and posted the debug log, you would have solved the problem a long time ago. This is even in the FAQ: http://wiki.freeradius.org/FAQ#The_NAS_seems_to_ignore_the_reply_of_the_radi... Alan DeKok. Alan, As you said, I tried with the option -i : radiusd --i <ip_address_radius server> -X But still i get the below error message at the radius server end, only one NIC is active now on the server. --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 192.168.0.1:4754 , id=119, length=151 Sending duplicate reply to client dlink:4754 - ID: 119 Re-sending Access-Accept of id 219 to 192.168.0.1 port 4754 On the client side MSVPN dialer interface, i see the error message: "Error 718: the connection was terminated becasue the remote computer didnt respond in timely manner". Thanks for your patience and co-operation.
"Karthik R" <kartthikr@gmail.com> wrote:
But still i get the below error message at the radius server end, only one NIC is active now on the server.
Then the problem isn't in the RADIUS server, is it? The server is responding to the NAS, but for some reason, the NAS isn't receiving the packet, or is discarding the packet. It's time to start using 'tcpdump' to see where the packets are going. Also look at firewall rules. But there's nothing more you can do to FreeRADIUS to fix the problem. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Karthik R