WPA and domain login problem

(Further to my earlier threads, I started thinking that I was experiencing
overlapping problems and decided to post one dealing simply with my domain
login issue.)

I am running WIndows XP Professional on a Dell Inspiron 4150 laptop and
using a WPC54G card to connect to a Linksys WRT54G (these problems also
occur with a Belkin wireless card, as well as a DLINK router). The WRT54G
is essentially set up as an access point, with one port of its switch
connnected to our office network. We have a domain set up on our network.
The card and router have the most up-to-date driver and firmware.

I do not have difficulties with this card when I use it in unencrypted mode.
In that mode, I am able to login to the domain after a reboot and I always
obtain an IP address through DHCP.

However, when I enable WPA security, I am experiencing some problems. The
WZC (updated version) is properly configured and is able to associate with
the WRT54G. I have had some issues re intermittent dropping of connection,
but my main concern right now relates to problems attempting to log onto the
domain after a reboot. In WPA mode, it simply will not do it.

In short, after I reboot, my login window comes up normally. The activity
light of the WPC54G lights up briefly every couple of seconds. This appears
to follow a regular pattern of on-pause-on-pause, i.e. it doesn't have the
regular flickering of normal network traffic. When I enter my password, the
login hangs for a couple of minutes before finally continuing (instead of
the usual few seconds on a normal wired login or an unencrypted wireless
login). After the login completes, the WPC54G does not have a proper IP
address from the DHCP server (although "renewing" the connection can solve
that problem). The card has either a 0.0.0.0 address or a 169.254.xxx.xxx
address. Interestingly, if I manually configure the card for static IP
addresses, I do not have this problem on boot up.

