Danny, have you tried my suggestion to run in a terminal "iwconfig wlan0 essid ssid_name"? (substitute for wlan0 and ssid_name as appropriate). I have no idea why this works, but I have had a 100% connection success rate over the last 6 weeks. I find it works either a) to issue the command once NM starts trying to connect, or b) to issue it after the WPA2 password dialog pops up. If (b), I sometimes have to click on the NM icon and then click on the particular connection I'm trying to make. But I have been connecting daily with no failures since I first discovered this workaround.
If a networking guru has any clue why this might work, I would love to hear an explanation. -- [Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP (Enterprise) network (disassociating by local choice (reason=3) ) https://bugs.launchpad.net/bugs/272185 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
