@Dmitry Maruschenko (yojick) #130 Yes, it's pretty irritating. It's not really a bug in network manager though, it's "just" a glitch in the GUI.
Here's how to make it work: 1) Select a totally random certificate from /usr/share/ca-certificates/mozilla 2) Try to connect . you'll not succeed, but don't worry. 3) This WILL create a connection file in /etc/NetworkManager/system-connections 4) The name of the connection file (a text file) will be the name of the desired wifi network SSID 5) You need to edit that file as root. Do this in a terminal (ctrl-alt-t): gksu nautilus /etc/NetworkManager/system-connections 6) Select the file (the name of the SSID) you just created 7) In this file there will be two lines you need to remove. One will state the requirement of a certificate the other will point to the bogus-certificate you used in step 1). Remove both lines. 8) Be sure that the line "identity=" contains BOTH your domain and username, as in identity=DOMAIN\USER (replace DOMAIN and USE with your actual domain name and user-logon) Congrats, if you did the above correct you're now connected. I totally agree that it's a joke that this isn't fixed yet. The "fix" posted by Pritam Baral (pritambaral) in #108 does NOT work anymore. It did however work when he posted it, but for 32 bit users it somehow created a connection file with "identity=DOMAIN\\USER" Notice the extra "\". Follow the steps from 5) to fix this. This is not criticism of Pritam Baral. He did a valid effort to try to fix it, but it's hilarious that this GUI-glitch wasn't fixed a long time ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
