Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Gengar003

macrumors newbie
Original poster
Nov 12, 2007
4
0
The attached picture is my error, and I am stumped as to how to fix it.

My system:
Black MacBook
Mac OS X 10.4.11
4GB RAM, 30GB free space on the HDD.

My wireless environment:
University-run wireless internet.
WPA2 Enterprise + 802.1X PEAP
My username/password in good standing (they work for wireless on other computers and for other university services unrelated to wireless internet)

Everything used to work correctly, until...

When I log into my computer's "guest" account, a window appears asking for an 802.1x username and password. When I type mine in, it connects correctly.

This window appears automatically after logging in to the "guest" account.

One time, I logged in to guest, but then tried to switch back to my account BEFORE the window appeared. The computer locked up completely. I had to turn it off by holding the "power" button down.

After that, I received the attached error every time I attempted to connect to the university network.

I have tried the following solutions:
  1. Rebooting into "safe boot" mode, then repairing disk permissions. It worked, but broke spotlight. I repeated the process, and then spotlight worked, but 802.1x didn't. Now, I'm stuck on "spotlight works and 802.1x doesn't."
  2. Creating a new location in network preferences
  3. Creating a new 802.1x profile and using that
  4. Re-entering all information related to this wireless internet connection.
  5. Rebooting
  6. Deleting everything out of /Library/Preferences/ByHost/com.apple.<every address>.networkConnect.plist
  7. Searching google for this error (only one useful page found; an archived apple.com forums' post with no resolution

None of those solutions have worked for me.

My university does maintain a 'visitor' network, so I can still access the internet, but I can't do things like access my network storage, university printers, etc, so this is non-workable long-term solution.

My main questions are:
  1. Has anyone else fixed this problem? If so, could you please tell me how?
  2. Is the error a result of a problem with the client (me), or with the access point/authentication server? (my guess is client...)

Thank you.
 

Attachments

  • Picture 2.png
    Picture 2.png
    28.8 KB · Views: 128
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.