-
All replies
-
Helpful answers
-
May 16, 2015 9:24 AM in response to nkpltby Niek1998,- I Hope this will work out for you
- Pull down the Wi-Fi menu and turn Wi-FI OFF
- From any Finder window, hit Command+Shift+G to bring up Go To Folder, and enter the following path:
/Library/Preferences/SystemConfiguration/
- Locate the following files, copy them to the desktop for a backup, then delete them from the /SystemConfiguration/ folder:
com.apple.airport.preferences.plist
com.apple.network.identification.plist
NetworkInterfaces.plist
preferences.plist
- Empty the Trash and reboot the Mac
- Turn Wi-Fi back ON from the Wi-Fi menu, join your preferred network as usual
This process forces OS X to create all new preference files for wireless networking, which can be an effective troubleshooting strategy if the wi-fi problems began after upgrading versions of Mac OS X and even installing incremental system updates.
- I Hope this will work out for you
-
May 16, 2015 3:10 PM in response to Niek1998by nkplt,Well, I tried that but it did not help. One thing was different, I do not have a com.apple.network_identification.plist, I do have a com.apple.nat.plist. Since I do not know what that is I did not toss it out. Should I try again and toss that file as well?
Thanks
-
May 18, 2015 6:11 PM in response to nkpltby nkplt,I tried tossing out everything you mentioned. Still no success. I tried to reset the airport and then set it up with the powerbook but still could not get it to work. I think it is some kind of conflict with my current wireless router from Verizon. I think I will just give it up and connect my powerbook via ethernet. That works better anyway. Thanks for the help.
-
May 21, 2015 2:13 PM in response to nkpltby ChitlinsCC,I have an older PB than you = G3 Pismo - 10.4.11 and connect wifi to an UBEE router/cable modem with no hassle at all sing WPA2-PSK via Internet Connect's [Airport] tab
UBEE modem's browser Control Panel
Try Create Network and let it do it automatically with the same credentials as on your other Mac?
-
May 23, 2015 5:43 AM in response to ChitlinsCCby nkplt,I tried that also, that option only gives me WEP connection. If I try create network, I can type in a WPA2 password but it still gives me the same error message. Maybe my airport card is messed up, I don't know
-
May 23, 2015 8:57 AM in response to nkpltby ChitlinsCC,Barring seeing the exact "error message" you don't post I think you may have hit upon the issue with "Maybe my airport Card is messed up." What does System Profiler say about it?
-
May 23, 2015 5:39 PM in response to ChitlinsCCby nkplt,The exact message is not very detailed. When trying to join, it fails and says "There was an error when joining Airport Network .......(name of my router)
I also have a Pismo G3 with airport card and so I fired it up and I get the same exact message. I guess it must be related to my router. I use Verizon Fios and their routers. I did check the router settings and it is set up as WPA2 and allows 802.11 b/g/n connection. Also, in my system profiler, all it says in both computers is Airport firmware version 9.5.2 which I believe is the latest firmware available. Thanks again for all the help but I unless someone can tell me how to access the error code in terminal so I can get more detail, I guess I will quit trying and just plug in with a ethernet cable.
-
May 23, 2015 6:31 PM in response to nkpltby ChitlinsCC,I know this is not very heartening advice - but you have proved that you can indeed "see" the router " ......(name of my router) " - so contacting the router folks and Verizon (?) seems in order. They are certain to point their finger straight back at you and your gear, so maybe insisting on escalating to a senior tech is essential.
The bottom line is that the EVENT that preceded the misbehavior is the New Router. I had some issues with TimeWarner router(s) and required switching to different make/model - same make/model several times = no joy - this last one connected right up, proving my point all along that it was their gear's fault.
You have the data you need = " worked before your FiOS gear hit the scene " = it is the immediately preceding event that is always the culprit. luckily, this time it wasn't your fault (unless you count your decision to fix what wasn't broke )
-
May 23, 2015 6:55 PM in response to ChitlinsCCby nkplt,actually, the new router wasn't my fault either. The old router failed and Verizon replaced it with the new router. Such is life. Talking to Verizon is worse than pulling teeth!! So since this laptop is not used that much anymore I will just connect ethernet and move on. My other computers still connect fine with the new router. Thanks again for the help tho.
-
May 23, 2015 7:57 PM in response to nkpltby ChitlinsCC,your original post implied you made a choice (?) " ....but when I upgraded my wifi network to a new router..." rather than a failure of hardware first = ah, well - if it were me, I would still make 'em fix it.
buenos noches, amigo


