On 10/07/2019 11:14, Jethro_uk wrote:
On Wed, 10 Jul 2019 02:08:17 +0100, 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.
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.
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.
Well troll hunters will be upset.
For some reason, I wonder if there's anyway of getting the workstation to
join a domain, and then leave it ? I have the vaguest of memories about
issues with XP images when cloned across a company I worked for that
required them to join/leave a domain to do something to "set" the
networking to make it unique.
ISTR there were (apparently mythical[1]) issues with cloned SIDs on a
domain... I don't recall a network related one though.
[1]
https://blogs.technet.microsoft.com/...sprep-matters/
(I suppose I could create a VPN from the XP box back here ad join it to
a domain controller running in a VM, but I am sceptical that will solve
the problem)
Which leads to another question ... there's nothing else on the network
that's doing a DHCP job is there ?
The router could see a total of three devices that had DHCPed, a couple
of SWMBO's iThings, and the Eee's ethernet.
I know WinXP/NT Server 4 networks
could be jammed if another DHCP server popped up from nowhere. Which used
to happen a lot (in those days) as salespeople carried NT4 Server laptops
and their IT guys never turned off DHCP. So when they connected to our
network everything barfed.
Yup Win server really does like to be master of all things DHCP and DNS,
that's for sure!
--
Cheers,
John.
/================================================== ===============\
| Internode Ltd -
http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\================================================= ================/