Home LAN ok with WEP but can't connect to works WPA-PSK secured network.
I have a fairly new ROM
Operator version 5.40.1.179
Rom version 1.40.00 WWE
Rom date 03/10/05
Radio version 1.06.02
Protocol version 1337.38
ExtROM version 1.40.179 WWE
Don't really want to do another ROM upgrade unless it is ABSOLUTELY essential. Anyone have a similar ROM with a working WPA-PSK network?
When we set WPA-PSK on the Blue Angel it insists on 802.1X authentication with either smart card or certificate. Our network doesn't use either but the tick box to turn off IEEE 802.1X access is greyed out on the BA. It isn't greyed out when we use WEP.
Is there a registry setting I could amend to turn off IEEE 802.1X when WPA-PSK is activated.
Do radio upgrades also require full hard resets?
Do hope someone can help.
On the Network Key screen what are you setting in the Authentication drop down? You should be choosing WPA-PSK and Data Encryption TKIP. Uncheck if checked The Key is provided for me automatically, and enter the key in network key box. Key index should be 1 by default. You should IGNORE the 802.1x tab.
I will let others answer regarding the Radio ROM upgrade as I am not sure what exists for the BA. But I doubt that this would solve the question anyway.
Hope this helps!
Jbn,
We are doing exactly as you say (TKIP, uncheck auto key, enter key & key index 1). We haven't been trying to set the details on the 802.1x tab but when we failed to connect we took a look at it.
We have MAC filtering set up and have included the BA MAC address (as provided by vxIP). Checked and double checked the key.
Just been informed that setting EAP type to PEAP in 802.1x tab rather than smart card or certificate might help.
Fingers crossed this will fix it.
Got it working
I had it working with my K-Jam original ROM, although I would much prefer support for 802.11i/AES...
Does anyone know if AKU2 introduces support for WPA2/AES/EAP-TLS or EAP-TTLS?
Now, there's a trick I think I read here before:
type your PSK with your on-screen keyboard, not the hardware keuboard.
Give it a try and let us know.
Cheers,
Hal
Oooops! Sorry guys, BA forum... My post is partly irrelevant.
Still, try the on-screen keyboard...
Re: Got it working
hal said:
I had it working with my K-Jam original ROM, although I would much prefer support for 802.11i/AES...
Does anyone know if AKU2 introduces support for WPA2/AES/EAP-TLS or EAP-TTLS?
Now, there's a trick I think I read here before:
type your PSK with your on-screen keyboard, not the hardware keuboard.
Give it a try and let us know.
Cheers,
Hal
Oooops! Sorry guys, BA forum... My post is partly irrelevant.
Still, try the on-screen keyboard...
Click to expand...
Click to collapse
All suggestions greatly appreciated, I think I have been trying the on screen keyboard but I will recheck.
Blue Angel will not connect to 802.11G network
I thought I would try out a few of the suggestions on my home LAN even though it was working fine under WEP. Then I would be set up for the office LAN on Monday (or so I thought).
It turns out my wireless access point does not have WPA-PSK facility (I may look for a firmware upgrade tomorrow).
However when I changed the network from mixed mode to just 802.11G I was unable to connect to it. Resetting back to mixed mode & it connects ok. It would appear that my problem is not WPA-PSK but more specifically 802.11G networks. Does WPA-PSK only operate on 802.11G networks or can it run on 802.11b?
I have seen the 5 page thread on the Wizard index relating to a cab installation / registry fix to enable 802.11g access. Unfortunately the cab didn't install on the Blue Angel.
Can anyone suggest a fix and do you have 802.11g access with your Blue Angels?
BA does not have 802.11g. The Wizard supports it with appropriate ROM or Registry updates.
WPA-PSK is independent of B/G. So, yes, if your workplace is G only then this could explain the problem that you are having.
jbn said:
BA does not have 802.11g. The Wizard supports it with appropriate ROM or Registry updates.
WPA-PSK is independent of B/G. So, yes, if your workplace is G only then this could explain the problem that you are having.
Click to expand...
Click to collapse
Thanks jbn, it's starting to make sense now.
I have just made the registry entries required by the Wizard to my BA. I'll reboot and set network to g and see how it goes..............
EDIT
DID NOT WORK. Perhaps the BA hardware simply can't do 802.11g. Can anyone confirm the WiFi of the BA is different to the Wizard AND not capable of 802.11g?
IIRC, the BA uses TI's TNETW1110 chip, which does *NOT* support 802.11g at all. The code for supporting the newer TNETW1130 (which is what I think they use in the Wizard) is actually present ... which is why WiFi will become disabled if you turn on the 802.11g registry hacks in your BA ...
Stabilo said:
DID NOT WORK. Perhaps the BA hardware simply can't do 802.11g. Can anyone confirm the WiFi of the BA is different to the Wizard AND not capable of 802.11g?
Click to expand...
Click to collapse
BA cannot do 802.11g because of the hardware. Never, ever.
If you have a g access point, it must be set to mixed mode for the BA (or any b-only device) to connect. Note that while the b device is active on the network, any other g clients will see slower connect speeds because of the compatibility mode. This is why some homogeneous environments would set to disallow b connections.
As far as WPA-PSK goes, I am using it with my BA. Any connect problems I've had were always due to something set wrong on the AP. The BA is WPA, not WPA2 (a/k/a 802.11i). Also, it does not support the AES mode of encryption. So make sure your AP is set to WPA-PSK (1 is usually implied when 2 is not supported) and TKIP, not AES or TKIP+AES.
One other suggestion. If you happen to be using a certain type of Linksys AP, there was a bug in one version of the firmware whereby if you had ever entered WEP keys and then tried to switch to WPA, it wouldn't work without first clearing the WEP keys with a hard reset. I had this issue and it drove me crazy until I read about the solution.
Hope this helps,
Paul
ratazzi,
Thanks for your comments.
Don't think they will like it at work if I tell them I need to slow the network down for 50 users just so I can connect my BA
Could I connect a 802.11b wireless access point to my desktop / laptop at work (connected to the internet) and connect my BA to the access point without slowing down the rest of the network?
It is good to know that the BA can do WPA-PSK even if only at 802.11b. I realise 802.11b is fast enough for the BA but if corporate networks are running at 802.11g then the BA will fail to connect at any speed.
Any other solutions to connect a BA to 802.11g?
ActivSync is ok but I would prefer wireless.
Is there a SD LAN card that would do 802.11g (plus WPA-PSK)?
Enabling mixed mode on a decent Wireless Access Point will not force all clients to run at 11Mbps. Those that can will do 54, those that can't won't.
jbn said:
Enabling mixed mode on a decent Wireless Access Point will not force all clients to run at 11Mbps. Those that can will do 54, those that can't won't.
Click to expand...
Click to collapse
That sounds good to me jbn, thanks again.
Stabilo said:
ratazzi,
Could I connect a 802.11b wireless access point to my desktop / laptop at work (connected to the internet) and connect my BA to the access point without slowing down the rest of the network?
Click to expand...
Click to collapse
You can do that.
However your IT staff would probably go beserk.
I check regularly to ensure that none of my users has done the very thing ... One user demended that he be allowed to and got very annoyed when I refused. He didn't see anything wrong with introducing a consumer grade (read low security) AP into an environment where we had paid top dollar for AP's with heavy security and spent many many hours locking everything down as much as humanly possible.
Remember WPA-PSK is not intended for enterprise level security ... it's better than WEP but given a poor passphrase it's vulnerable.
Is there a SD LAN card that would do 802.11g (plus WPA-PSK)?
Click to expand...
Click to collapse
A quick search of google says yes. Don't know if they are any good ... perhaps you could let US know?
Some good points there Doormat.
If I use a complex passphrase (WPA-PSK) and MAC filtering I am assuming it will be relatively safe i.e. as safe as the main network since that is what the network guys have set up.
Having recently purchased an E100, 2 off E200's a C500 and a M2000, together with about 3GB of SD cards my budget is rather stretched.
As soon as I can I will pick up a SD LAN card and post my results.
Thanks for all the help from XDA-developers.
Doormat,
My attempts with google suggest 802.11g only exists for CF cards not SD cards. Or that was the comment made 8th Jan by ms mobiles http://msmobiles.com/news.php/4767.html
Do you have a link for a SD card?
802.11b devoces will impact 802.11g device!
JBN,
I have to partly disagree with you:
using mixed mode will negatively impact the throughput of you .11g network.
This is due to the protection bit that is being set then for the .11g devices/APs.
The global effect is that while the datarate of the 11g clients will be of 54Mbps (potentially), the real throughput on an enterprise grade AP will be at best around 17/18Mbps instead of 25-27Mbps.
That's a very good reason for corp netadmins to try and ban .11b devices on an 11g network...
Doormat, I agree with you. In my terminology an AP brought by an end-user in a corp network qualifies as a rogue AP and will be immediately blocked.
WPA2/802.11i/RSN with eap-tls/ttls or PEAP is the first basic rule of thumb... Even @home that's what I run. Call me paranoid ;-)
Cheers,
Hal
hal, you are technically correct of course, but the net result in most configurations is not noticeable as far as performance goes. There is a huge difference with WAPs that were forced to B for all clients when only one such client had connected amongst a set of Gs. In my (limited I accept) experience there is no practical difference for most of the time. In high bandwidth environments it is an academic discussion because in those circumstances systems should be connected using 100BaseT or GigE in a switched network rather than a collision-prone network.
Let's not lose sight of the original question though with this level of technical conversation!
Stabilo said:
Doormat,
My attempts with google suggest 802.11g only exists for CF cards not SD cards. Or that was the comment made 8th Jan by ms mobiles http://msmobiles.com/news.php/4767.html
Do you have a link for a SD card?
Click to expand...
Click to collapse
Here's what I found:
http://www.digitimes.com/bits_chips/a20060209A9053.html
I must admit ... I hadn't noticed the march release date before.
Damn - hate it when I accidentally double post!
Related
Hi
I have a wifi AP at home, and one at work, Both use WPA-PSK with mac addy auth. SSID Visible cause sh1te WM2003SE OS cant cope with hidden SSID.
Get a whole load of oddities from the XDA IIs. Both SSID's and keys are listed in the wifi setup on the device. What I would expect is that if I switch the device on when I am within range of the AP @ work, it connects to it no fuss, likewise, when I drive home, switch XDA on it connects, no fuss, unfortunately this is not usually the case. The following are in order of likelyness to occur!
Problem 1
Sometimes I switch it on, and it sits there searching for eons, never finds AP. If I disable and then re-enable wifi on the XDA then it connects.
Problem 2
Sometimes, the XDA will tell me that its connected to my home network when I am at work - it isn't!
Problem 3
Sometimes I switch it on, it connects to the AP, but no net connectivity - looking. Using PPC Ipconfig, I see that device never managed to get an IP addy. Stop, start wifi problem resolves
Problem 3
Occasionally, the PPC forgets the shared secret, and I have to re-input it, start/stop wifi before it will connect to the AP
Problem 4
Sometimes, it just BLUNTLY REFUSES to connect to the AP if I do the above. In this case I try all the above with a soft reset as well. If that fails then I need remove all the wifi AP's, soft reset, wait (ages) for it to see a new AP, enter the PSK then it will connect.
It also struggles to connect to other APs (wifi hotspots). Things work a whole lot better when there is just one AP involved (i,e not work and home).
Prob 4 occurs once/week, prob 1 occurs every day, others somewhere between. All problems are of course COMPLETELY UNACCEPTABLE for a product that has been released to the consumer.
Nigel
Hello Veledron,
I've a similar problem: at our company WLAN is set up to reqire WPA and authentication with user certificates. Since it is not possible to import user certificates in Windows Mobile 2003 SE "out of the box" I found out how to do that - it is described here
http://www.jacco2.dds.nl/networking/crtimprt.html
a little bit difficould procedure, but it worked - I can see my personal company certificate in the private-certificate store of my MDAIII.
The problem is, that I can't get a connection. WLAN-Manager says "connected", but I can't receive an IP-address - and in the logs of our Cisco-APs I can't see anything from my PDA. What also is a little bit strange for me: the MDAIII does not remember the setting "authentication with certificates", it always switches to "authentication using PEAP"...
any idea?
thanks
Gerald
Hi Veledron & gekap
I too have similiar problem with my netgear router at home. It seems that everytime it connect to the network it will just keep scanning eventhough it prompt that it already connected. It been 2 days and still i cannot manage to connect
Hopefully there is a solution to this problem.
Regardz
shark
There is.... Turn off AP, or move device to location where it is out of range, remove all WiFi profiles from device, hard reset, turn on router. wait (ages) for device to realize that there is a wifi ap nearby, enter PSK, all is well.
There seems to be no pattern to the WiFi failures, I have to do the above maybe twice a week to get it to connect. When the device gets itsself into a poor state this is the only way.
You cant delete an active profile, and the profile list only appears when wifi is turned on (stupid!) hence the need to turn off the AP.
Nigel
Hi Guys,
I manage to solve my wifi problem,
i just add the XDA IIs mac address to my netgear router plus assigned a reserve ip address based on it mac address and was able to connect successfully with no problem. Hope this solution helps.
Regardz
Sharkz
Hi,
thanks for the tips, but all of them are not a solution for me. I do not have any problems connecting to WLANs using WEP or to unencrypted WLANs, but i guess that there are problems with WPA in the PDA2K. I think the guys of you who have succussful connected to a WLAN using WPA have done that using WPA-PSK, not WPA with TKIP as encryption-method and PEAP or certificates as authentication method over 802.1x.
In our company TKIP is mandatory, and it is necessary to use certificates for authentication - this can be done with either EAP-TLS (so called "smartcard or certificate" in the setup-menu of the PDA-2k) or using PEAP. I've troubleshooted this a lot, and I can't see any authentication packet coming to our Cisco-APs from the PDA2K using this methods (I've turned on advanced logging on the APs to see any little bit...).
I fear the worst, that the WLAN-driver of the PDA2K does not support TKIP! Of course WPA is supportet from Windows 2003 Mobile SE, but in my opinion that is not enough - the card driver down the OS must also support the whole WPA-Standard, and it seems to me that the PDA2K driver does only support WPA-PSK. I found an article which can be an explanation of the problem:
http://www.socketforum.com/topic.asp?TOPIC_ID=2924
So I've 2 questions to you:
.) which driver version is installed on your PDA2Ks? (you can find that in the registry under HKLM\SOFTWARE\Drivers\Wavedev - I've: Common: 0.04.01, Device: 1.06.01 GER, DriverVersion: 0.08.00, Patch: 1.00)
.) has anyone of you ever connected to a WLAN using WPA (not WPA-PSK!)?
thanks
Gerald
Where the hell is it?
After using the preferred W2003 method of tapping everything in sight in the vain hope that I might stumble across what I'm looking for, I've failed miserably. So, having configured my shiny new router for WPA encryption, how the bl**dy hell do I configure the XDA2s to talk to it via WPA?
crocodile said:
Where the hell is it?
After using the preferred W2003 method of tapping everything in sight in the vain hope that I might stumble across what I'm looking for, I've failed miserably. So, having configured my shiny new router for WPA encryption, how the bl**dy hell do I configure the XDA2s to talk to it via WPA?
Click to expand...
Click to collapse
Connect to your shiny new router with your XDA2s. A "window" will popup and ask you for the key.
Assuming that the PPC can use (WPA) Authentication, which I can not prove since I use 64bit (WEP) encryption. If WPA auth. doesn't prompt on your PPC, try using WEP for WiFi security on your shiny new router.
I'm using WPA-PSK with my Linksys WRT54G (Firmware v3.03.6) without problems ..
QTEK9090
ROM: 1.22.00 WWE
RADIO: 1.10.00
PROTOCOL: 1337.391
EXTROM: 1.22.557 WWE (cooked)
BT: 3500 (with patch)
Yes, but is your router shiny?
Try putting the WINS address "192.168.0.1" or whatever address of your router is.
Also some devices would only accept the Hex variety of the key you choose.
Good luck.
I have a similar problem. I have a linksys wireless router set to secure.
My SX66 asks me for the password. When I enter it I get an error message that it is not the correct password.
The SX66 then says it is connected to the network and shows the SSID and other details, but other than this message it doesn't seem to be connected and I cannot connect to the internet.
What am I'm doing wrong?
To get to the options:
1) turn on the wireless
2) wait for it to pop up asking you if your router connects to "work" or the "Internet". I assume you will want to click "work".
3) Open the wireless LAN manager
4) Click the TOOLS menu at the bottom.
5) Choose NETWORK CARDS
6) You should have a "Configure Wireless Networks" window up.
7) Tap your shiny router one time (it should say connected BTW)
Now you should have 3 tabs at the bottom, General - Network Key - 802.1x . Under the Network Key tab you should have 4 options for Authentication - Open, Shared, WPA, WPA-PSK. The data encryption option will depend on which authentication you choose. I beleive you should choose WPA for authentication and WEP for data encryption. Then put in the key. If that does not work, try TKIP for data encryption maybe.
I have not tested out any of this myself yet. I still have an old linksys running 128 bit WEP. I am getting a Sonicwall TZ-170 SP (think that is the model #) and will then try WPA and maybe even see if I can get RADIUS working through the PDA2K.
WiFi Security
Thank you ed207_us for those instructions!!! They helped so much.
For everyone's general consumption, I thought y'all might be interested in WiFi security:
http://windowssecrets.com/comp/050526/#story1
(towards t e bottom of the page -- it's worth looking for)
http://blogs.zdnet.com/Ou/index.php?p=43
I just got my home WiFi network running; this is so cool!
So, is it possible? Has it been done and I missed it? WPA2 ability would greatly increase my use of this device, and everyone else's I'm sure.
I've also searched all over the web for information on connecting the SX66 to a WPA2 connection.
I'm running DD-WRT v23 SP2 on a Linksys WRT54GL. My router is running in WPA2 Pre-Shared Key Only security mode with AES WPA Algorithms. My WPA Shared Key consists of 63 random alpha-numeric characters as generated by GRC's Ultra High Security Password Generator.
My SX66 is running ROM version 1.40.00, Radio version 1.15.00, and ExtROM version 1.40.125, as supplied by the SX66 Standardization Project.
I'm using Juniper Odyssey 4.50.0.2911 to try to connect to my router.
After typing in the router information, Odyssey attempts to connect to the access point but gets no further than searching for access point.
Can anyone offer any advice?
Try to "downgrade" your security to wpa... :/
I found this over the internet, it may be your router...
However, in WPA2's ratification, there is an
implemetation called WPA2/TKIP+AES which allows the use of WPA/TKIP for
backward compatibility. Check if your APs support that..... Even that, it
is not a guarantee that it will work. I have never got it working with
Linksys WRT54GS/WRT54GX. However, the Linksys WRT54GC works flawlessly. My
laptops are connecting via WPA2/AES and my WM5 devices are connecting via
WPA/TKIP.
Click to expand...
Click to collapse
Looks like there's some wireless issues here -
I have a Dlink DI-524 b/g router, set to WEP with a small key.
Running WM5 - wireless fine.
Running WM6 Black edition 1.2 - Can see access point, says key is wrong.
Running WM6 Black edition 2.0 - Can see access point, says key is wrong.
Running WM6 XDA live... .20 - fine
Pretty sure XDA live .10 was fine as well, but that was a few weeks back now .
Tried all the settings available, WEP,WPA,WPA2,Hex keys, Ascii keys, no encryption at all..... no go. Can see the AP fine..... takes about 30 seconds before coming back with an incorrect key error.
Anyone else see this?
Sorry dude, Im using WEP 64bit key and works a treat (reception sucks in the loft though)
hmmmmm.
I've tried 64/128 bit keys and everything... perhaps its an issue with wm6/router software. What model AP are you using?
Just tried mine and it works flawlessly...
Maybe try and reset the router/wap?
Been there, done that as well
It's a bit of a puzzle.
It's strange that one flavour of WM6 works and not another. I might have to do a bit of scratching about in the registries/dll's of both and see if there's anything different.
But it's not too critical, as long as one version of WM6 works for me
WPA PSK TKIP running fine here......
No problems with WPA-PSK using TKIP on D-Link DSL-G604T.
Also fine here...
I am using the back 2.0 right now and I have no issue at all.
My settings are:
WPA2 AES RADIUS on a Dlink 2100 AP
from now on... can you please post all issues with Black 2.0 here
Wellll.... I was going to post there, but I was unsure if it was just a WM black issue or a larger one involving other flavours. I did a search before posting and there were hints of similar wireless issues with other roms and other people.
And I've found some sort of solution -
Flashed it back to WM black, finally managed to get it to connect with wpa-2 with an pre-shared AES key. After that, all connection modes work - open/wep/wps.
Will check the registry settings and see if there's anything obviously different now than from the default install.
Funny I was having a similar problem, but it was with WM 6 Black Edition V1.2.
My phone was not finding one of my wireless routers, even when I was standing right beside it, but it would connect to my other one fine. They are both identical and are setup identically, so I dont know why this was happening. It only happened with Black 1.2, XML, and LVSW were fine.
I just now flashed Black V.2 and everything is running fine again.
Very strange... it seems to be the opposite of what happened to you.
What type of router?
I have a router at my office - MN-700 by Microsoft - that causes this problem with all versions of WM6. You will have to reboot both your cable/dsl modem and router and all will be fine. All will be fine until you re-connect your phone via your USB cable and re-sync. After that, you'll be back in the same boat and have to reboot the modem and router.
I have two routers at home - one by dlink and one by linksys - and neither have ever exhibited similar behavior. Therefore, I think it more a router (perhaps firewall?) problem, than a problem with WM6.
I'm now $.02 in the hole....
J
Guy_Incognito said:
Looks like there's some wireless issues here -
I have a Dlink DI-524 b/g router, set to WEP with a small key.
Running WM5 - wireless fine.
Running WM6 Black edition 1.2 - Can see access point, says key is wrong.
Running WM6 Black edition 2.0 - Can see access point, says key is wrong.
Running WM6 XDA live... .20 - fine
Pretty sure XDA live .10 was fine as well, but that was a few weeks back now .
Tried all the settings available, WEP,WPA,WPA2,Hex keys, Ascii keys, no encryption at all..... no go. Can see the AP fine..... takes about 30 seconds before coming back with an incorrect key error.
Anyone else see this?
Click to expand...
Click to collapse
you can
Start->Settings->Connections(Tab)->Wireless LAN ->Power Mode->Best Performance
The Setting is Maybe fine.
There's loads of us happily wifi-ing with Black V2.
I look after hundreds of clients wireless networks... and you may not be surprised to learn that 99.9% of wep problems where it says "incorrect key" are caused by...wait for it... an incorrect key!
Don't cut and paste the key. TYpe it in manually.
However - other options:
Do you have mac filtering enabled on router?
Have you set your device to ask for a specific IP address?
Have you set the device to max performance?
Finally... change the SSID of your home network. All the mucking about you have done may have left some residual mess in the device registry and it is getting confused.
also before typing just check in a word if you are typing the key correct... maybe theres a problem with your hw keyboard... and you don't know it...
qwertz <-> qwerty <-> ??????
IronManDS said:
I have a router at my office - MN-700 by Microsoft - that causes this problem with all versions of WM6. You will have to reboot both your cable/dsl modem and router and all will be fine. All will be fine until you re-connect your phone via your USB cable and re-sync. After that, you'll be back in the same boat and have to reboot the modem and router.
I have two routers at home - one by dlink and one by linksys - and neither have ever exhibited similar behavior. Therefore, I think it more a router (perhaps firewall?) problem, than a problem with WM6.
I'm now $.02 in the hole....
J
Click to expand...
Click to collapse
hmm...i recently upgraded from WM5 to WM6 LVSW0326 ROM and faced this same problem...same setup, same router, same WEP and it worked for a while ...then it died. Refused to connect.
i am sure the WEP is correct as i have the same key on my other wireless devices... and know what is even more interesting? i disable WEP and my device connects ok!
so i know it is not the router or the wifi protion of my hermes, more like the ROM is not sending the network key properly...even after asking for it several times!
anyone has a cab for just the wifi portion?
edit: never had this issue with WM5 even with WEP enabled!
I HAVE THE SAME PROBLEM...
i tried to post my problem in the 1.2 and 2.0 forums, but no one could help ....
i found a weird round about way to make this work every once in a while...
i would go to my network adapters > IEEE wifi adapter > change the specific ip to one that i knew it would work from my router...
this would make it connect, but woudln't work right....
so then when i change it back to "use server-assigned IP"... it would pick up the right address from my router and work .... and all would be fine.... but then when i turned off wifi and tried again, it would fail again.
a problem i see is when it's trying to detect my network, the IP address in the grayed-out box reads (fe80::209:2dff:feef) but when it would work correctly, it would have a normal IP address....
maybe there's something in the writing to the wifi that's different in america???
philpwong said:
you can
Start->Settings->Connections(Tab)->Wireless LAN ->Power Mode->Best Performance
The Setting is Maybe fine.
Click to expand...
Click to collapse
It's work! Thanks!
I did try "This is hidden network" and all the others' suggestions! This is the simpliest and workable method!
Thx again! I can surf by wireless Lan again!
I wonder if MS have seriously reduced the power output on the wireless when its set to BEST BATTERY. It seems a) its set to that by default rather than in the middle and b) quite a few people are having problems with their wifi.
I have Belkin N1 router and it connected fine first time even on low power - and on BEST PERFORMANCE I pick up more of my neighbours SSID's than I used to with WM5
I've had most of the problems listed here.
The new LVSW now has this problem also but Vanilla works fine for me, old LVSW's, XDA Live. Upon changing the protocol the router uses I could connect on the first attempt, subsequent attempts would not work.
I have no trouble with the works router.
This seems to be something other than Microsoft, maybe worth asking LVSW what he did differently on his latest.
Hey
I just got this phone.
Anyways, thought it'd be great to connect to my home internet.
We have an Airport Base Station. It's passworded with WPA Personal.
Anyway, it goes to connect, says I need a network key. I type the password in and it fails to connect. I figure I need to set it to WPA.
I go to configure and then click my router in the list.
In 'General' Tab I've got it as 'connects to the internet'.
In Network key I'm pretty sure i've tried them all. Some settings has the network key grayed out. Other settings I type it in, click ok and it INSTANTLY says the network key isnt correct. Wouldn't it need a moment to verify with the router if I'm typing the right password?????
Anyway I think I've tried all combos. Then when I click my router and hit connect, it says connecting for a moment, then goes back to available.
Any ideas?
I did a hard reset. I havent updated the ROMs or anything yet... would that be wise?
Cheers
bt home hub2 connects but no net
I am wirelessly connected to our BT homehub2 network, but cannot use internet explorer, all the wpa, channel, passkey's etc are the same?
O2xda2s on T-mob rom 2003 2GbSD - Pre-pay O2sim
Last I checked, the angel only supports 802.11B, not G.
No G = no WPA, only WEP.
hmmm
but it has WPA settings in the network key tab?
also it refers to it as 802.11X I think?
ok guys do not confuse encryption with network speed, personally i use in my BA and router with setup WPA PSK (Personal Key) with TKIP encryption, secure and compatible solution
if encrypption is WPA2 the BA will not connect
xplode said:
ok guys do not confuse encryption with network speed, personally i use in my BA and router with setup WPA PSK (Personal Key) with TKIP encryption, secure and compatible solution
if encrypption is WPA2 the BA will not connect
Click to expand...
Click to collapse
Shows how long it's been since I updated my angel then, I was not aware that a WPA stack had been added to the available ROM's.