On Sun, 30 Dec 2007 22:54:45 -0000, Colin Wilson
<(E-Mail Removed) o.uk> wrote:
>> Any ideas?
>
>http://www.skyuser.co.uk might have come across it before...
>
>The only other thing I can think of is whether you have any firewall
>software ignoring the new internal IP range ?!?
>
>Can you get a list of attached devices within the router config ?
The devices that didn't work weren't showing as connected devices.
Anyway, I got to the bottom of it.
Elder son had managed to enter the WAP password incorrectly twice
(probably all in lower case). It's interesting that the laptop didn't
show an error in connection; it's just sat there for a week "acquiring
ip address". I suppose it's reasonable for the router not to give it
an ip address if it won't authenticate :-)
Second Win XP home machine. Never, ever gets an ip address via
wireless. This looks like a poor implementation of 802.11G by the
Belkin wireless adaptor. I have always had trouble with Belkin gear; I
should have binned it months ago. Anyway, forcing it to connect in B,
not G mode cured the problem. Although this drops the speed to 11Mb/s,
it's only 4Mb/s up the internet pipe anyway, so no loss there. It is
simple to force the connection into B mode if you use the Belkin GUI
to configure it but I coudn't see a way of doing it if Windows was
managing the wireless network connection.
Cheers
Norm