After doing an internet search, I noticed that previous drivers for the
WPC11 had similar problems with domain logins on Windows XP and Windows 2000
(see:
http://www.linksys.com/download/vert...60503_wpa.txt).
As well, I noticed that a domain login issue for Windows 2000 was resolved
for the WPC54G (see: http://www.linksys.com/download/vertxt/wpc54g_ver.txt).
It seems that there continues to be a problem with domain logins with this
card, at least when using WPA-PSK encryption. Perhaps, as with the earlier
problem that WPC11 had, the card is not being properly activated prior to
domain login.

Has anybody else experienced this problem? Has anyone been successful in
using this card in WPA-PSK mode to log on to an NT domain?

Regards,

Peter

Further to my previous post, I have looked at my system event log and found
the following warning from the DHCP service repeatedly occurs at startup:

"Your computer was not able to renew its address from the network (from the
DHCP Server) for the Network Card with network address 000625426631. The
following error occurred: The operation was canceled by the user. . Your
computer will continue to try and obtain an address on its own from the
network address (DHCP) server."


My ntbtlog (boot log) shows that the system started booting at 2:51:13 pm.
This DHCP warning appears 26 times between 2:52:01and 2:54:07. At 2:54:07,
my attempt at logging in fails, and I get an error from NETLOGON as follows:
"No Domain Controller is available for domain GHL due to the following:
There are currently no logon servers available to service the logon request.
Make sure that the computer is connected to the network and try again. If
the problem persists, please contact your domain administrator." After the
NETLOGON error, I get another 19 occurrences of the DHCP warning, which stop
at 2:55:43.

The DHCP warnings (both before and after the NETLOGON error) follow (and are
followed by) information messages from TCPIP stating that "The system
detected that network adapter \DEVICE\TCPIP_{details omitted} was connected
to the network, and has initiated normal operation over the network
adapter."

Immediately after the last DHCP warning, I get a number of entries in the
system event log from "Service Control Manager" advising that the following
services had been sent a "start control" and then had "entered the running
state": Terminal Services, Network Connections service, Telephony Service,
Remote Access Connection Manager service, SymEvent service, Norton
Anti-virus related services, SSDP Discovery Service, Network Location
Awareness service.

Clearly, the problem I am having with very long hanging upon login is
related to the DHCP service not being successful when WPA encryption is
enabled. It is strange that the warning message describes the operation
being cancelled by the user, as I am doing nothing but waiting patiently for
my system to log on.

Regards,

Peter

P.S. A repair installation of XP Pro SP1 has, at least for the time being,
seemed to correct problems I having post-login with DHCP. For example, now
when I repeated try to "repair" my wireless network connection, the result
is almost immediately successful.

"Peter Copeland" <(E-Mail Removed)> wrote in message
news:KFn7b.2777$(E-Mail Removed)...
> (Further to my earlier threads, I started thinking that I was experiencing
> overlapping problems and decided to post one dealing simply with my domain
> login issue.)
>
> I am running WIndows XP Professional on a Dell Inspiron 4150 laptop and
> using a WPC54G card to connect to a Linksys WRT54G (these problems also
> occur with a Belkin wireless card, as well as a DLINK router). The WRT54G
> is essentially set up as an access point, with one port of its switch
> connnected to our office network. We have a domain set up on our network.
> The card and router have the most up-to-date driver and firmware.
>
> I do not have difficulties with this card when I use it in unencrypted
mode.
> In that mode, I am able to login to the domain after a reboot and I always
> obtain an IP address through DHCP.
>
> However, when I enable WPA security, I am experiencing some problems. The
> WZC (updated version) is properly configured and is able to associate with
> the WRT54G. I have had some issues re intermittent dropping of
connection,
> but my main concern right now relates to problems attempting to log onto
the
> domain after a reboot. In WPA mode, it simply will not do it.
>
> In short, after I reboot, my login window comes up normally. The activity
> light of the WPC54G lights up briefly every couple of seconds. This
appears
> to follow a regular pattern of on-pause-on-pause, i.e. it doesn't have the
> regular flickering of normal network traffic. When I enter my password,
the
> login hangs for a couple of minutes before finally continuing (instead of
> the usual few seconds on a normal wired login or an unencrypted wireless
> login). After the login completes, the WPC54G does not have a proper IP
> address from the DHCP server (although "renewing" the connection can solve
> that problem). The card has either a 0.0.0.0 address or a 169.254.xxx.xxx
> address. Interestingly, if I manually configure the card for static IP
> addresses, I do not have this problem on boot up.
>
> After doing an internet search, I noticed that previous drivers for the
> WPC11 had similar problems with domain logins on Windows XP and Windows
2000
> (see:
>
http://www.linksys.com/download/vert...60503_wpa.txt).
> As well, I noticed that a domain login issue for Windows 2000 was resolved
> for the WPC54G (see:
http://www.linksys.com/download/vertxt/wpc54g_ver.txt).
> It seems that there continues to be a problem with domain logins with this
> card, at least when using WPA-PSK encryption. Perhaps, as with the
earlier
> problem that WPC11 had, the card is not being properly activated prior to
> domain login.
>
> Has anybody else experienced this problem? Has anyone been successful in
> using this card in WPA-PSK mode to log on to an NT domain?
>
> Regards,
>
> Peter
>
>
>

P.P.S. I spoke too soon about the DHCP issue being resolved post-login. I
still have the connection dropping and being unable to renew the address.
My connection is still cutting out at regular intervals (probably associated
with the DHCP renewal period) and occasionally not getting an assigned IP
address.

"Peter Copeland" <(E-Mail Removed)> wrote in message
news:Cxq7b.2814$(E-Mail Removed)...
> Further to my previous post, I have looked at my system event log and
found
> the following warning from the DHCP service repeatedly occurs at startup:
>
> "Your computer was not able to renew its address from the network (from
the
> DHCP Server) for the Network Card with network address 000625426631. The
> following error occurred: The operation was canceled by the user. . Your
> computer will continue to try and obtain an address on its own from the
> network address (DHCP) server."
>
>
> My ntbtlog (boot log) shows that the system started booting at 2:51:13 pm.
> This DHCP warning appears 26 times between 2:52:01and 2:54:07. At
2:54:07,
> my attempt at logging in fails, and I get an error from NETLOGON as
follows:
> "No Domain Controller is available for domain GHL due to the following:
> There are currently no logon servers available to service the logon
request.
> Make sure that the computer is connected to the network and try again. If
> the problem persists, please contact your domain administrator." After
the
> NETLOGON error, I get another 19 occurrences of the DHCP warning, which
stop
> at 2:55:43.
>
> The DHCP warnings (both before and after the NETLOGON error) follow (and
are
> followed by) information messages from TCPIP stating that "The system
> detected that network adapter \DEVICE\TCPIP_{details omitted} was
connected
> to the network, and has initiated normal operation over the network
> adapter."
>
> Immediately after the last DHCP warning, I get a number of entries in the
> system event log from "Service Control Manager" advising that the
following
> services had been sent a "start control" and then had "entered the running
> state": Terminal Services, Network Connections service, Telephony Service,
> Remote Access Connection Manager service, SymEvent service, Norton
> Anti-virus related services, SSDP Discovery Service, Network Location
> Awareness service.
>
> Clearly, the problem I am having with very long hanging upon login is
> related to the DHCP service not being successful when WPA encryption is
> enabled. It is strange that the warning message describes the operation
> being cancelled by the user, as I am doing nothing but waiting patiently
for
> my system to log on.
>
> Regards,
>
> Peter
>
> P.S. A repair installation of XP Pro SP1 has, at least for the time being,
> seemed to correct problems I having post-login with DHCP. For example,
now
> when I repeated try to "repair" my wireless network connection, the result
> is almost immediately successful.
>
> "Peter Copeland" <(E-Mail Removed)> wrote in message
> news:KFn7b.2777$(E-Mail Removed)...
> > (Further to my earlier threads, I started thinking that I was
experiencing
> > overlapping problems and decided to post one dealing simply with my
domain
> > login issue.)
> >
> > I am running WIndows XP Professional on a Dell Inspiron 4150 laptop and
> > using a WPC54G card to connect to a Linksys WRT54G (these problems also
> > occur with a Belkin wireless card, as well as a DLINK router). The
WRT54G
> > is essentially set up as an access point, with one port of its switch
> > connnected to our office network. We have a domain set up on our
network.
> > The card and router have the most up-to-date driver and firmware.
> >
> > I do not have difficulties with this card when I use it in unencrypted
> mode.
> > In that mode, I am able to login to the domain after a reboot and I
always
> > obtain an IP address through DHCP.
> >
> > However, when I enable WPA security, I am experiencing some problems.
The
> > WZC (updated version) is properly configured and is able to associate
with
> > the WRT54G. I have had some issues re intermittent dropping of
> connection,
> > but my main concern right now relates to problems attempting to log onto
> the
> > domain after a reboot. In WPA mode, it simply will not do it.
> >
> > In short, after I reboot, my login window comes up normally. The
activity
> > light of the WPC54G lights up briefly every couple of seconds. This
> appears
> > to follow a regular pattern of on-pause-on-pause, i.e. it doesn't have
the
> > regular flickering of normal network traffic. When I enter my password,
> the
> > login hangs for a couple of minutes before finally continuing (instead
of
> > the usual few seconds on a normal wired login or an unencrypted wireless
> > login). After the login completes, the WPC54G does not have a proper IP
> > address from the DHCP server (although "renewing" the connection can
solve
> > that problem). The card has either a 0.0.0.0 address or a
169.254.xxx.xxx
> > address. Interestingly, if I manually configure the card for static IP
> > addresses, I do not have this problem on boot up.
> >
> > After doing an internet search, I noticed that previous drivers for the
> > WPC11 had similar problems with domain logins on Windows XP and Windows
> 2000
> > (see:
> >
>
http://www.linksys.com/download/vert...60503_wpa.txt).
> > As well, I noticed that a domain login issue for Windows 2000 was
resolved
> > for the WPC54G (see:
> http://www.linksys.com/download/vertxt/wpc54g_ver.txt).
> > It seems that there continues to be a problem with domain logins with
this
> > card, at least when using WPA-PSK encryption. Perhaps, as with the
> earlier
> > problem that WPC11 had, the card is not being properly activated prior
to
> > domain login.
> >
> > Has anybody else experienced this problem? Has anyone been successful
in
> > using this card in WPA-PSK mode to log on to an NT domain?
> >
> > Regards,
> >
> > Peter
> >
> >
> >
>
>

Hi Peter,

I have similar symptoms, with different equipment. (and no domain
login)
Maybe this information can elicit some help from others more
knowledgeable:

I'm using:

Belkin Wireless Access Point (802.11g), running WPA-PSK.
Dell Inspiron 5150, with TrueMobile 1300, XP.
[Both the radios above are Broadcom based]

The symptoms:

On startup, activity light flickers every couple of seconds.
Though windows comes up, none of the icons do.
It is 'hung' this way, for about 2 minutes.
Finally the wireless network icon comes up and everything boots
quickly.
Once it is up, the network is working fine (DHCP assigned IP worked).

Looking at the Events log for the system, I see a repeated cycle (for
the entire two minues that it is hung) of:
tcpip - discovered new interface
dhcp - failed, cancelled by user

The strange part:

The laptop is dual-boot, both to XP Professional installations.
They were both installed in exactly the same way.
I don't recall any differences or errors.
BUT one of them has the above problems, the other works FINE!!!
I can not see a difference between them, and it is driving me crazy.

What I've tried:

Complete reinstallation of XP Professional SP1 (but no additional
software)
Install WPA patch
Install wireless drivers
..... No good!

Cheers,

Laz.