After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 517055 - unable to connect after switching from wpa2 to wpa
unable to connect after switching from wpa2 to wpa
Status: RESOLVED DUPLICATE of bug 447300
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-02-17 19:04 UTC by oliviacond
Modified: 2008-08-08 21:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description oliviacond 2008-02-17 19:04:56 UTC 
Please describe the problem:
after i set the router to use wpa instead of wpa2, nm can't automatically connect it. nm should should be able to connect it and ask me for password automatically.
nm's status was "Connecting"/"Trying to establish connection".
To solve this, i had to manually connect by selecting "Connect to other network".

Steps to reproduce:
1. change from wpa2 to wpa in the router
2. try to connect
3. 


Actual results:
the status is only "Connecting" without successfully connected

Expected results:
i should be able to connect to the wireless network successfully

Does this happen every time?
haven't try for second time

Other information:
Comment 1 Wouter Bolsterlee (uws) 2008-05-06 15:06:34 UTC 
Check, I've been hit by this once as well. Another option is to remove the gconf keys.
Comment 2 Wouter Bolsterlee (uws) 2008-06-17 12:08:54 UTC 
Perhaps NM doesn't notice there's an authentication failure?
Comment 3 Germán Poo-Caamaño 2008-08-08 21:18:37 UTC 
I'm marking this bug as duplicated because it's the same issue:
- When some part of the authentication changes in the AP, NM is not
  able to connect anymore.

*** This bug has been marked as a duplicate of 447300 ***