Bug 1420 - problems connecting to 3com AP
: problems connecting to 3com AP
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: unspecified
: All All
: P2 major (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-22 16:34 UTC by Kevin Pearsall
Modified: 2008-12-18 11:37 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-04-22 16:34:00 UTC
customer reported, that he can't connect with fw 9 to his 3com 3CRWE454G72

also says he's having some dhcp issues with it as well.
Comment 1 Kevin Pearsall 2005-04-22 16:35:14 UTC
more information from another customer with the same problem:
Resetting the 3com to factory default did not help.
Also selecting the region USA on both SB2 and 3com
did not enable them to talk to each other.

The settings on my 3com are:

3C number			3CRWE454G72
Software version		1.03.07A
Boot loader version		1.00.00
Wireless version		V1.0.2.1
Hardware version		R01A
Serial Number			73BF339A07C02

LAN IP Address			10.103.155.8
LAN Subnet Mask			255.255.255.0
Access Point's DHCP Server	Disable (enabling makes no difference)
LAN Port MAC Address		00-0D-54-A0-7C-02

Device Mode			Access Point mode
Wireless Networking Enabled	Enable
Channel				3 (other channels (1 and 11) make no difference)
Service Area Name/SSID		Croky (default 3Com also does not work)
Device Name			ap
WPA Encryption			Disabled
WEP Encryption			128bit (Disabled makes no difference)
Wireless MAC Address		00-0D-54-A0-7C-02

The access point log just says:

07 min(s) 01 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 09 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 17 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 24 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 32 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 40 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
07 min(s) 55 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 03 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 11 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 19 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 27 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 35 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 43 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 51 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
08 min(s) 59 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
09 min(s) 07 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
09 min(s) 15 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device
09 min(s) 22 sec(s) after system power on : Wireless MAC address
00:04:20:05:A4:09 has connected with the device 

The wireless connectivity view option on the SB2
keeps giving a number of 90-91%, which drops to
81-85% when I unscrew the antenna.  But occasionally
it shows 0%, both with and without antenna.
Comment 2 Vidur Apparao 2005-04-23 10:26:48 UTC
I didn't have the problem with firmware 1.03.07, but upgraded to 1.03.07A and am
not able to connect.
Comment 3 Vidur Apparao 2005-04-23 14:33:38 UTC
The problem is that firmware 1.03.07A is sending REASSOCIATE_RESPONSE messages
instead of ASSOCIATE_RESPONSE. Fix in the works.
Comment 4 Vidur Apparao 2005-04-24 11:11:44 UTC
Fixed in firmware 11 (6.0.x branch) and 12 (trunk).