(RADIATOR) radiator and windows 2000 RRAS

Hugh Irvine hugh at open.com.au
Fri May 20 17:58:10 CDT 2005


Salut Stephane -

As always we will need to see a copy of your configuration file and a  
trace 4 debug showing what is happening so we can try to understand  
the problem.

regards

Hugh


On 20 May 2005, at 21:08, DELORT Stephane wrote:

> Re,
>
>
> -----Message d'origine-----
> De : Hugh Irvine [mailto:hugh at open.com.au]
> Envoyé : vendredi 20 mai 2005 10:16
> À : DELORT Stephane
> Cc : radiator at open.com.au
> Objet : Re: (RADIATOR) radiator and windows 2000 RRAS
>
>
>
>
>> Salut Stephane -
>>
>
>
>> Ooops - my apologies - I didn't notice this typo.
>>
> You're welcome, is there a command line test program just like in  
> samba, "testparm" to check the syntax ?
>
>
>> As for wired connections, there is no difference compared to wireless
>> connections, so you should not have any difficulty.
>>
>
>
> I thought so, but I can't get it to work.
> On the same network I have :
> - Active Directory (windows advanced)   [192.168.0.2]
> - Radiator and RRAS (on the same computer) [192.168.0.3]
> - A windows XP with SP2 [192.168.0.8]
>
> I tried 2 strategies (if I can call it that):
>
> 1) Create a VPN between the supplicant (XP) and Radiator.
>
> I use the default windows VPN client and it worked fine with MSCHAP  
> V2.
> Reading articles throughout the web, it appears that PEAP will only  
> be available for VPN with Longhorn (in 2050 ?).
>
> 2) Use windows XP network connection authentication feature.
> Since windows XP1, when you right click on a network connection,  
> you an "Authentication" tab. There I choosed PEAP and MSchap V2. I  
> did not see any text box to lead the requests toward a specific  
> RRAS/NAS/Radius.
> Indeed, it would have been too much beautiful if it had worked so  
> easily.
> Once I activate the network connection everything works as if I did  
> nothing and there is no authentication carried out.
> Did someone make it work ?
>
> Beside, I know that this kind of question is more related to  
> Windows then to Radiator. Thus, I am sure it would help anyone  
> trying to test a radius server on a wire network before coming to  
> the radio.
> I tried funk odyssey and Aegis client but both are only able to  
> work with wireless network.
>
> Thanks in advance to any help clearing this problem,
>
> regards,
> Stéphane
>
>
>
>
>
>
>
>
>> regards
>>
>
>
>> Hugh
>


NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list