![]() |
2010-05-08
, 00:07
|
Posts: 4 |
Thanked: 1 time |
Joined on May 2010
|
#22
|
![]() |
2010-05-08
, 07:28
|
Posts: 117 |
Thanked: 44 times |
Joined on Dec 2009
|
#23
|
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.
![]() |
2010-05-08
, 17:37
|
Posts: 4 |
Thanked: 1 time |
Joined on May 2010
|
#24
|
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.
The Following User Says Thank You to cogx For This Useful Post: | ||
![]() |
2010-05-08
, 18:12
|
Posts: 117 |
Thanked: 44 times |
Joined on Dec 2009
|
#25
|
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]
![]() |
2010-05-08
, 18:21
|
Posts: 117 |
Thanked: 44 times |
Joined on Dec 2009
|
#26
|
As I wrote in my post, the settings you wrote in post #10 are the same as we use:
Security Method set as "WPA with EAP"
EAP Type: PEAP
EAP Method: EAP MSCHAPv2
Our servers use SSL certificates signed by Thawte.
Last summer when my N810 stopped working, I was sure it was due to this bug:
https://bugs.maemo.org/show_bug.cgi?...ltiple&id=3914
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.
![]() |
2010-05-08
, 20:21
|
Posts: 4 |
Thanked: 1 time |
Joined on May 2010
|
#27
|
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.
![]() |
2010-05-09
, 12:18
|
Posts: 117 |
Thanked: 44 times |
Joined on Dec 2009
|
#28
|
![]() |
2010-06-06
, 08:57
|
Posts: 7 |
Thanked: 1 time |
Joined on Mar 2010
|
#29
|
![]() |
2010-07-07
, 10:25
|
Posts: 22 |
Thanked: 3 times |
Joined on Apr 2010
|
#30
|
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.
Bugs i watch
----------------
A2DP unstable when WiFi is on.
"Wi-Fi Protected Setup" doesn't work, is not optional, and is used when disabled.