Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
I was a concerned with the problem of bringing PCs that
had previously been setup on other Wifi networks onto a
different WiFi network. Folks were experiencing either:
(1) incorrect WEP key errors or,
(2) automatic, private IP (169.254.*.*) assignment from
Windows.
So I brought down my LAN/MN-700 and one WinXP/MN-710 to
try and duplicate these problems. I succeeded in doing
this. By changing channels on the base station, the
WinXP/MN-710 immediately lost connection to the LAN. The
WinXP/MN-710 then connected to a second, dummy MN-700 I
had setup on the same channel, but a different WEP key,
for this purpose. After a hardwire reset to the original
LAN base station, the channel was changed back. The
dummy MN-700 was powered down.
Now however, I was unable to connect via the WinXP/MN-710
to the LAN. I received the "incorrect WEP key" error. I
also received a Windows-generated automatic, private IP
(169.254.*.*). I tried a number of times. The WEP key
had not changed for my LAN, but I could not connect after
a few tries. Finally, after more minutes passed the MBNU
indicated I had "connected". It takes this long.
Minutes.
Then I tried accessing the WAN/Internet, but could not.
I still had the automatic, private IP assigned to the
WinXP/MN-710. I tried to "RENEW". After a couple on
minutes, I was again assigned the same automatic, private
IP. Hmmm.
It turns out the solution was to "ADD" the base station's
router gateway IP to the configuration. You can do this
even under "Obtain IP automatically" under the "Advanced"
tab. After this a software "RESET" to the base station
via the "Base Station Management Tool" allowed me
to "RENEW" to a DHCP server-assigned IP.
The WinXp/Mn-710 is now fully connected. Patience in
allowing WIndows and the WiFi to establish contact seems
important. It is not an instantaneous process.
Hope thid helps!
I was a concerned with the problem of bringing PCs that
had previously been setup on other Wifi networks onto a
different WiFi network. Folks were experiencing either:
(1) incorrect WEP key errors or,
(2) automatic, private IP (169.254.*.*) assignment from
Windows.
So I brought down my LAN/MN-700 and one WinXP/MN-710 to
try and duplicate these problems. I succeeded in doing
this. By changing channels on the base station, the
WinXP/MN-710 immediately lost connection to the LAN. The
WinXP/MN-710 then connected to a second, dummy MN-700 I
had setup on the same channel, but a different WEP key,
for this purpose. After a hardwire reset to the original
LAN base station, the channel was changed back. The
dummy MN-700 was powered down.
Now however, I was unable to connect via the WinXP/MN-710
to the LAN. I received the "incorrect WEP key" error. I
also received a Windows-generated automatic, private IP
(169.254.*.*). I tried a number of times. The WEP key
had not changed for my LAN, but I could not connect after
a few tries. Finally, after more minutes passed the MBNU
indicated I had "connected". It takes this long.
Minutes.
Then I tried accessing the WAN/Internet, but could not.
I still had the automatic, private IP assigned to the
WinXP/MN-710. I tried to "RENEW". After a couple on
minutes, I was again assigned the same automatic, private
IP. Hmmm.
It turns out the solution was to "ADD" the base station's
router gateway IP to the configuration. You can do this
even under "Obtain IP automatically" under the "Advanced"
tab. After this a software "RESET" to the base station
via the "Base Station Management Tool" allowed me
to "RENEW" to a DHCP server-assigned IP.
The WinXp/Mn-710 is now fully connected. Patience in
allowing WIndows and the WiFi to establish contact seems
important. It is not an instantaneous process.
Hope thid helps!