I dont know which type of radius server are you using.
You have both to register the dll on the client and to have a working radius
server at the other end. the client does not talk directly to the radius
server but rather to the authenticator using eapol. in the WLAN case the
authenticator runs in the access point. It will translate the eapol messages
into radius messages and forward them to the remote server.
When starting the authentication, the radius server send a start message to
the client. this message carries a proposed type of authentication which
may not correspond to the one wanted by the client. the client has the
possibility to send back a Nak message to suggest another authentication
scheme. If the radius server supports this scheme (and the nak) , it will
send back another start message with the wanted authentication type.
if the radius server does not support the scheme you are using the only
messages you will exchange is the identity going to the server, followed by
the start from the radius, and possibly a nak from your client. You won't go
further.
The use of the tracing facility of the radius server or sniffing of the
packets exchanged is useful to understand what is happening.
regards
Denis
"Tarundeep Singh Kalra" <tkalra at gric dot com> a écrit dans le message de
news: eQLxyPhk...@TK2MSFTNGP09.phx.gbl...