seems like all is not fair in wifi land. this article
http://www6.tomshardware.com/network/ shows that some APs and STAs from different vendors don't work. I have to say if this is WPA forget about WPA2 it would seem that WIFI would just draft two times the issues we have now!
Its a moot point now, but the passphrase gets translated internally to a 256-bit hex key (it mangles together the passphrase and some of the network information to create a stronger key than the passphrase alone).
It doesn't look to be a setup error - I'd be giving up on it about this point too :)
I have solved this problem. After many hours of playing with drivers and calling 3COM, it appears that the issue was with the 3COM wireless gateway.
They sent me a BIOS flash (version 1.02.12) that addresses the broadcom - 3COM - WPA issue. It hasn't been released yet, but testing is almost complete. I tried the flash and my broadcom wireless NIC connects to the gateway with WPA without any problems
The only issue I'm still having is that when I have my computer pull DHCP from the gateway, it takes about 45-60 seconds for the WLAN to activate after booting. If I set the IP statically though, the WLAN is available right at bootup. Any information on this DHCP issue would be appreciated.
-Jeremy
p.s. Here is the message I recieved from 3COM:
Hello Jeremy,
The released version of 3crwe554g72 software (V1.02) has problems when
connected to Broadcom based cards when using WPA-PSK.
This should be fixed in V1.02.12 which we are regression testing now.
I have enclosed V1.02.12. If you want to try it, then please do so. It is
still not a fully released version of code.
but it is really close to complete testing and should address your issue
Yes, I was talking about the gateway. I have the 11g access point also and it does the same thing. I spoke with 3COM and the firmware on the 2 models are almost identical code except that the gateway/router has a 4 port switch and some extra firewall software built in. Other than that they are almost identical.
I am still waiting on the firmware upgrade for the regular Access point though, will let you guys know if it works when I get it.
Is this the US 3Com support you are talking about? I am in contact with their UK support and they claim the codebase for the AP and the gateway are entirely different and the bug we are talking about is not known by them. My contact says he has ordered the necessary hardware needed (truemobile 1300) to reproduce the bug in order to find a solution in an upcoming firmware.
Okay I now have the 1.02.11 firmware flashed on my AP. Everything seems to work only the DELL client program identifies the signal as WEP as oppose to WPA!? The AP has WEP disabled and WPA+PSK enabled, so has the client. Could you please verify that the DELL software identifies your signal as WPA with the 1.02.11 firmware for the gateway or AP if you have it?
I just put this new firmware on the WAP and the DHCP doesn't work with the NIC. I can connect to the access point, but I am never able to pull an IP address. If I connect to the access point from another PC, the MAC address of the wireless client is listed, but no IP is given out. If I try to set the IP address to the MAC address, i recieve an error message.
At this point the access point is still not working correctly from my testing and I am still sending it back to 3COM once my RMA goes through.
If you have problems with frequent reconnect/disconnects from wireless clients, you may find that a hard reset of the TrueMobile 2300 router will help.
Keep in mind that you will lose all of your custom settings, so either save them or make a note of them.
I was experiencing increasingly frequent disconnects - I had long ago upgraded the 1300 driver, the 2300 firmware, and installed Microsoft's KB815485 and KB826942. For most of last month, my connection was great, and fully secured with WPA and AES.
For the last week, my connection has been getting worse and worse, until it was resetting every 60-90 seconds. I uninstalled and reinstalled the drivers and KBs, to no avail. Finally I stuck a pin in the side of the 2300 for 5 seconds, and voila, it works great again.
superboss
23 Posts
0
September 9th, 2003 08:00
salvador_dali
13 Posts
0
September 9th, 2003 09:00
nice!
thanks superboss
salvador_dali
13 Posts
0
September 9th, 2003 09:00
Herrflik
21 Posts
0
September 9th, 2003 12:00
It doesn't look to be a setup error - I'd be giving up on it about this point too :)
Asul1026
3 Posts
0
October 31st, 2003 13:00
I have solved this problem. After many hours of playing with drivers and calling 3COM, it appears that the issue was with the 3COM wireless gateway.
They sent me a BIOS flash (version 1.02.12) that addresses the broadcom - 3COM - WPA issue. It hasn't been released yet, but testing is almost complete. I tried the flash and my broadcom wireless NIC connects to the gateway with WPA without any problems
The only issue I'm still having is that when I have my computer pull DHCP from the gateway, it takes about 45-60 seconds for the WLAN to activate after booting. If I set the IP statically though, the WLAN is available right at bootup. Any information on this DHCP issue would be appreciated.
-Jeremy
p.s. Here is the message I recieved from 3COM:
Hello Jeremy,
The released version of 3crwe554g72 software (V1.02) has problems when
connected to Broadcom based cards when using WPA-PSK.
This should be fixed in V1.02.12 which we are regression testing now.
I have enclosed V1.02.12. If you want to try it, then please do so. It is
still not a fully released version of code.
but it is really close to complete testing and should address your issue
superboss
23 Posts
0
November 5th, 2003 10:00
Asul1026
3 Posts
0
November 7th, 2003 12:00
Yes, I was talking about the gateway. I have the 11g access point also and it does the same thing. I spoke with 3COM and the firmware on the 2 models are almost identical code except that the gateway/router has a 4 port switch and some extra firewall software built in. Other than that they are almost identical.
I am still waiting on the firmware upgrade for the regular Access point though, will let you guys know if it works when I get it.
superboss
23 Posts
0
November 12th, 2003 11:00
Is this the US 3Com support you are talking about? I am in contact with their UK support and they claim the codebase for the AP and the gateway are entirely different and the bug we are talking about is not known by them. My contact says he has ordered the necessary hardware needed (truemobile 1300) to reproduce the bug in order to find a solution in an upcoming firmware.
"It's all about communication!" :)
superboss
23 Posts
0
November 21st, 2003 11:00
superboss
23 Posts
0
November 26th, 2003 06:00
The new firmware is now available from 3com´s site:
http://www.3com.com/products/en_US/result.jsp?selected=6&sort=effdt&sku=3CRWE454G72&order=desc
Asul1026
3 Posts
0
December 1st, 2003 19:00
I just put this new firmware on the WAP and the DHCP doesn't work with the NIC. I can connect to the access point, but I am never able to pull an IP address. If I connect to the access point from another PC, the MAC address of the wireless client is listed, but no IP is given out. If I try to set the IP address to the MAC address, i recieve an error message.
At this point the access point is still not working correctly from my testing and I am still sending it back to 3COM once my RMA goes through.
hactar19
3 Posts
0
February 11th, 2004 23:00
If you have problems with frequent reconnect/disconnects from wireless clients, you may find that a hard reset of the TrueMobile 2300 router will help.
Keep in mind that you will lose all of your custom settings, so either save them or make a note of them.
I was experiencing increasingly frequent disconnects - I had long ago upgraded the 1300 driver, the 2300 firmware, and installed Microsoft's KB815485 and KB826942. For most of last month, my connection was great, and fully secured with WPA and AES.
For the last week, my connection has been getting worse and worse, until it was resetting every 60-90 seconds. I uninstalled and reinstalled the drivers and KBs, to no avail. Finally I stuck a pin in the side of the 2300 for 5 seconds, and voila, it works great again.