Yep! The AP is set to WPA-PSK (TSIK encryption is used although you cannot change the encryption method on the AP side) and I set the hex key. On the Inspiron 5100 I switch to WPA-PSK TSIK and enter the same key. I get nothing but "new wireless network found" and a prompt to enter the WEP key (?!?!) I enter the PSK key and it goes back to "new wireless network found".
When the wlan is detected on the clientside it wants me to enter the WEP password although I have not selected WEP on the AP or the client, whats up with that? Do I NEED to have WEP enabled in addition to WPA-PSK? This is driving me nuts...
On the AP, you should set encryption to be TKIP for both group and pairwise (it may not distinguish; in the case just use TKIP). TSIK (?) is unlikely to be supported by anyone but 3com.
Set the authentication to PSK only (disable EAP/1X/Radius).
For simplicity's sake, enter a simple PSK passphrase (8 characters) for now.
On the client, set your ID as your only preferred network for now. For properties, use authentication WPA-PSK, encryption TKIP, and enter the same passphrase as above in place of the "network key". The 'authenticate' tab can be safely ignored.
When you OK everything, the network should connect, skip authentication, and setup encryption as normal (for WPA).
If it doesn't work, make sure both the AP and client are Wi-Fi certified for WPA. If either isn't, then try for a firmware upgrade from the supplier. If that doesn't do it, then you might need new hardware.
In that case the usual rules are:
#1- Only get wifi certified kit
#2- If #1 is impossible, stick with a single vendor (or at least single chipset type)
:: Forgot to add, the windows error message suggests the AP is not beaconing WPA-PSK-TKIP, so its trying to fall back to WEP. So, the odds are the AP config is the problem here.
AP Sorry TSIK was a typo, TKIP is the encryption method used on the AP (its not alterable). I've set the AP to use WPA - PreShare Passphrase as suggested.
Client Is set to WPA-PSK / TKIP. Ive set the network key to the hex encoded version of the entered passphrase (what format should it be entered in? xx-xx-xx-xx, xx xx xx xx or xxxxxxxx?) but the problem is still exactly the same as before.
Both the AP and the Client is certified for WPA. The client is an Inspiron 5100 with a truemobile 1300 (latest drivers) on WindowsXP Home SP1.
Message Edited by superboss on 09-05-2003 09:08 AM
You should be close then - but, you're overguessing the passphrase entry ;)
All you need to do is enter the same phrase on both ends of the link, exactly as-is. The XP UI is fairly unhelpful here, as it tries to present a minimal interface, but for any type of connection, its 'key' entry boxes take either a passphrase or hex key, depending on context. Its important to enter the passphrase the same both ends, ie, keep the same case. You can use symbol characters too (such as %), but its a good idea to keep it simple first time round.
i have the same problems with the Linksys WRTG54 router and the 3 Com 3CRWE454G72. With the SP1 I needed the MS patach 815485 to get the WPA. I set the Linksys to use WPA PSK and a group renewal from 0 to 6000 secs. I used the TKIP and the AES and the card will not connect. It only works on an open encrypted format i.e. OPEN with WEP. I changed to this card to get better reception from the router and that has been better however this WPA should work on it.
Okay tried setting the passphrase in cleartext and made sure to use lowercaps etc. Still no go. It detects the signal as TKIP and says it finds the network but only prompts me to enter the WEP password :-/
so it seems with the reverse config of what you have that there is a problem too. I believe that the issue lies with your card and my router unable to utitlize 256 bit processing. This is necessary for the WPA to work and on the tech sheets it seems to be lacking.
Thats curious; what do you have running on the PC.
OK, if you're not using this already, just use XPs own networking control (I know, its shoddy, but it ought to be able to do it :) ). If theres a Broadcon control panel installed, disable or kill it for now.
In XPs wireless, you can then just pick the SSID from the list in the 'advanced' window, and setup WPA-PSK in the properties for that SSID. You get to type in the PSK phrase twice, then if you OK both of those its *supposed* to just connect (worst case, unplug and replug the card to get it to do it).
Theres one more last-ditch thing you can do with PSK if that doesn't work, and thats to enter a full 256-bit hex key on each end rather than the passphrase. On XP, you just type a 64-character 'passphrase' and it assumes you meant it to be a hex key instead. For the AP, it might be the same, or might have an explicit setup option for it.
johnallg
2 Intern
•
7.3K Posts
0
September 2nd, 2003 23:00
superboss
23 Posts
0
September 3rd, 2003 05:00
superboss
23 Posts
0
September 5th, 2003 07:00
When the wlan is detected on the clientside it wants me to enter the WEP password although I have not selected WEP on the AP or the client, whats up with that? Do I NEED to have WEP enabled in addition to WPA-PSK? This is driving me nuts...
Herrflik
21 Posts
0
September 5th, 2003 10:00
Set the authentication to PSK only (disable EAP/1X/Radius).
For simplicity's sake, enter a simple PSK passphrase (8 characters) for now.
On the client, set your ID as your only preferred network for now. For properties, use authentication WPA-PSK, encryption TKIP, and enter the same passphrase as above in place of the "network key". The 'authenticate' tab can be safely ignored.
When you OK everything, the network should connect, skip authentication, and setup encryption as normal (for WPA).
If it doesn't work, make sure both the AP and client are Wi-Fi certified for WPA. If either isn't, then try for a firmware upgrade from the supplier. If that doesn't do it, then you might need new hardware.
In that case the usual rules are:
#1- Only get wifi certified kit
#2- If #1 is impossible, stick with a single vendor (or at least single chipset type)
:: Forgot to add, the windows error message suggests the AP is not beaconing WPA-PSK-TKIP, so its trying to fall back to WEP. So, the odds are the AP config is the problem here.
Message Edited by Herrflik on 09-05-2003 12:56 PM
superboss
23 Posts
0
September 5th, 2003 13:00
AP
Sorry TSIK was a typo, TKIP is the encryption method used on the AP (its not alterable). I've set the AP to use WPA - PreShare Passphrase as suggested.
Client
Is set to WPA-PSK / TKIP. Ive set the network key to the hex encoded version of the entered passphrase (what format should it be entered in? xx-xx-xx-xx, xx xx xx xx or xxxxxxxx?) but the problem is still exactly the same as before.
Both the AP and the Client is certified for WPA. The client is an Inspiron 5100 with a truemobile 1300 (latest drivers) on WindowsXP Home SP1.
Message Edited by superboss on 09-05-2003 09:08 AM
Herrflik
21 Posts
0
September 8th, 2003 06:00
You should be close then - but, you're overguessing the passphrase entry ;)
All you need to do is enter the same phrase on both ends of the link, exactly as-is. The XP UI is fairly unhelpful here, as it tries to present a minimal interface, but for any type of connection, its 'key' entry boxes take either a passphrase or hex key, depending on context. Its important to enter the passphrase the same both ends, ie, keep the same case. You can use symbol characters too (such as %), but its a good idea to keep it simple first time round.
salvador_dali
13 Posts
0
September 8th, 2003 09:00
bossman
i have the same problems with the Linksys WRTG54 router and the 3 Com 3CRWE454G72. With the SP1 I needed the MS patach 815485 to get the WPA. I set the Linksys to use WPA PSK and a group renewal from 0 to 6000 secs. I used the TKIP and the AES and the card will not connect. It only works on an open encrypted format i.e. OPEN with WEP. I changed to this card to get better reception from the router and that has been better however this WPA should work on it.
superboss
23 Posts
0
September 8th, 2003 16:00
Okay tried setting the passphrase in cleartext and made sure to use lowercaps etc. Still no go. It detects the signal as TKIP and says it finds the network but only prompts me to enter the WEP password :-/
salvador_dali
13 Posts
0
September 9th, 2003 01:00
Herrflik
21 Posts
0
September 9th, 2003 06:00
Thats curious; what do you have running on the PC.
OK, if you're not using this already, just use XPs own networking control (I know, its shoddy, but it ought to be able to do it :) ). If theres a Broadcon control panel installed, disable or kill it for now.
In XPs wireless, you can then just pick the SSID from the list in the 'advanced' window, and setup WPA-PSK in the properties for that SSID. You get to type in the PSK phrase twice, then if you OK both of those its *supposed* to just connect (worst case, unplug and replug the card to get it to do it).
Theres one more last-ditch thing you can do with PSK if that doesn't work, and thats to enter a full 256-bit hex key on each end rather than the passphrase. On XP, you just type a 64-character 'passphrase' and it assumes you meant it to be a hex key instead. For the AP, it might be the same, or might have an explicit setup option for it.
salvador_dali
13 Posts
0
September 9th, 2003 07:00
Herrflik
Where would I generate the 256 bit Hex key for the WPA? Does the passphrase get translated via a generic tool on XP?
superboss
23 Posts
0
September 9th, 2003 07:00
Am I reading you right.. it translates a passphrase to a hexadecimal string on the XP side?
superboss
23 Posts
0
September 9th, 2003 08:00
Found this cool page for generating hex keys:
http://www.warewolflabs.com/portfolio/programming/wepskg/wepskg.html
superboss
23 Posts
0
September 9th, 2003 08:00
salvador_dali
13 Posts
0
September 9th, 2003 08:00
superboss
try that hex key in place of the passphrase. let us know what if any connectivity you get. my ap does not generate a hex key alas!