Large number of "Wireless Network Authentication Required" windows open after unlock
Please be somewhat patient with me as I am still somewhat of a noob in Linux.
My problem lies when I close my laptop for a short to long while and then reopen it and log back in (it locks the screen), I will have a large number of "Wireless Network Authentication Required" windows open and I will have been kicked off my network. The longer that I leave the laptop closed, the more of the windows will be there. It then takes me a bit of time to close them all and log back onto my wireless network.
I am running Slackware 14 full install and am using Xfce as my gui. I have a Toshiba Satellite L550D - 00w with a Realtek Wireless LAN (802.11 bg).
I am unsure as to where to start sleuthing to try and solve this issue. Any Suggestions would be greatly appreciated.
Are you running any sort of Active Directory, LDAP or something similar?
"Wireless Network Authentication Required"
Without knowing much about your problem, clearly something is requiring your key/passphrase/whatever and your laptop has gone to sleep and is not providing it. I see the same at work when there is a communication problem between a client and Active Directory. The other day I was changing out cables and accidentally hit the power button on the UPS with my elbow... that brought down the server running AD and brought about 20 friggin windows like this on each client computer!
Thanks RootMason for your reply.
To my knowledge I am not running any active directory, but am unsure how to check and see if I am. Like I said in my previous post I am a noob. I do understand the basics but when it comes to troubleshooting I am a little ignorant. I did do a full install of Slackware 14 and have been more or less been using the default settings.
Is there any way that I can tell if I am running an active directory? Is there any other information that I could offer up that may help to troubleshoot this extremely annoying problem?
Any more help is gratefully accepted and greatly appreciated.
Don't aplogize for being a "noob", I'm kinda' one too! Well, I'm an intern at a networking company, but I'm only about 2.5 years in and spend most of my time trying NOT to fuck everything up!
That being said, where is the problem occurring? At home or at work? If it's at work and you're not the admin then the admin (or tech or whatever) would be the right guy to hem up and talk to about it. If it's at home, then it's probably some problem with your router trying to autheticate the connection while your laptop is asleep.
I apologize, I don't know anything about your model of router (Toshiba Satellite L550D), but perhaps that's a place to start looking? If I have an opportunity tonight I will try and investigate the problem a bit further... any way you can send any more info on what the error is? Maybe a screenshot?
Hope it helps, have a nice one buddy.
RootMason, Thanks for your reply. My router is actually an Apple Airport Extreme 5th generation <------I think it 5th gen. My computer is the Toshiba Satellite L550D.
After a little more investigation and looking in /var/log/messages I found this:
Does anybody have any suggestions regarding this?
Sorry, I did some research but came up pretty much empty handed, buddy! Off the top of my head one of your problems could be with NetworkManager which I see is throwing this error (I just picked a random one):
Jul 11 06:53:24 draAx NetworkManager: <info> Activation (wlan0) starting connection 'My Network'
I've had plenty of troubles with Network Manager so I get rid of them first thing when I use a system. Unfortunately, I use Debian & Centos so I don't know how to do that in Slackware (I even google'd "slackware 14 disable network manager"). In Centos it's simply to find the interface config file (/etc/sysconfig/network-scripts/ifcfg-eth0) and setting the "NM=no" parameter, hopefully it's something of the same.
I did dig up this little tidbit, but I think it was using slackware 12.somethin':
"The problem in my case was caused by network manager disconnecting. I found more info in /var/log/daemon.log. That in turn seems to be caused by a problem with the card not obtaining a dhcp lease, which causes NM to make a call back to the kernel tht it’s disconnecting."
Anyways this again sort of points to a problem with your network manager. A less awesome way of fixing it might be to remove the "shared secret" from the router... but this will let anyone in range be able to use your router I believe... probably not any better of an option than just not closing the lid!
Anyways, hope that helps. I will continue trying to help if it doesn't. Have a nice one, holmes!
|All times are GMT -5. The time now is 09:19 AM.|