Strange problem establishing connection - only when XP boots

Hi.
I've searched for solutions to this, and except for one other person
reporting the same symptoms, I've come up with nothing...

I'm using:

802.11g Access point: Belkin Wireless Access Point (802.11g), running
WPA-PSK.
Client: Dell Inspiron 5150, with TrueMobile 1300, on XP with WPA
hotfix.

[Both the radios above are Broadcom based]

The symptoms:

On startup, background and desktop icons come up, system tray icons
don't, and the hard disk activity light flickers every couple of
seconds.
Windows explorer is hung while this is happening, but some programs
can run.
It is 'hung' this way, for about 2 minutes.
Finally the wireless network icon comes up and everything finishes
booting
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

Has anyone seen this before?

Cheers,

Laz.

That's exactly the behaviour I'm experiencing, although I occasionally also
have problems with DHCP assigning an address. (Even when I assign an IP
address without DHCP, I get a number of tcpip messages every 5 seconds
saying that it discovered a new interface.)

It would seem that: (a) there's a flaw in the implementation of WPA in
Windows XP; or (b) Windows XP simply needs an exceptionally long period of
time to bring up all the services necessary for a WPA connection.



"Laz" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi.
> I've searched for solutions to this, and except for one other person
> reporting the same symptoms, I've come up with nothing...
>
> I'm using:
>
> 802.11g Access point: Belkin Wireless Access Point (802.11g), running
> WPA-PSK.
> Client: Dell Inspiron 5150, with TrueMobile 1300, on XP with WPA
> hotfix.
>
> [Both the radios above are Broadcom based]
>
> The symptoms:
>
> On startup, background and desktop icons come up, system tray icons
> don't, and the hard disk activity light flickers every couple of
> seconds.
> Windows explorer is hung while this is happening, but some programs
> can run.
> It is 'hung' this way, for about 2 minutes.
> Finally the wireless network icon comes up and everything finishes
> booting
> 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
>
> Has anyone seen this before?
>
> Cheers,
>
> Laz.

I also have this problem with the truemobile 1300.
A work around is to disable the device before you shutdown.
After rebooting, enable the device. No more delays.


On Mon, 29 Sep 2003 14:52:24 -0400, "Peter Copeland"
<(E-Mail Removed)> wrote:

>That's exactly the behaviour I'm experiencing, although I occasionally also
>have problems with DHCP assigning an address. (Even when I assign an IP
>address without DHCP, I get a number of tcpip messages every 5 seconds
>saying that it discovered a new interface.)
>
>It would seem that: (a) there's a flaw in the implementation of WPA in
>Windows XP; or (b) Windows XP simply needs an exceptionally long period of
>time to bring up all the services necessary for a WPA connection.
>
>
>
>"Laz" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed). com...
>> Hi.
>> I've searched for solutions to this, and except for one other person
>> reporting the same symptoms, I've come up with nothing...
>>
>> I'm using:
>>
>> 802.11g Access point: Belkin Wireless Access Point (802.11g), running
>> WPA-PSK.
>> Client: Dell Inspiron 5150, with TrueMobile 1300, on XP with WPA
>> hotfix.
>>
>> [Both the radios above are Broadcom based]
>>
>> The symptoms:
>>
>> On startup, background and desktop icons come up, system tray icons
>> don't, and the hard disk activity light flickers every couple of
>> seconds.
>> Windows explorer is hung while this is happening, but some programs
>> can run.
>> It is 'hung' this way, for about 2 minutes.
>> Finally the wireless network icon comes up and everything finishes
>> booting
>> 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
>>
>> Has anyone seen this before?
>>
>> Cheers,
>>
>> Laz.
>
>
>