I've been experiencing this same problem on my campus network for a while, and switching to WICD seems to have fixed it for me, too!
I think it's worth noting that the access points on my campus are Aruba Networks access points, and we use the SafeConnect system for network authentication. We actually run two networks: the campus network, and a guest network. The guest network bypasses authentication through SafeConnect to allow guests to hop on the campus wireless (with some access restrictions). I have never had any trouble connecting to the guest network with NetworkManager, but almost always got the "Status 17" error when connecting to the campus network. I've attempted to research this issue before, and seem to recall something about this being specific to Aruba Networks access points. http://ubuntuforums.org/showthread.php?t=1889157 seems to make that connection, and points to a bug filed with the intel wireless drivers: http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 . In any case, WICD does seem to work as a workaround! ** Bug watch added: bugzilla.intellinuxwireless.org/ #2346 http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
