Thanks a lot, depu!
I created a new connection profile, filled in the SSID manually, configured it properly - but now what? If I open the wireless connections through the status bar, it displays our work network with exactly the same SSID (four uppercase letters) that I filled in. But next to it, there's no green indicator for a known network, and if I try to connect, it still asks for a Preshared Key. How can I force it to use the configured profile instead of auto-detecting what type of network it is?
Cheers!
Thats odd.
Some reasons i can think of are
1. The Network settings are different, either EAP Type is different or the EAP method is.
2. Maybe the settings havent "caught on" and you need to restart the N900.
3. If your network is using domain authentication then the username you need to mention should contain the domain as well for example something like tmo\depu where tmo is the domain and depu is the user name.
4. [unlikely but i'd like to mention none the less] theres a typo you have made somewhere.
I used to be able to connect to our campus WPA Enterprise WiFi with my older N810, until they upgraded the server from Windows 2003 (IAS) to Windows 2008R2 (NPS). I also now have an N900 and it is also unable to connect.
There is a long list of devices which connect just fine to our campus network, some of which I've set up for professors myself and others are confirmed to work in other colleges and divisions:
Blackberrys, HTC smartphones, Apple iPhone/iPod/iPad, Motorola Droid, the Archos 5 Internet Tablet, and more.
I've been using the settings talked about in post #10, since they are the same as we use on campus, with the key step being to set the domain\username under the Advanced/EAP tab, which I understand is the step that people tend to not know about until they research it.
I just can't see how it can be anything I'm doing wrong at this point. I've tried putting in the information over and over and over and over, on and off for the past three weeks (somehow thinking it would magically work the next time, putting in the same information)
And yet, I just recently set up an iPod Touch and it was connected in less than a minute. My Windows XP and Windows 7 laptops connect just fine as well.
If there is no bug in the Nokia code, then I'm really at a loss here.
Actually, I don't want to get someone mad at me for muddying the waters, but I also find it interesting that a professor with a Nokia N82 is also unable to connect. Other than the Nokia N900, N810 and N82, the only other WiFi -capable device known not to be able to connect to our network is the Zune HD.
I used to be able to connect to our campus WPA Enterprise WiFi with my older N810, until they upgraded the server from Windows 2003 (IAS) to Windows 2008R2 (NPS). I also now have an N900 and it is also unable to connect.
details, details people.
Whats the network type, authentication method, encryption type, certificates used etc.
Saying "other devices work, the n900 doesn't" gives no one any information other than the info that *something* is not working.
Please provide details and file bugs so that Nokia can debug and if we are lucky provide a patch for that.
However, I get an N900 only to find that it also won't work.
If there is some particular bugzilla entry I should be posting to, let me know.
My eyes keep going back to https://bugs.maemo.org/show_bug.cgi?id=2051
but it looks to me as if it has been dismissed by the Maemo folks and I don't know what information I could provide that Naterator hasn't already provided in comments #44 and #45 in that entry.
Basically the username should be set as domain\username OR username@domain.
Some educational sites using eduroam support this method, some use EAP-TTLS+PAP which does not work. PEAP + MSCHAPv2 is quite popular authentication method which is supported by the tablets, but some setup is needed. Therefore, bad out of the box experience is guaranteed. If you're uncertain, try if step-by-step guide below works. If it doesn't - bummer.
(This example is for Eduroam for N900. Same works for 770, N800 and N810 too)
Originally Posted by
Go Applications -> Settings -> Internet connections
[Connections]
[New]
[Next]
Connection name: eduroam
[Next]
Scan .. Wi-Fi ..
[Yes]
EAP type: PEAP
[Next]
EAP method: EAP MSCHAPv2
[Next]
User name: (username@domain)
password: (your password)
[Next]
[Advanced]
[EAP]
Use manual user name: [x]
Manual user name: (username@domain)
[Save]
[Finish]
However, I get an N900 only to find that it also won't work.
If there is some particular bugzilla entry I should be posting to, let me know.
My eyes keep going back to https://bugs.maemo.org/show_bug.cgi?id=2051
but it looks to me as if it has been dismissed by the Maemo folks and I don't know what information I could provide that Naterator hasn't already provided in comments #44 and #45 in that entry.
Thanks for the info on the bug id's.
Although what i had asked as the *network* setup and not what you had setup on the n900, It is possible that the network update has modified some parameter which is being ignored/ incorrectly sent by the n900.
It would seem that your issue is similar or same as #3914, which is apparently fixed for the N900.
Just to check, have you downloaded and installed the server certificate as a WLAN certificate? I dont think you specifically need to have a mac for that(like it was being discussed in the bug tracker). There should be a way to do that even on a windows/linux box.
Thanks for the info on the bug id's.
Although what i had asked as the *network* setup and not what you had setup on the n900, It is possible that the network update has modified some parameter which is being ignored/ incorrectly sent by the n900.
They changed the WiFi network configuation going a year now and I didn't have the N900 until a month ago. I never tried to configure the N900 against the old Windows 2003 IAS server. That's back when I was using the N810. Sorry for introducing too many variables into my original post. I've long since given up on the N810, since my understanding of bug 3914 is that the N810 will never work against Microsoft NPS RADIUS.
The settings required for our network (WPA, PEAP, MSCHAPv2) are well documented and, as I said in my original post, my Windows laptops and iPod authenticate fine. I only include that information to try to offer up the idea that I'm not utterly clueless, not to suggest that the N900 is an inherently inferior device that won't work for anyone.
I came across the "PEAP + MSCHAPv2 WiFi Authentication Setup" page weeks ago and all that did was to tell me that I already knew what settings to put in my N900, despite the fact it doesn't work for me on our campus (where I work). At the bottom of that page it says, "If you're uncertain, try if step-by-step guide below works. If it doesn't - bummer."
Bummer, indeed.
I get human nature is to protect one's own code or favorite device against all negativity, whether justified or not. I also get the slapping down on the "mee too" posts. Given the complexity involved, at this point the Maemo developers are going to need logs to look at and I keep hoping that the several people that are in fact giving them logged details across several different buzilla entries will eventually lead to a breakthrough. The point being, I'm not the only one on the planet having this exact issue, even if it is only affecting a small number of N900 owners.
In truth, I've already pretty much given up on the N900 for work and moved on, especially given all of the Android-based devices coming out within the next few months that look to be amazing. I can still use the N900 at home and at friends' houses, just not at work, at least not currently.
Originally Posted by
It would seem that your issue is similar or same as #3914, which is apparently fixed for the N900.
Just to check, have you downloaded and installed the server certificate as a WLAN certificate? I dont think you specifically need to have a mac for that(like it was being discussed in the bug tracker). There should be a way to do that even on a windows/linux box.
We use the Thawte Server CA certificate, which is included on the N900. However, I did in fact get the exported cert and installed it, but it still didn't work.
You look like someone who's got a lot of patience .
And its really unacceptable to have a *connected* device which only works on specific network setups and i cant figure out why there isnt any more focus on this from Nokia given the bugs which we are seeing regarding the WLAN setup.
Although if the 3914 bug is the same as the problem you are facing, please reopen the bug and let the Nokia dev's know that it still doesnt work, maybe that will lead to a clarification/patch.
hihi i still cant select the certificate after pr1.2. when i click on certificate in the internet configuration it still show as none. pls advise thanks
.