WiFi "Limited or no connectivity" issues (XPSP2)

As I understand it, the "Connected" but "Limited or no connectivity" status
is active when there _is _an established "physical" connection between the
computer and the router - but _before_ the WPA-key has been sent (or
acknowledged?).

When I shutdown the system it issues Info Msg 4201 "The system detected that
network adapter xxx was connected to the network and has initiated normal
operation over the network adapter". It is stated elsewhere that the msg is
issued when the adapter is "enabled _or_disabled" which indicates that
"normal operation" should be understood as "no operation" in this case. This
is confusing, at least ;-)

Upon startup the same infoMsg is issued twice, 45 seconds apart, but the
internet connection does not get up. And concurrent with the second message,
a warning 1003 is issued. "Your computer was not able to renew its adress
from the network... cancelled by the user... will continue to try"

BUT, a) it has a fixed adress already (so it should not be renewed in the
first place), b) the user (me) has not interferred in any way (so, what user
was that, actually).

43 seconds later it makes another try, which results in Warning 1008, with
similar content asbefore "Your computer was not able... semaphore timeout...
willl continue to try".

3 second later Dhcp has obviously given up getting the adress over the
network and assigned it an entirely new adress of 169.254.75.111 (despite the
fixed one, which is different).

So now the computer is "Connected" but with "...no connectivity" and the
wrong IP adress.

I have to resolve this situation by manually disconnecting, and then
reconnect again. Upon reconnect the WPA-key is being shown to me (in a sense,
because only stars are shown ;-) which I then "OK" and send to the router.
After that the link is up.

I _assume_ that the problem is that the WPA-key is not sent (or
acknowledged) as it should on the automatic connection tries during the boot
sequence.

So my big question is:
Q1: What can I do to make the system establish the fully "connected"
connection by itself during the boot.

Curiosity questions are e.g...
Q2: Isn't there some logical error when the "connected but not connected"
state makes the system forget that the IP adress is fixed and should not be
retrieved from the network.

Q3: Is it really proper to issue a msg stating that the adapter "was
connected to the network" and that the system has "initiated normal
operation" when in fact the adapter has been disconnected from the network
because it was disabled because of the shutdown.

Q4:Why can't the system on its own identify this "connected but not
connected" situation and re-establish the connection automatically, whithout
my intervention?

I should stress that this computer has a WiFi network connection only. It
does have an Ethernet cable adapter too, but no cable is connected to it and
the system makes no attempts to use it (at least none that makes a trace in
the event log).

Kind regards / Ake