Just thought I'd post this FYI. I had a couple of days of hassle getting my XDA2i to talk to my BT Voyager 1250 WiFi router/modem.
I finally got it to work with the following settings..
XDA2i :-
Network Name : Whatever your SSID is
Connects to : The Internet
Authentication : Shared
Data Encryption : WEP
Network Key : your 10 digit network key, by default printed on the bottom of the router.
Key index : 1
Use IEEE 802.1x network access control - yes/checked
EAP type : PEAP
BT Voyager1250:-
Network name : Whatever you've called it
Wireless Channel 6(2437 Mhz)
Encryption - Enabled with default 64 bit encryption key
SSID broadcast - Enabled
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.
I have searched for quite a while and haven't found this exact problem.
I have an at&t 8525 and cannot connect to my Wi-Fi. I turn on the WLAN and wait for the phone to discover the connection points. I select my Wi-Fi point and it asks me for my key. I enter the key and after a delay, it displays the "Key Code is invalid" and asks for it again. I have verified the key against my wireless router and it is correct. I have successfully connected to the Wi-Fi once (after many attempts to enter the key), but have never been successful since.
I have deleted the settings and had the phone re-discover the connection and also tried to set up the connection manually. Nothing works. Any ideas?
Thanks for any help!
You don't say what ROM version you're using and whether it's WM5 or WM6.....
Some of the cooked WM6 ROMs require you to "pretend" that your WLAN is a hidden network (i.e. the SSID is not broadcast, even if it is). You need to go to Start | Settings | Connections tab | Wi-Fi (assuming you have this!) and then tap & hold the required WLAN from the list, select Edit and tick the box that says "This is a hidden network". Then click Next until you get to the end of the process and you should be able to connect to that WLAN successfully.
HTH, Mark.
Sorry. I'm running WM5 ROM Version 2.15.502.3. This is the latest version to come from at&t. Nothing special.
When you enter the key...are you entering the actual key, or just the passphrase which is used to create the key??
the actual key is a weird collection of numbers and letters whereas the passphrase is normally a password........something memorable.
the device needs the key and not the passphrase.
I entered the 13 character string that is designated Key 1 on my router. I thought this was the key. Is this correct? I don't remember anything about a passphrase on the router is that used in another type of security?
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!
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.