10-16-04 02:25 AM
Sounds like a firmware issue, update to the latest firmware that might help
--
========================================
=====
This posting is provided "AS IS" with no warranties, and confers no
rights.
========================================
=====
"Borja Carrero via AdminLife" <anonymous@adminlife.com> wrote in message
news:%2387JIrPjEHA.3568@TK2MSFTNGP10.phx.gbl...
> Hy everybody,
>
> I?ve managed to make the MS solution work with an IAS from Windows Server
> 2K3 but not with W2K, at least for the time being.
>
> The test scenario is the following:
>
> * Windows 2K SP4 client with Authentication tab enabled and configured for
> PEAP MS-CHAP v2
> * Avaya AP-3 running firmware 2.4.5 (maybe I need to update to version
> 2.4.11, I think this is where the problem might lie at).
> * Proxim AP-2000 running firmware 2.4.11 (this is === to the Avaya model,
> in fact I think it?s the same HW + SW)
> * IAS radius running on W2K server with an Active Directory PDC service in
> the same PC.
>
> Now, the problem is that the PEAP authentication goes on perfectly,
> according to traces taking in both the client and the IAS but, somehow,
> full connectivity doesn?t take place. The error varies from:
> * DHCP server not getting the DHCP request (if you fix the IP address then
> you have connectivity)
> * Authentication success, key exchange but then no connectivity, not even
> fixing IP address.
>
> If we disable the 802.1x security escheme on the APs, the problems
> dissappears.
>
> Anyone can give me any pointers?
>
>
>
>
> --------------------------------
> From: Borja Carrero
>
> -----------------------
> Posted by a user from AdminLife (http://www.adminlife.com/)
>
> <Id>G2E7qWAtu0u169DgAnCS3A==</Id>
[ Post a follow-up to this message ]
|