I assume the router runs Linux since I wasn't having a problem previously. Well, this has happened before but this time has been more persistent than previously. My router is a Netgear 7550 purchased through att. I don't know that this router has a reboot switch on it. Should there be a reset switch or do you just unplug the router for a few minutes and then plug it back in? Once I do that, do I have to reconfigure the settings on my computer, or will all that remain intact? I've found the same thing to be true with my desktop computer; I leave it in sleep mode most of the time. Once every few weeks I power it off for a few minutes and that seems to get certain cobwebs cleared out. Maybe it's my imagination but I do it anyway. So is there a power switch on most routers, or do you simply unplug it?

Here is something: In the "Session and Startup" under "settings" I see that "Launch gnome services on startup" and "Launch KDE services on startup" are both unchecked. Should these be checked for the keyring to operate at startup? Thanks again!

i dont think so but click the gnome one and see what happens upon restary

If you wouldn't mind, can you look in the directory /etc/NetworkManager/system-connections

and see if multiple files exist for the same network (you should see configuration files with the name of your wireless network). On my xubuntu test install, the password keys are stored as plain text inside of these files.

Its a stab in the dark, but its worth checking to see if you have multiple files. If there is one with your old password, I would either delete that file, or maybe just edit it so that it has the right password.

When I placed "/etc/NetworkManager/system-connections" in a terminal, the only reply I got was "Is a directory." I was assuming that was to be placed in a terminal? If there was something additional I was supposed to do, please let me know. Thank you for this suggestion.

just take a look inside the directory and see if there are text files containing your network information. any file manager will do. or:

will give you a listing of all the files in the directory.

This is what came up:attwifi IceForum Yuhan Yuhan. Okay so there are 2 Yuhans. No doubt that is the source of this problem. The question is how to get rid of the one that bears a faulty password? Thanks for this.

Okay...in the Network Connections GUI I see the two listings--one of which has the bad password. I've tried deleting it before but it just keeps coming back when I reboot...along with the bad password! I don't know how to rid my system of this wrong Network. Any ideas? Thank you.

Are you sure there is no difference in the file names? Its not Yuhan-1 or Yuhan-copy or something?

Nope. Exactly the same.

I think what I want to try is this:

1. disconnect from all any and all networks.

2. open a terminal

3. do this:

4. do this:

5. return to the network manager gui. Connect to the Yuhan network and see if it asks for a pass key. It should, as I think we just deleted the old configurations. Reboot and make sure the change sticks.

I made an edit that is important to the rm code.

Well, it was a very good try and I think it was close...but not quite. Everything proceeded as you said and I did get the password notice after going through the two commands. However, I still wasn't able to log in. I looked at the Network Manager and now there is Yuhan and Yuhan 1. Yuhan 1 still has a bum password but now a different one: it's the first 5 characters of my legitimate password. I'm on this time by, again, going to "disable wireless," and then clicking on that and then clicking on "enable wireless." I'm wondering if I can go through your sequence again and modify it in some way so that it doesn't produce another false network with a false password? Thank you for your persistence and creative approaches to this. I do appreciate it.

I think I will try to go through the sequence you provided above again and see if it will make a difference. Now I can't get online with the laptop AT ALL! The problem is the same: I cannot get that second "Yuhan" out of the system. It seems to keep reasserting itself no matter what. I'm sure this is a software problem; not a hardware issue. I appreciate the help on an issue that is kind of dumb and shouldn't be a problem in the first place!