I for some reason can't connect to a wpa enterprise connection using PEAP. I input my user name / password etc. The connection says "connecting" and then it goes back to "available" after staying at connecting for some time. Any ideas? Is Schrap's rom potentially the problem? Or what component would I have to change to alter the WPA encryption. It connects fine to my home WPA-PSK connection... Any ideas would be great thx .
802.11 WPA2 connection issue
i'm facing exactly this problem on my samsung i780 ... also flashed a winmo6.5 ROM ( earlier had 6.1 ) ... same problem continues ... any help welcome !!!
Related
Hard to believe !
I just got back home and tried to connect my new Blue Angel to my Wifi network and... and... and... it seems that there is no way to connect to an AP not broadcasting the SSID !!!
Can someone confirm this? Why such a restriction? Any workaround (besides broadcasting the SSID) ?
My previous PDA did not have this problem !
Thanks.
You are correct. This does not work with the current driver version (at least the one that shipped with my MDAIII in Germany).
Even if you connect to the AP with the SSID broadcasting and set-up WEP, the link will not be re-established when the SSID broadcast is subsequently turned off on the AP.
I also found that even when SSID BC was on, the MDAIII required frequent resets when turning on Wifi and switching APS. Hopefully they'll supply an updated driver.
BTW: Connecting to non-broadcast SSID does work on an MDAII with a sandisk wifi card using the latest Socket driver (doesn't work with the Sandisk driver).
Cheers,
Martin
Well, it works on my new SPV M2000. My AP has an SSID set, but does not broadcast it. I had to type the correct SSID/WEP key, and it all just worked.
I can connect to my access point, even though it's not broadcasting it's SSID. I think the trick is to name your network the same as the SSID. After turning on WLAN, in the WLAN manager - click tools, then click new connection and name the connection your SSID, and then enter relevant WEP keys, etc.
Be warned that it seems the PDA2K has awful WiFi range, my connection rarely shows over 50%, even in the same room as my access point, and on the next floor of my house, the connection often drops - never had this problem with any laptops or other PPC devices.
@whydidnt and dbarfoot :
Okay, sorry about that. I could not find how to get to the place where you can see the active WLANs APs etc... Seems to work as it used to.
I'll disable again the broadcasting of SSID today to check if it works okay, but I don't expect a big surprise.
I was kind of worried if it really had not been supported properly
Thanks
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
Hi all, I've just installed upgrade my Jasjam to WM6 ( Black 1.2) - very nice and fast. However, after upgraded I'm unable to connect to my NetGear Router via Wifi (WEP enabled) any longer.
The WEP Key and MAC address are correct - sometimes the software SOCKET WIFI can identify the SSID but unable to connect still. I've tried to connect without WEP key but no success. The only success I have with the Jasjam to use the Internet is via MS activesync thru notebooks ( via WEP wireless ) to the router. Can anyone help ????....
Is there some setting in WM6 that I'm not awared off.
Many thanks in advance.
I had the same problem with my netgear router on WM6 until I realised I had to check/enable "This is a Hidden Network" in the network card settings.
should work
gfreek said:
I had the same problem with my netgear router on WM6 until I realised I had to check/enable "This is a Hidden Network" in the network card settings.
should work
Click to expand...
Click to collapse
Thank you very much. That tiny check has saved me hours of frustration. It worked perfectly.
Hi there, I have a big problem that will force me to downgrade to WM5 if I can't solve it.
Here's the facts:
I don't have a telephone line at home and I'm connecting to internet using a flat GPRS/UMTS connection with Vodafone using my TyTN as bluetooth modem (using the old WM5 DUN profile).
Since I upgraded to WM6 (and I love it) the DUN profile and Wireless Modem has been replaced by Internet Sharing application. It works very fine but it messes up my network connection with my other PC.
I used to share the internet connection this way: the bluetooth modem was connected to my main PC (AMD Sempron). The LAN (manually setted up) on this PC was: 192.168.0.1 / subnet 255.255.255.0. The LAN (manually setted up) on other PC (AMD Athlon) was 192.160.0.10 / subnet 255.255.255.0 / gateway 192.168.0.1. It all worked very fine.
Now as I connect the PAN bluetooth internet sharing my main PC (Sempron) acquires a new network address (the TyTN seems to be automatically setted as 192.168.0.1) so the LAN on the PC is 192.168.0.153 /subnet 255.255.255.0 /gateway 192.160.0.1 and the connection works fine but I'm not able anymore to connect via LAN tothe other PC even if I try different LAN settings on the Athlon (I tried to manually set it as 192.168.0.10 /subnet 255.255.255.0).
Who can tell me how to configure the LAN setting on the 2 PCs so that I can access internet enabling PAN bluetooth on the TyTN with the main PC (Sempron) and still continue accessing remote folders and files via LAN on the other PC (Athlon)?
It would be great if I could share the connection with the 2 PCs like I did before, but I'll be ok if I can connect to internet with one and have a working LAN between the 2 PCs.
Hope I explained it well.
Waiting for suggestions. Thank you!
Pick a machine that is to be the internet gateway. Do this by initiating the BT PAN network on the first machine. On the first machine's IP stack, Enable Internet Connection Sharing. On the second machine, use the first machine's IP as your default gateway.
You should then be able to access the internet from both machines.
marty_73 said:
Hi there, I have a big problem that will force me to downgrade to WM5 if I can't solve it.
Here's the facts:
I don't have a telephone line at home and I'm connecting to internet using a flat GPRS/UMTS connection with Vodafone using my TyTN as bluetooth modem (using the old WM5 DUN profile).
Since I upgraded to WM6 (and I love it) the DUN profile and Wireless Modem has been replaced by Internet Sharing application. It works very fine but it messes up my network connection with my other PC.
I used to share the internet connection this way: the bluetooth modem was connected to my main PC (AMD Sempron). The LAN (manually setted up) on this PC was: 192.168.0.1 / subnet 255.255.255.0. The LAN (manually setted up) on other PC (AMD Athlon) was 192.160.0.10 / subnet 255.255.255.0 / gateway 192.168.0.1. It all worked very fine.
Now as I connect the PAN bluetooth internet sharing my main PC (Sempron) acquires a new network address (the TyTN seems to be automatically setted as 192.168.0.1) so the LAN on the PC is 192.168.0.153 /subnet 255.255.255.0 /gateway 192.160.0.1 and the connection works fine but I'm not able anymore to connect via LAN tothe other PC even if I try different LAN settings on the Athlon (I tried to manually set it as 192.168.0.10 /subnet 255.255.255.0).
Who can tell me how to configure the LAN setting on the 2 PCs so that I can access internet enabling PAN bluetooth on the TyTN with the main PC (Sempron) and still continue accessing remote folders and files via LAN on the other PC (Athlon)?
It would be great if I could share the connection with the 2 PCs like I did before, but I'll be ok if I can connect to internet with one and have a working LAN between the 2 PCs.
Hope I explained it well.
Waiting for suggestions. Thank you!
Click to expand...
Click to collapse
silverfox0214 said:
Pick a machine that is to be the internet gateway. Do this by initiating the BT PAN network on the first machine. On the first machine's IP stack, Enable Internet Connection Sharing. On the second machine, use the first machine's IP as your default gateway.
You should then be able to access the internet from both machines.
Click to expand...
Click to collapse
Ok, I started the BT PAN on my main machine (AMD Sempron) but how do I enable the connection sharing? When I was using the DUN connection I used the Advanced Options section to enable the Connction Sharing, but where do I find this opzion now?
On a Windows Machine the IP range to be assigned when Internet Connection Sharing is turned on is 192.168.0.x. That is also the range used by Internet Sharing on the phone. This is a routing conflict. You cant have a 0.x being handed out from the phone to the 1st computer and then have that computer handing out 0.x addresses to any other computers. The IP range the Phone hands out needs to be regedited to something else like 192.168.1.x As far as I know, you cannot change the address range in Windows Internet Connection Sharing. You will have to do it on the phone.
If this helps.
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.