Right then, a bit of an update! The way i got around it was disabling NOD32's "IMON" thing, that was stopping me getting an IP address. If you have NOD32, use the latest release of it which you can get off their website
Right then, a bit of an update! The way i got around it was disabling NOD32's "IMON" thing, that was stopping me getting an IP address. If you have NOD32, use the latest release of it which you can get off their website
No NOD here
Significant NOD absence here also; drat and double drat!
My son has managed to fix the problem: here is his account of how he did it.
It turns out that our wi-fi access point is acting in mixed mode - i.e. is is
providing both WEP (the old standard) and WPA (the new standard) encryption
and authentication. Although I had tried to force windows into using WEP
only, by manually entering the settings (right click connection, properties,
wireless networks, properties), it still reverted to WPA-PSK (pre shared key
- the norm in small networks - meaning that the codes must be manually
entered on all machines), instead of connecting using WEP - this is probably
a bug. The solution was simply to use the "new" wireless networks interface,
and when prompted, enter the WPA key instead of the WEP one.
This problem and solution should affect machines that:
* are running XP with SP2 installed
* are running mixed mode access points
Well-spotted that man!
There are currently 1 users browsing this thread. (0 members and 1 guests)