On 10/07/2019 02:08, John Rumm wrote:
On 09/07/2019 21:56, ss wrote:
On 08/07/2019 19:56, ss wrote:
Ok will try and ring tomorrow, it did run on the ethernet yesterday.

Update:

I think I can close this off now. The netbook has been investigated in
depth by remote by J Rumm for over an hour, the situation is still not
resolvedÂ* and looks like winxp is likely the issue. I am confident
that all the contributions by others were covered by John, I say
confident in as much I havent a clue to most of what he was looking at.

Anyhow I do thank you all for your contributionsÂ* and a special thanks
to John for the time taken to investigate it for me.

For those still following along, I will give a quick summary of what we
know now...

So this is not a WEP/WPA issue. WinXP was correctly identifying WPA, and
actually connected without any difficulty.

so why was it issuing a wep error message?

What it does have is a DHCP problem after having authenticated on the
wifi. If I manually assign an IP in the correct subnet, then it works
ok. However that is not a useable solution for the use case required.


router has some special magic for its mac addr?


The router configuration and DHCP setup is fine (and other wifi devices
have connected and DHCPed ok)

This could be related to the issues addressed in KB953761 (DHCP options
not recognised, when sever includes option 43). However that hotfix does
not seem to have done it initially at least, although I am currently
clarifying an issue on that.




--
If I had all the money I've spent on drink...
...I'd spend it on drink.

Sir Henry (at Rawlinson's End)