Hi, i have a similar problem with my Dad's SB2 and his Compex N28G
router. He cannot log in using WEP or WPA. If no encryption is
selected, everything is fine.
When I brought my Linksys WRT54G to troubleshoot, no problems
encountered, SB2 can login whether WEP or WPA.
It appears that some
Mark,
Some thoughts:
Are both AP running at the same time? If so, and they are being used
as DHCP servers to get the IP address for the SB this might cause the
169.254.xxx.xxx problem.
Try turning off the old AP and see if that helps.
Make sure you reset the SB by holding the power button
Thanks for the reply David,
I have just got my SB2 working with my old WAP now. The reason that
wasnt working was because the password for the new WAP was longer than
the old one and I had put spaces in after it instead of deleting the
remaining characters. So the major panic is over as I can
Mark,
Glad you've got your music back especially as your having to work.
Luckily I am on a few days holiday.
With regard to the SB apparently connecting I did notice that when I
rebooted mine it did try to connect as soon as I choose the network
name. It obviously could not have done this as
David,
It did ask me for my password after I had selected the WAP. I entered
it incorrectly,on for my old WAP as it had lots of spaces after it, but
then the SB2 said it was connecting to the WAP and after about 5 seconds
it actually said that it was connected. Obviously there is absolutely
no
Mark,
it seems the real problem now is that, for some reason, the SB is
fixated on the 169.254 address.
I dont know if the following is possible, as I do not use my router as
a DHCP server. I run a full domain setup with WIN SBS 2003. The
router and server PC have fixed IP's issued by the SBS
OK a little update on my 'day at work'!
I tried the fixed IP thing and it did not work.
I then tried connecting my SB2 to my new WAP without any encryption at
all an 'open system' hey presto it worked. So I then tried it with
128bit WEP encryption and yet again that worked. So I finally tried
I saw this behavior myself when working to configure a new SB2 in a WPA
network. The device would claim that it was connected, but it would
continuously select the default private IP (169...).
I backed off all of my security constraints of my host network
(WPA2,AES/TKP - WPA,AES - WPA,TKIP).
