Bug 2974 - Can't Connect using WPA or WPA 2 with SMCWBR14T-G
: Can't Connect using WPA or WPA 2 with SMCWBR14T-G
Status: RESOLVED DUPLICATE of bug 2937
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 29
: PC Windows XP
: P1 blocker (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-10 07:30 UTC by Sam
Modified: 2006-04-05 13:30 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam 2006-02-10 07:30:02 UTC
I am having problems connecting a Slim Device v3.0 to a SMCWBR14T-G router using WPA or WPA2.
 
Here is a description of the problem:
 
I can connect using no encryption or via ethernet using the 4-port switch; however, I can't connect using WPA or WPA2 wireless authentication. 
 
If I use WPA2 it won't get past the authentication stage. Yes, I am entering the WPA2 correctly (correct upper case, lower case, symbols, etc.)
 
If I use WPA the Slim Device authenticates but doesn't detect the DHCP server, gets an AIPA address 169.254.x.x.
 
If I use a fixed IP and WPA it authenticates, gets past the connection wizard but won't connect. I can't ping the Slim device's IP address. Yes, ICMP is turned off, I have tried it with DHCP turn off and on (fixing every IP address that connects fine with DHCP tunred off) and I have disabled my desktop's firewall (has the Slim Server software installed). A netstat -a -n indicates that no ports are blocked as indicated on your KB.
 
I have also tried updating the slimdevices firmware to version 29 and updating the SMC router to the latest firmware, 1.07.
 
My laptop connects via WPA2 all the time.

The router is in normal b/g mode, not speedbooster mode.
 
I think this is a bug. Please advise. Many thanks.

The device is great but I need to get it working via WPA or WPA2. If I need to buy a new wireless router what ones would you recommend?

Many thanks.

Regards,

Sam
Comment 1 Richard Titmuss 2006-04-05 13:30:43 UTC

*** This bug has been marked as a duplicate of 2937 ***