Wi-Fi no connect when WPA2 psk contains ASCII space - Atrix 4G General

My home wireless network is secured with a WPA2 63 character ASCII pass phrase that includes a space (blank) character. All wireless devices in my home can connect to it except for my Atrix 4G phones. I changed the pass phrase on my router to replace the space with a non-blank character, and my Atrix was able to connect.
The ASCII space character is valid in a WPA2 pass phrase, but the Atrix 4g evidently does not support it.
I just thought I'd mention this in case anyone else runs into this problem.
It would be interesting if some of you could confirm my findings for WPA2 or any other wireless security protocol that permits ASCII space characters.

Related

Thicko WLAN question

Right then, I don't know much about secure Wifi, so I've just changed my access point to not broadcast the SSID. So, how might I get my MDA Pro to learn about the SSID if it's not broadcast? Can someone please give me a "for dummies" guide to the LEAP thing as I don't have a clue
When I was broadcasting an SSID, it all worked perfectly, pretty much automatically.
I cheated, i set access point to broadcast ssid just whilst i put the JJ on it, once on i turned off ssid broadcasting.
its seemed a bit flakey when trying to add it in the leap settings page. i tried both open adn eap and then just decided it'll be quicker just to enable ssid for 2 mins.
This is hardware dependent, of course, but I set my wifi router up to only allow access from listed mac addresses. That, in addition to hiding ssid (once connected) and 128 bit wep is about enough to stop me getting the crawling heebie-jeebies.
They don't call me paranoid mike for nothing.
Just because you are paranoid, doesn't mean they *aren't* out to get you
this_mike said:
This is hardware dependent, of course, but I set my wifi router up to only allow access from listed mac addresses.
Click to expand...
Click to collapse
Interesting, and I think my router will do this. How can I determine the MAC address of the MDA?
OK, the following is on a blue angel but I imagine that the principle should extend to WM05.
Firstly, get the wep setup and copy the (uppercase) key to your ppc via AS so you can broadcast your ssid with relatively few twitches D).
Start > Settings > Connections > WLAN, fire up wifi and connect to your access point - in WM2003SE this means checking a tick box (or ticking a checkbox). Once you're connected, you should be able to see the ssid, tx rate etc as well as the mac of your wifi adapter.
Additionally / alternatively, your wifi ap may tell you the macs of all connected devices. The smart person would check this first and make a note of any devices and use this as a cross-check.
HTH!
Hidding the ssid doesn't bring any security
- trust me -
...
The only way is to setup a basic WPA encryption. And you will be secure as long as you change the password on regular basis (every 1 or 2 months)
Avoid WEP encryption it's just crap and doesn't bring any security.
The SSID stuff and mac address filtering are just making you think that you are secure when you are not.
30sec to 5min max to decrypt WEP encryptions, less than 5 sec for mac address and SSID stuff.
works fine on mine and I don't broadcast ssid.
>start>settings>connections>network cards
>add new
type in your SSID as the network name
fill in the rest as per your setup
ok, there is no real security on wireless, but if we are all going to use it we may as well instigate all the security options we can. if there are 2 connections for a cruiser to access and 1 is easier than the other, I know what I would do....
WEP and above do provide security, at least if you don't want any old Johnny using your network.
So, use WEP or whatever security you have.
Hiding SSID literally just hides it. However, most hacking tools easily show the SSID anyway, so don't really on this. But, if you do hide the SSID, you have to set up the connection manually, typing in the name of the SSID and WEP key.
V
most hackers tools that show ssid will decrypt wep in less than 2min.
I was just pointing it out because
1- it's to consider when you're buying an Access Point
2- If you're using it with sensible website (bank account) and such (even to check your mail - using your credit card etc ...)
fair point...
I guess it would be unthoughtful of us to give the know how without also giving the gotchas
;-)
I have got a hidden SSID and the qtek is able to find the network after typing in the name, but it ist not able to connect.
I have already checked the MAC.
It gets the right IP but after few second it scans the network for another time and so it goes on

configuring linksys wifi with WEP

