Microsoft IAS Patch to Correct Very Slow RADIUS/802.1X Aut..

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

We are running Microsoft IAS (on top of Windows Server 2003) as our
RADIUS server to authenticate wireless/802.11 connections.

A colleague has informed me that there is a patch available that fixes
an intermittent problem where machines sometimes take a very long time
to authenticate via 802.1X/EAP.

As I understand things, this patch (hotfix?) will eventually come out
for free in a service pack but is currently available for $250.

We need the patch now and are thus willing to pay the $250. However,
we have been unable to re-locate the patch (and/or knowledgebase
article) on Microsoft's web site, and the colleague in question is
temporarily out of the country.

Can anyone point us in the right direction?

Thanks,

Jeff

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Will do--thanks for the offer of help Steve. It looks like we need
patch #883659, however, and another colleague has in fact obtained it
this morning.

Jeff





On Tue, 04 Jan 2005 22:20:41 -0800, Steve Riley [MSFT]
<steriley@microsoft.com> wrote:

>Jeff: please write to me from your real email address. I can help you with
>this. Thanks.
>
>Steve Riley
>steriley@microsoft.com
>
>
>
>> We are running Microsoft IAS (on top of Windows Server 2003) as our
>> RADIUS server to authenticate wireless/802.11 connections.
>>
>> A colleague has informed me that there is a patch available that fixes
>> an intermittent problem where machines sometimes take a very long time
>> to authenticate via 802.1X/EAP.
>>
>> As I understand things, this patch (hotfix?) will eventually come out
>> for free in a service pack but is currently available for $250.
>>
>> We need the patch now and are thus willing to pay the $250. However,
>> we have been unable to re-locate the patch (and/or knowledgebase
>> article) on Microsoft's web site, and the colleague in question is
>> temporarily out of the country.
>>
>> Can anyone point us in the right direction?
>>
>> Thanks,
>>
>> Jeff
>>
>