Loc: Yuba City, California
My iMac's airport wireless card would not connect to the Internet, not via my router anyway. The router is downstairs so I couldn't test my internet connection via ethernet.
My iPod Touch has no problem getting on the Internet using the same router.
My iMac can get on the Internet if I leech off of one of the unsecured wireless routers in the neighborhood.
I also switched user accounts but received the same troublesome network problems, with regard to wireless.
When I choose my router's network from the Network control panel it indicates I am using a Self-assigned IP and in small print states that I may not be able to access the internet. Even though my Airport icon on the menu bar has full black bars and the Network control panel gives me a green light, Safari can't open a page and Mail is dead.
So I jumped onto one of the neighborhood routers once again and bingo, Safari loads up lickety-split.
I rebooted the Mac with the Leopard disk and verified permissions and along with the usual permissions suspects, I received seven SUID file warnings indicating that changes had been made to select files but they would not be reversed. There were other permissions anomalies related to iPhoto frameworks plug-ins and the rest were Quicktime related.
Disk repair yielded nothing unusual and now I am performing an Archive and Install.
That complete, the first thing I notice is my internet connection has been restored, however Little Snitch's icon is missing in action from the Mac's menu bar. I double-clicked LS in the applications folder and was informed LS was broken and must be reinstalled again.
I did that and restarted and now its working properly.
As I await Software Update downloads, I thought I would share this with anyone who might be interested.
Loc: Yuba City, California
After the download process was complete, SU prompted me to restart my computer but the Mac hung for more than five-minutes, displaying only the desktop picture.
It was locked up, but by choosing Control-Eject I could invoke the Restart/Sleep/Shutdown panel and when I clicked on any of the buttons nothing would happen. I brought up the Force-Quit dialogue out of curiosity but the box was empty and not even Finder was running.
So I did a hard restart and eventually the Log-in box appeared but after choosing my ID and entering a password the Welcome screen made an appearance, prompting me to choose a language and keyboard layout, followed by prompts for my personal information, such as name and address and Apple ID, the usual routine you expect after having reinstalled Leopard.
When I got the end of the Welcome process, I would click the Done button and the Log-in screen would appear. After logging in I ended up right back at the Welcome screen and being prompted to choose a language and keyboard again.
I performed a second hard restart and this time instead of a log-in screen, my Mac's desktop was blue and suddenly the download indicator appeared and commenced to download the updates I chose earlier. Once that was complete, my Mac is back to normal.
Perhaps the log-in/welcome anomaly occurred because I began using the computer immediately after performing the Archive and Install feature, rather than downloading the latest updates, I don't know.
I'd sure like to have the last two and a half hours back though.
I would have had you try another user first. If that didn't work then we know it's nothing in any User's folder, it's system level. To resolve airport and network connectivity issues I'd first move /Library/Preferences/SystemConfiguration folder to the desktop then reboot. You'd would have had set up airport and network stuff again of course but it's a known fix for connectivity issues. It's probably just the airport and network plists in there but I have never bothered to diagnose it that far down. The wide pattern shotgun works fine.
Too late now though, at least you have a clean system. That never hurts anything.
You had to reinstall LS because the A&I doesn't move any system files installed at system level, only user files. Don't you find LS drags the whole browsing experience down? Your router/firewall protects inbound, but have you ever found LS to block an outbound connection you didn't want to go out? My .02¢ on LS. You know us, you asked for thoughts.
Edit - BTW, the hang after update was a little weird but I've seen it even on a clean system, well, clean except for LS, I'd suspect that may have not wanted to shutdown or something. You could check the console logs if you noted the exact time and possibly see what hung up. When doing that far of an update I always do the Combo Update first, non-restart updates next, then the ones needing a restart. I'm up to .04¢ now.
Loc: Yuba City, California
I would have had you try another user first.
Yup, I mentioned that. But as you say, the wide pattern shotgun took care of it all.
Everything is running fine. I did have to revalidate my Maya user license and its as you say, Alias probably installed something in the System folder, causing Maya to fail on launch after the new install.
Aside from a kernel panic in the fall of 2007, this machine has been running flawlessly for two years and my uptime periods have gone on for as long as fifty to sixty days at a stretch without a restart, so I'm not complaining.
I just thought it was weird because I could get on the internet with someone else's router but not my own, that I could get on the internet with my router using my iPod, but not my Mac. That the Mac was assigning its own IP and not using the one provided by my router.
In fact, when I went to the Network > Advanced > TCP/IP, the IPv4 address was totally out of left field. It looked more like an IP that might be assigned by Cox cable and not my router. Also, the router's IP was missing in action, along with the IP that would normally be assigned to my Mac. I noticed this when I was investigating the "self-assigned" IP.
One item of note though, is that last week I was having trouble maintaining my internet connection. Airport would drop my connection while I was browsing and by going up to the Finder menu and clicking on the Airport icon, I would turn Airport off and back on and almost immediately my internet connection would be restored. It became a routine for about three days.
That is until I did some checking on Apple's website and found a white paper on troubleshooting Airport and one of the first items on the list was deleting the airport plist file, which I did and Airport began behaving properly once again.
No problem. I blew by the "other user" part obviously. My curiosity though is why things like that happen to a perfectly fine running system. All of a sudden something belches garbage into the wrong spot. Who's error was it writing the bad bits, HD, OS? Only the Shadow knows.
Loc: Yuba City, California
I found these solutions by Magnus Lewan posted in the Apple Discussions forum:
1. Reset Open Firmware. As you turn on the machine, press & hold Cmd+Option+O+F until you get a screen that says "Welcome to Open Firmware". At the prompt, enter "reset-nvram" (without the quotes). Press return. Enter "reset-all". Press return and the machine will restart.
2. Open network preferences. In airport, go to advanced. Check the box that says disconnect the wireless network when logging out. (It seems incredible that it would work, but apparently it sometimes does.)
3. Restart in "Safe" mode (hold down "Shift" while restarting). Once in Safe mode simply restart again in regular mode. Apple docs here.
4. Go into your keychain and find the password key for your network. If you connect to a WAP it will be the name of that WAP. Then in the key click on the access control tab. It probably shows selected applications. Change this to "Allow all applications to access this item".
5. (The following apparently works temporarily, but it is not very clean. I would not recommend it except as a last resort.) Remove all the files and folders from the non-user Library/Preferences folder and reboot.
After my shotgun fix, these solutions are moot, but if it happens again I'll give number 1 a shot. I did 3, 4, and 5 before my A&I.
I googled "self-assigned IP" and found the problem goes back a few years. And here I thought it all started with the last Airport update.
Xplain's use of MacNews, AppleCentral and AppleExpo are not affiliated with Apple, Inc. MacTech is a registered trademark of Xplain Corporation. AppleCentral, MacNews, Xplain, "The journal of Apple technology", Apple Expo, Explain It, MacDev, MacDev-1, THINK Reference, NetProfessional, MacTech Central, MacTech Domains, MacForge, and the MacTutorMan are trademarks or service marks of Xplain Corp. Sprocket is a registered trademark of eSprocket Corp. Other trademarks and copyrights appearing in this printing or software remain the property of their respective holders.
All contents are Copyright 1984-2010 by Xplain Corporation. All rights reserved. Theme designed by Icreon.