[iwlagn] iwl 5300 - Dialog 'Authentication required by wireless network' keeps appearing despite being given correct WPA/WPA2 Personal key

Bug #307353 reported by swulf
42
This bug affects 6 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am trying to connect to a WPA-PSK AES encrypted network using a Lenovo W500 laptop running Ubuntu 8.10. The internal wireless card is an Intel WiFi Link 5300.

Connection to the network has worked precisely once, and then after numerous previous failures. The key (passphrase) is correct and connection to the same wireless router from a different laptop running Windows XP works 100% of the time.

Following the entry of the key into the 'Authentication...' dialog box - and the subsequent connection failure - selecting the 'Show password' checkbox shows a string of 64 letters and numbers, what seem to be a hex representation of something.

This is a show-stopper because I don't use insecure wireless networks and so am forced to use a wired connection (which rather defeats the point of an expensive laptop).

Please advise me as to how I may assist in the rectification of this issue.

Revision history for this message
Michele Mangili (mangilimic) wrote :

Hello!

Thank you for reporting this issue and helping to make Ubuntu better!

I'm moving your report to network-manager-applet!

I must admit that I'm experiencing a very similar problem. I can connect to my wi-fi network and I can use it for a couple of hours without any problem. But sometimes it seems that my pc disconnects from the wi-fi network. It immediately tries to re-login using WPA/WPA2 PSK but it always appear the dialog 'Authentication required by wireless network'.

I've found this possible workaround:
1) Right-click on network-manager-applet icon
2) Uncheck enable wireless
3) Right-click on network-manager-applet icon
4) Check enable wireless again
And I can use the wi-fi network again.

Revision history for this message
Alexander Sack (asac) wrote :

this is usually a driver issue. Maybe linux-backport-modules help for you or the jaunty kernel. If that doesnt help, please attach complete /var/log/syslog

Changed in network-manager-applet:
status: New → Incomplete
Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 307353] Re: Dialog 'Authentication required by wireless network' keeps appearing despite being given correct WPA/WPA2 Personal key

On Mon, Feb 09, 2009 at 06:07:31PM -0000, Alexander Sack wrote:
> this is usually a driver issue. Maybe linux-backport-modules help for
> you or the jaunty kernel. If that doesnt help, please attach complete
> /var/log/syslog
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: network-manager-applet => network-manager
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Dialog 'Authentication required by wireless network' keeps appearing despite being given correct WPA/WPA2 Personal key
> + [iwlagn] iwl 5300 - Dialog 'Authentication required by wireless network' keeps appearing despite being given correct WPA/WPA2 Personal key
>

were you able to test the backport drivers?

 - Alexander

Revision history for this message
Binoy (mailbinoyv) wrote :

using linux-backports-modules-jaunty
the problem still exists.

I have two routers one using wep and other wpa2 personal
jaunty has the same problem connecting to both
the problem started after upgrading from intrepid to jaunty

workaround mentioned by Michele Mangili *does* work
syslog attached

Revision history for this message
swulf (swulf) wrote :

Seems to no longer be a problem (i.e. it works) following upgrade to 9.10.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.