So, my university uses WPA2 Enterprise to authenticate users (you have to put in your username and password to connect), and I have been having problems getting and staying connected.
These issues were occuring on my PB G4, but they are also occurring on my new MBP, so I must be doing something wrong. No one else seems to have as much trouble with this.
After connecting, an 802.1X dialogue comes up asking for my password (even though it is in keychain), and sometimes it will authenticate, sometimes not. When it does, it usually doesn't get an IP address and assigns one randomly (which doesn't work of course). I have to toggle airport on and off and select the (preferred) network manually multiple times before it will get an IP address.
Usually the internet works after this, but only until it decides to stop responding and I have to start the process over again. I have a console log from turning the Airport on, waiting for it to automatically try to connect (the icon in the menubar turns on and off several times) then it gives up and I select it manually, and at the bottom of the log it eventually connects...
If anyone can discern the problem here, it would be greatly appreciated. This is extremely frustrating because it only happens on campus with this WPA2 Enterprise authentication! WPA Personal and WEP work just fine.
These issues were occuring on my PB G4, but they are also occurring on my new MBP, so I must be doing something wrong. No one else seems to have as much trouble with this.
After connecting, an 802.1X dialogue comes up asking for my password (even though it is in keychain), and sometimes it will authenticate, sometimes not. When it does, it usually doesn't get an IP address and assigns one randomly (which doesn't work of course). I have to toggle airport on and off and select the (preferred) network manually multiple times before it will get an IP address.
Usually the internet works after this, but only until it decides to stop responding and I have to start the process over again. I have a console log from turning the Airport on, waiting for it to automatically try to connect (the icon in the menubar turns on and off several times) then it gives up and I select it manually, and at the bottom of the log it eventually connects...
If anyone can discern the problem here, it would be greatly appreciated. This is extremely frustrating because it only happens on campus with this WPA2 Enterprise authentication! WPA Personal and WEP work just fine.