Sign in with
Sign up | Sign in
Your question

WPA with 802.1x boot time issue, machine authentication

Last response: in Wireless Networking
Share
Anonymous
a b F Wireless
August 13, 2004 11:55:19 AM

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

Hi folks, following problem:

Config: Intel 2200BG Chipset in Acer Notebooks (WPA w. 802.1x PEAP), Netgear
FWG114P WPA Access Point, W2K3 Server with IAS

I am attempting to implement 802.1x on wireless using PEAP. The problem that
I am seeing is that machine authentication is very slow to be performed by
Windows XP clients. The machine authentication does not even start until at
least 30 seconds after the Windows login GINA is displayed. This is
frustrating as the machine will not be provided an IP on the network until
machine authentication passes. If the machine is not on the network with the
user attempts to login then the login will be local, no DC will be
contacted, and any login script that this user has will not run, also no
Group Policies as Computer Software Installations...

User Authentication works perfectly, but after logon. When I log off, then
computer authentication works also. After Standby or Hibernate it also takes
up to 3 Minutes for the 2200BG to rescan the wireless connection and
reauthenticate.

Hotfix (KB826942) is installed, also the Group Policy Setting "Always wait
for the network at computer startup", also the Wireless Settings on 2200BG
"authenticate as computer".

BTW, WPA-PSK works perfectly, but that's not what I want...

Please help, thanks

Bernhard
Anonymous
a b F Wireless
August 19, 2004 11:18:24 AM

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

Have you disabled broadcast ssid on the access points? I have seen slow
connection time with 2200bg cards when it has to look for the ssid. Does
this same issue happen with different wireless client hardware?

--
RUSSELL GROTEWOLD
"Berhard Wagner" <bernhard_wagner@hotmail.com> wrote in message
news:eXnDfoPgEHA.3428@TK2MSFTNGP10.phx.gbl...
> Hi folks, following problem:
>
> Config: Intel 2200BG Chipset in Acer Notebooks (WPA w. 802.1x PEAP),
Netgear
> FWG114P WPA Access Point, W2K3 Server with IAS
>
> I am attempting to implement 802.1x on wireless using PEAP. The problem
that
> I am seeing is that machine authentication is very slow to be performed by
> Windows XP clients. The machine authentication does not even start until
at
> least 30 seconds after the Windows login GINA is displayed. This is
> frustrating as the machine will not be provided an IP on the network until
> machine authentication passes. If the machine is not on the network with
the
> user attempts to login then the login will be local, no DC will be
> contacted, and any login script that this user has will not run, also no
> Group Policies as Computer Software Installations...
>
> User Authentication works perfectly, but after logon. When I log off, then
> computer authentication works also. After Standby or Hibernate it also
takes
> up to 3 Minutes for the 2200BG to rescan the wireless connection and
> reauthenticate.
>
> Hotfix (KB826942) is installed, also the Group Policy Setting "Always wait
> for the network at computer startup", also the Wireless Settings on 2200BG
> "authenticate as computer".
>
> BTW, WPA-PSK works perfectly, but that's not what I want...
>
> Please help, thanks
>
> Bernhard
>
>
>
Anonymous
a b F Wireless
August 27, 2004 1:17:36 PM

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

Have you managed to solve the slow login problem?

I am having the same issue where the latency in receiving a DHCP
address causes the problem of no login script and therefore no shared
drive access.

I am using XP, Cisco PCMCIA, Cisco Aironet 1230 A/B, W2000 IAS, W2000
AD.

Any help is greatly appreciated.

Kim



--
bebrox
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message953040.html
!