So I can get on wifi networks anywhere but at home. My MDA Vario finds the SSID, but won't connect.
If I remove WEP encryption on the router side, it'll connect. No luck with WEP64 or 128, it'll just say 'connecting' for a while and then go on to the other networks on my list.
What am I missing? I'm using the WRT54GL, which is pretty much the same as every other Linksys.
The obvious question comes into my mind.
Did you place the WEP key in "network key".
If not that will do the trick.
Cheers,
Drifter
yeah, I have.. both shared and open, on WEP. Something more odd is happening, which is why I suspect the configuration of the Linksys.
Like I said, it works if I turn off WEP on the router.
if I wait a while, I get the "unable to obtain a server-assigned IP address" message.
Try to reset your Linksy by unpluging it for a while.
Sometimes I can't connect to my linksys and after a reset it will connect.
Some ohter question. Why don't you use WPA instead of WEP?
Have you the possibility to enter the WEP Keys in hex and in ASCII Mode on your router?
WEP is a bit tricky on a wm5 device. You have to enter your key in hex format and it has to be exactly 10 digits long for 64bit or 26 digits long for 128 bit. That means the ASCII version of the key has to be five digits or 13 digits respectively before being converted to hex. I believe your router will do the conversion for you.
BTW, the lynksis wrt54g series routers are sorta a "hacker favorite" because lynksis made the firmware open so there have been a lot of firmwares developed for it that extend it's capabilities like being able to turn up the transmission strength or add a RADIUS server. Check out DD-WRT or OpenWRT (actually a mini Linux installation). It's a fun little machine.
Gene
theres no need to enter the key in hex. i use an ascii key! but be sure you take the right format on your router!
I've not got an ascii key to work but have helped a number of people to connect to a variety of APs using hex of exact length that couldn't otherwise connect. FWIW.
Yeah, that's why I got the GL
I've tried 5-character ascii and 13-char ascii. I think I'll try the 64-bit hex now.
I may use WPA at some point, but I have other odd devices that need to connect, such as a wireless print server. They are hard to configure.
(edit: I got tired of having to type in the hex key, so I went with WPA. Reconfigured my printer adapter and MDA, now I have two laptops and a second MDA to go! I guess the ASCII-hex generation scheme on the Linksys doesn't match the WM5 scheme.)
so you got it to work? If not, give your wizard a static ip address and see if that helps. also i'm connecting to my linksys and d-link routers easily and both or them have a Shared WEP encryption.
I have a linksys and it works fine; try upping the power output of your k-jam to full power and then try...
yes, I got it to work. I think the trouble was trying to use the ASCII WEP key.

Wifi wep long key problem

My HTC hd can find my router and says that it is available but when i enter the 26 WEP key string it is unable to connect. I notice that it seems to " save " a much shorter key string. Does the hd have a problem with long WEP keys. I have tried chaning the WEP to something shorter but the router will not allow this. Many thanks for any help.
Paul
I don't use WEP, but have an issue with a long WPA2 key - it just doesn't connect. It's not a problem specific to HD though, I had this problem with my previous WM6.1 device which was manufactured by Asus. So far I haven't been able to find a solution.
I have no problem with my 26 key WEP
My wifi settings are:
Authentication: Open
Data Encryption: WEP
Default transmit key: 1
Wep Encryption: 128 Bit, 26 Hex digits
Passphrase: *something*
Key index: 1 (the 26 hex digit code (numbers only)
Check your wifi router setting, maybe it's in WPA/PSK, which use shorter letters for encryption
I'm using 32 bytes (64 in hex) key for wpa2 without problem.
I'm sure I didn't set so long key to my router, but I forget the key so I just retrieved it from windows using some tool and I got 64 bytes hex string as a result and it works. The same situation for WiFi at work.

WIFI will not connect

Hi all, my wi-fi is acting strange. At my parents house i can connect to my wireless router with WEP64 and the 5 character ASCII key, however at my house my WEP64 is HEX based and when i type it is it will not connect.. do i need to do anything different for HEX keys vs ASCII keys?
Thanks!

Need help setting up Wifi Network with PEAP

Hi,
I'm pretty new to EAP and PEAP, but it looks like my campus just upgraded the Wireless to WPA2 using PEAP. I wanted to configure my Cingular 8525 (which I just bought secondhand last week) to take advantage of this newest Wifi network. I am currently not on campus (and thus do not have access to the network), but I wanted to have all of the configuration ready before the next term started. There is some Cingular/AT&T version of WM6 currently loaded.
I start off by creating a new wireless network, just like I did for my home network. I can add the network ID, and I set the security to WPA2 and AES, and check the box "the key is automatically provided".
When I go into the next page ("Configure Network Authentication"), I select PEAP for EAP type. However, I cannot open the "Properties" dialogue.
It gives me the error: "Cannot log on to the wireless network. This network requires a personal certificate to positively identify you".
Here is a PDF link to how we are supposed to configure the new network under Windows XP. I guess once it is configured correctly, we just have to log in with our university User-ID and password to use the network.
Will the registry hack mentioned here help solve this problem?
They have older WEP networks, but apparently they are slower and have a more limited range. Also, it tehy wireless configuration utility states "invalid key" for the newer WEP network, since the key is ASCII and contains non alphanumeric characters.
Also, is there a way to set networks as "preferred", like in windows XP? At my house, many nearby networks are detected, and I sometimes have to manually connect to my own.
Thanks in advance for the help.

Categories

Resources