Airport problems after leopard update

Hello, guys.
I need your support to solve a "mistery". I remember a similar post 4 or 5 months ago but in this case issue was solved with the next patch.
I have been installing several leopard updates and now I can't connect me to my wireless lan. Leopard cannot understand my password.
No problem if I want to connect me to unsecure wireless lan.
I think that is a problem with the password entry window code.
Some kind of suggestion ?
Thsnks in advanced.

Hi cbejarano!
As requested by a brody, a Host, has relocated your Topic, to a more appropriate Forum.
As it has been transferred, it is not necessary for you to repost elsewhere, at this time.
But also for future reference, please review the first entry How To Post A New Topic, on Feedback About Discussions.
That is the Forum where you erroneously posted your issue.
Numerous new members also post first entries there, so you are not alone!
Hence the need for explanatory tips!
Enjoy Your Stay In  Discussions!
ali b

Similar Messages

Airport problems after latest update password

Yesterday I did a software update and airport was one of the updates listed. After the update neither my desktop or laptop would connect to the airport network. I used the airport utility to re set up the airport base station and was able to get my laptop working on the wireless network. My desktop, however, will not connect to the airport anymore. It keeps telling me the password is incorrect (the password is correct, I am using it to log in on my laptop). I notice on my laptop the security is WPA2 and on the desktop I only have the option of WEP. The desktop is running OS 10.4. Any ideas?
Thanks for your help

I was having major problems too. I ended up completely uninstalling itunes then downloaded it again from http://www.apple.com/itunes/. If you're using firefox, for some reason itunes will not download and I don't know if using googlechrome will also have problems,so just to be sure that it will work on your first try, use internet explorer when you download itunes. Good LUCK!!

Airport Problems after Security Update 2007-004

Ever since I've installed Security Update 2007-004 my Airport connection has been dropping about every 15 to 30 minutes. Sometimes Airport will stay connected but will stop working until I renew my DHCP lease (I get the same IP though). When it drops I click on the Airport icon to reconnect but my network doesn't always show up. Sometimes I have to turn Airport off and back on again to make it show up, and a few times I've had to reset my computer to make it show up.
I have a MacBook Pro with an 802.11n card. I'm using two different routers; one at work, and one at home. The work router is a Linksys N router while the one at home is a Linksys G router.
I've tried all the tricks. Repairing Permissions, deleting the extension caches, installing the standalone updater, but nothing is working.

Deleting AppleAirPort2.kext solved the problem for some...
http://discussions.apple.com/thread.jspa?threadID=934370&tstart=0
While others had to rollback the AppleAirPort.kext to version...
http://discussions.apple.com/thread.jspa?messageID=4310165&#4310165
Installing the Security update 1.0.1 from 5/01/2007 helped others. Reapplying the Combo Update again helped a couple of people.

Airport problems after 8/12 airport and security update

My MacBook Pro which had been working flawlessly since I got it last year received the airport and security updates distributed today. After the reboot my airport turns itself off after a few minutes and will not come back on and the computer seems to be running hotter than usual. Booting from a recent clone of the drive without the updates did not fix the problem and the card turned itself off a few minutes after the reboot and will not come back on.
Anyone having similar problems after the update?

Does your problem occur only when unplugged. If so, then maybe this update is for you: http://support.apple.com/downloads/AirPortClient_Update_for_MacBook_and_MacBookPro. Check it out, but use your own judgment in installing; not much info is provided.

Airport Problems after "AirPort Extreme Update 2008-001" (1.0)?

I recently installed the update and have been unable to connect to my wireless network at home ever since. The airport detects my router and asks if I would like to join the network, but after I click yes, it says "there's an error in connecting", and thus no connection is made.
I can, however, get internet connection through ethernet from my router.
I can't be totally sure the update is the cause of the problem, but I haven't downloaded or installed anything else recently, and all other pc's wireless connections work fine with my router. I also haven't tried connecting through other wireless networks, so I'm not sure if the problem is exclusive to my router.
Has anyone else had similar problems after the update?
Also, does anyone know the default settings for the airport? I'm wondering maybe I have altered settings that's causing this problem.
Any help is greatly appreciated

I have the same problem but I have not found a fix.

Multiple Samsung Stratosphere problems after FF1 update

There have been multiple posts on various issues users have found after the recent Stratopshere FF1 update. Some were replys to older posts and some only touched on a single issue. I wanted to consolodate into one thread, and hopefully get teh attention of Verizon to maybe reply here.
For reference, a lot has been discuss here --> https://community.verizonwireless.com/message/874446
Summary: Verizon and Samsung have finally updated the Stratosphere almost 1 year after release. This updated the phone from Android 2.3.5 to Android 2.3.6. Going by filename, this is known as the FF1 update. This update went live at the end of August 2012, and most users were upgraded before mid September 2012.
There were some noticable changes in this update:
-Lock screen has changed. The puzzle piece and glass lock options have been removed. New options have been added, such as facial recognition unlock.
-Call answering screen has changed, introducing the option to ignore call with a message.
-Camera now has digital zoom ability.
-Ability to uninstall the 2 games the phone comes with (Need for Speed and Lets Golf)
-Phone icon has changed ever so slightly
-Wifi icon now included up and down arrows to indicate data is being sent or recieved
-Wallpaper no longer "stretches" over multiple screens - ie, it no longer scrolls as you move from screen to screen
-The visual voicemail app has been improved (I have personally not used this feature)
-Callback number is now supported in text / picture messages
-Android core OS updated from 2.3.5 to 2.3.6 (both versions are still Gingerbread)
-Update to how the device deals with the end of scrolling. It used to rubber-band bounce back, now it will just give a green bar and expand the bar as you scroll. (I cannot fault Samsung for this change as this was at teh core of an Apple lawsuit and has been changed in newer versions of Android.)
-(I am sure there are more. please list any others you may have noticed)
I have found some problems, and others have confirmed that this is (at least) somewhat widespread:
-The biggest problem is with wifi connectivity. Upon an initial connection to wifi, everything works great. After somewhere between 15minutes and 2 hours, problems start happening. Its as if the wifi keeps hanging or reconnecting. Download speeds (tested with the SpeedTest.com app) slow to about one third of normal. Apps like Facebook that require a constant connection will just time out.
-It appears the signal strength for 3g and 4g connections is lower. There are places where I used to get a 4g connection, and now I only get 3g. Some palces I fall back to just 2g digital.
Another minor issue i found was with text messages. When you reply to a message, it no longer automatically focuses the text in the input box. You have to first click into the box to start typing. Not a huge deal, but one more step to take over and over. Minor annoyence.
At my house, I struggle to get a 3g or 4g signal. I depend on wifi for my data connection. So with the wifi connection problem introduced by teh FF1 update, my phone is somewhat useless to me now while at home. Here are teh troubleshooting steps I have been through so far to attempt to fix the wifi problem:
-Complete factory reset on my phone. (did not help)
-Pull battery and SIM card out of phone for 15 minutes. (did not help)
-Went to a Verizon store. The guy at the store was helpful, and said he also had a Stratosphere and was getting the same wifi problems after the update. He said all he could do was to send me out a replacement phone. I got the replacement phone, and it had the same problems.
-I read in multiple palces that Android 2.3.6 has a bug within wifi and DHCP. Apparently if you have a DHCP lease set to "forever", the phone will keep requesting a new address. Setting the DHCP server on the router to something like 2 weeks, or using a static IP is supposed to solve this. I have a NetGear N900 router, and I can not change teh DHCP lease time. It appears, however, that my router is not sending out "forever" leases. But just to make sure, I gave my phone a static IP. (None of these steps made any difference).
The only thing that temporarily fixes the problem is a reboot of the phone. This will again give you anywhere from 15min to 2 hours of good wifi use before problems start happening.
I have now had this update for over a week, and on 2 phones. I still can't maintain a wifi connection for much longer than 15 minutes without problems starting up.
I am asking Verizon or Samsung to at least confirm this issue if possible. Maybe there are newer revs of the Stratopshere hardware that don't have this problem. Or there is something unique about my (and apparently others) situation. But it seems like Verizon's current stance is to offer a repalcement phone (as currently all Stratospheres are within their 1 year manufacture warranty as the phone has not been ouy for quite 1 year yet).
I am asking for a workaround for this problem, or a true fix adressed by a new software update, or at least allow us to roll back to the original Andorid 2.3.5 software.
I have had my original Stratosphere for almost a year with no wifi problems - then get the FF1 update and have had nothing but problems on 2 different phones.
Thank you for your time.

Thanks for starting a comprehensive thread on problems with this update. I want to add one more.
I have Bluetooth in my car (a 2004 model), and previously the phone has connected to it practically instantly when I start the car. Since the update, I have never been able to connect the phone to the car by Bluetooth. Several times the phone has made a standard notification sound at the moment it should be connecting to Bluetooth, though no notification appears. I have no idea what that could mean.The car's Bluetooth shows up as paired in the list of devices in Settings > Wireless & networks > Bluetooth settings. I haven't seen this widely reported as an update issue, but perhaps some others have experienced it too.
UPDATE: I finally did some testing, and found that the notification was to signal the extremely brief appearance of a dialog indicating that the car's Bluetooth was requesting a connection. Accepting that request let the phone connect with the car, and calls went to the car's sound system as they should. When I turned the car off and back on (just the electrical system; not wasting any gas on this!), the connection was established immediately, so apparently the acceptance only had to be done once. Nevertheless, it did have to be done, and the dialog notification disappears within seconds. I believe it would have been possible to go into Bluetooth settings and accept the connection request there if I missed the notification; but not seeing the notification, I might not know to do this.
One further observation: When I turned the phone's Bluetooth off and back on after a connection had been established, leaving the car on the whole time, the two did not reconnect. I believe that may be different from before the update, but I'm not really sure.
Message was updated by David Rensberger

EFI Problems after last update anyway to downgrade ??

Hello
EFI Problems after last update anyway to downgrade ??
i have updated my MacBook 2010 EFI to MB71.0039.B0E which is 2.1 version
after updating to this version the Boot time become much slower when i want to change boot partition
and shutdown become very much slower and startup too
i tried to install Mac OS X Lion again but it doesnt help
can i downgrade to this version 2.0 ???
or when Apple will release the new version ?
or where can i send a feedback regarding this issues !!!!
Thanks

These are user to user forums. If anyone knows the answer, they will give it.
You can always call Apple support which may charge a fee or you can patiently wait for an answer here, which is free.

Share and save problem after latest update

hello,
i have share and save problem after latest update - i have installed ps touch on nexus 5 about 2 months ago and until yesterday everything was good but after latest update i can't save and share images in ps touch ( i do reinstall this app but problem is still and app doesn't work properly ) how can i downgrade to the old version ? Could you fix this problem quickly ?

i use app which called "aLogcat"
--------- beginning of /dev/log/main
I/dalvikvm(24476): Enabling JNI app bug workarounds for target SDK version 11...
D/dalvikvm(24476): GC_CONCURRENT freed 174K, 2% free 17054K/17264K, paused 2ms+2ms, total 15ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
--------- beginning of /dev/log/system
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=27743080, downTime=27743066, deviceId=4, source=0x1002 }
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=27743086, downTime=27743066, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_FOR_ALLOC freed 122K, 1% free 17271K/17428K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 10K, 1% free 17434K/17604K, paused 7ms, total 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 65K, 2% free 17690K/17928K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 17.615MB for 328336-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18010K/18252K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18011K/18252K, paused 9ms, total 9ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.073MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18479K/18724K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 18481K/18724K, paused 2ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 6ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.532MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18949K/19196K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 19418K/19668K, paused 1ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19592K/19844K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 20.049MB for 933136-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 20503K/20756K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 21416K/21668K, paused 1ms+1ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 50K, 2% free 22351K/22580K, paused 7ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 5K, 1% free 23900K/24140K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 1% free 25824K/26084K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3411K, 14% free 24528K/28204K, paused 12ms, total 13ms
D/dalvikvm(24476): GC_CONCURRENT freed 2814K, 14% free 24256K/28204K, paused 2ms+1ms, total 11ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9266K, 1% free 17270K/17424K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 15K, 1% free 17575K/17748K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 22K, 2% free 17875K/18072K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 2% free 18195K/18396K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18517K/18720K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18838K/19044K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19159K/19368K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19480K/19692K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19974K/20192K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 20616K/20840K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 21431K/21664K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 22714K/22960K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 2% free 24004K/24432K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8478K, 33% free 17593K/26228K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 32% free 17895K/26228K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 31% free 18198K/26228K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18519K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 29% free 18840K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19482K/26228K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 23% free 20297K/26228K, paused 2ms+1ms, total 15ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 19% free 21260K/26228K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22543K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 9% free 23979K/26228K, paused 21ms, total 22ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8485K, 33% free 17598K/26132K, paused 13ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 25K, 32% free 17894K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 12K, 31% free 18204K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18524K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 28% free 18845K/26132K, paused 8ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19487K/26132K, paused 1ms+0ms, total 9ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 20129K/26132K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 20% free 21091K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22375K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9K, 9% free 24011K/26132K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 2147K, 10% free 23855K/26456K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed 8776K, 35% free 17337K/26304K, paused 3ms+2ms, total 20ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=564.0, y[0]=-50.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=28190972, downTime=28190972, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_CONCURRENT freed 186K, 31% free 17626K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 63K, 30% free 17884K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3K, 29% free 18201K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 27% free 18696K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 25% free 19190K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 19831K/25476K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 19% free 20794K/25476K, paused 2ms+0ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 14% free 22078K/25476K, paused 1ms+2ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 7% free 23855K/25476K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 6% free 24176K/25476K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 6440K, 26% free 19562K/26216K, paused 9ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 93K, 23% free 20207K/26216K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 11K, 21% free 20935K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 18% free 21673K/26216K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22499K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 10% free 23695K/26216K, paused 9ms, total 9ms

IPhone 4s got problem after I update to 7.1.1. Battery drain so fast

iPhone 4s got problem after I update to 7.1.1. Battery drain so fast

The Ultimate Guide to Solving iOS Battery Drain
<http://www.overthought.org/blog/2014/the-ultimate-guide-to-solving-ios-battery-d rain>

Had a problem after download updated itune, error 7 (window error 126) cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

Please Read This To Reduce or Eliminate Problems after Software Update

Hi all, I have been reading quite a handful of Mac users here reporting problems ranging from minor ones like slow downs to major ones like application crashes, and many of them blame the new OS and/or Security Updates.
Without learning more from the details of how did they perform their Software Updates and Install, I am making a huge assumption that it maybe something they did or didn't do, one of the key things they did not do is Repair Disk Permission
Below is what I called, the "ritual procedure" needed to perform before and after a Software Update, and also any other major software installation - to help reduce or eliminate "hiccups" afterwards, I cannot gaurantee that all macs all over the world will not suffer any problems after an update, but by doing so, you may help reduce it; I have 4 macs all together and so far I have not encounter any major problems after many versions updates.
Anyway, I didn't come out with this series of procedures, I read it off somewhere in this Discussion quite a while ago, and thought I share it again with all of you:
1.Before starting Software Update, unplug all external devices, FireWire, USB, hubs etc etc, not just turning them off but unplug the cables off your Mac, leave only your keyboard, mouse and internet connection on (unless you are using a wireless keyboard and/or mouse or on wireless internet)
2.Repair Disk Permission
3.Restart the Mac, then start your SU, do not run any other apps.
4.After finishing SU, restart your mac; If you are updating OS or Security Updates, Restart is required.
5.Repair Disk Permission again
6.Shutdown and re-plug in everything and start up your mac as normal.
I know the procedure is pretty long and "troublesome", especially the unplugging and restarting part, but so far it really has done my macs good, so I am going to "swear" by it... my FireWire, USB devices etc still work as normal.
This is really contrary to that "Macs are easy to use", yes, no doubt about it, but the software updates etc is just well, put it this way: The Mac OS when it comes to updates, is very very delicate... so handle with it great care, it will just turn out okay.
Cheers

Thank you for posting that. I posted a similar set of suggestions here:
http://www.macmaps.com/backup.html
Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

After Leopard Update this AM, My Airport Card is Disabled!

I ran the small Leopard update this morning. After a reboot, my 24" iMac's (aluminum) airport card is disabled. Mac OS X 10.5 says that no airport card is installed. I tried rebooting again, but no luck. This is totally unacceptable. I have never had such issues with Apple before. My only reprieve was to plug in an ethernet cable. Under "About This Mac" it does not show an Airport card is installed any longer. Please help!

Just found a solution to the problem with this post:
"Can you guys having problems check if the AppleAirPort2.kext is still present in your /System/Library/Extensions folder? It is an older Tiger-only AirPort driver that is no longer used on Leopard. You can simply delete it, or move it aside by changing the extension to something besides .kext. See if that fixes your problem."
I removed this file and without restarting, AirPort appeared again.

Airport Problems after update and trouble shooting

Hi There,
I have an Intel iMac and after updating airport i've been having problems with it. I'll be using the internet and all of a sudden it will just disconnect and cannot detect any network connections. Now, i've seen the other posting already about fixing this problem, and I have done what it says to fix the problem by moving the system configuration folder and the com.apple.systempreferences.plist file. After I do this, it works for a few hours but then i have the same problem again. The folder and the file is recreating and i have to follow the same steps and move them again, but then every few hours it keeps getting recreating. Is there something that i can do so i'm not constantly moving the files around and having to re-setup my network. Is there a way to reset Airport to the way it was before i installed the update?
Thanks

"Is there a way to reset Airport to the way it was before i installed the update?"
Of course you can erase your hard drive and reinstall up to 10.4.7, and not go any higher. The problem is the 10.4.8 update, or some part of it. The many other updates recently posted for different apps are not part of the cause, so those updates can be installed.
"Is there something that i can do so i'm not constantly moving the files around and having to re-setup my network."
Yes, once you've followed the "restart twice" instructions involving preference file deletion, it appears that by turning off AirPort before letting it sleep, restart, or shut down, those two files will not get the same corruption recreated. Afterwards, you should be able to turn on AirPort and after a slight delay of about six to eight seconds AirPort will be able to reacquire your network.
If you forget to turn off AirPort before sleep, restart, or shutdown, then those files will again be corrupted and you'll have to go through the process all over again. I ran through it about 50 times, changing this and that, and that's all I could come up with.
Hopefully someone else out there with a different perspective will be able to figure out what else needs to be done.

Airport problems after update

I have been using my 20" Intel iMac for a few months now and have had no problems getting the built-in airport device to connect to my wireless home network. Yesterday, I downloaded and installed the new airport system update, and ever since I've been having big trouble. It doesn't show any available network connection at all (and I know my wireles network is working because my laptop can still connect). If I restart the computer, sometimes it will find my network and sign on, but then it drops the connection after just a few minutes and goes back to saying it can't detect any available networks. Has anyone else had any problems since the new update? Any suggestions on what to do? Thanks.

Unfortunately, I can't get any of your suggestions to work. If I restart the computer and go through the Network Diagnostics set-up, I can sometimes get it to find my home network and connect, though not everytime. The connection might last from 2 minutes to an hour or more, but then it is inevitably lost, and Airport shows no available networks, even though my MacBook is still connected to my home network and shows several other available networks from neighbors' houses, too. It seems like it must be a software problem since I had no problems before the update. Does anyone know anything else I can try short of taking it in to an Apple Store? Thanks for all your suggestions.

Airport problems after update Airport Extreeme 2008-004 V.1

Since when i have installed the update Airport Extreeme 2008-004 V.1 my Airport card is giving me problems. The network seams to go down and if i reset the Airport it restart working for a certain time. I have noted that the problem apears most of the times when Time Machine starts the backup on the Capsule (but this is not 100% sure).
I am quite sure the problem is the update because i never had this before.
This is the log..
03/11/08 17:10:31 kernel AirPort: Link Down on en1
03/11/08 17:10:31 configd[14] AppleTalk shutdown
03/11/08 17:10:31 kernel vmnet: bridge-en1: interface en is going DOWN
03/11/08 17:10:31 kernel vmnet: bridge-en1: interface en is going DOWN
03/11/08 17:10:31 configd[14] AppleTalk shutdown complete
03/11/08 17:10:32 mDNSResponder[16] ERROR: mDNSPlatformTCPConnect - connect failed: socket 47: Error 50 Network is down
03/11/08 17:10:32 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096459555
03/11/08 17:10:32 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096459555
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096459798
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096459798
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096460048
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096460048
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096460298
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096460298
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096460549
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096460549
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 4096460649
03/11/08 17:10:33 mDNSResponder[16] mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00823000 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 4096460649
03/11/08 17:10:35 kernel en1: 802.11d country code set to 'IT'.
03/11/08 17:10:35 kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 40 48 56 64 104 112 120 128 136 36 44 52 60 100
03/11/08 17:10:35 kernel vmnet: VMNetDisconnect called for port 0x560bc00
03/11/08 17:10:35 kernel vmnet: bridge-en1: filter detached
03/11/08 17:10:35 kernel vmnet: bridge-en1: down
03/11/08 17:10:35 kernel vmnet: bridge-en1: detached
03/11/08 17:10:35 kernel vmnet: Freeing hub at 0x4516800.
03/11/08 17:10:38 kernel Auth timed out
03/11/08 17:10:38 airportd[776] Error: Apple80211Associate() failed -6
03/11/08 17:10:38 airportd[776] Could not find any preferred networks; trying broadcast requests..
03/11/08 17:10:42 ntpd[27] sendto(17.72.255.11) (fd=27): Can't assign requested address
03/11/08 17:10:43 kernel MAC AUTH succeeded
03/11/08 17:10:43 configd[14] AppleTalk startup
03/11/08 17:10:43 kernel AirPort: Link Up on en1
03/11/08 17:10:43 kernel vmnet: VNetUserIf_Create: created userIf at 0x8a8e000.
03/11/08 17:10:43 kernel vmnet: VMNetConnect: returning port 0x8a8e000
03/11/08 17:10:43 kernel vmnet: Hub 0 does not exist, allocating memory.
03/11/08 17:10:43 kernel vmnet: Allocated hub 0x58b7000 for hubNum 0.
03/11/08 17:10:43 kernel vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e7:76:aa
03/11/08 17:10:43 kernel vmnet: Hub 0
03/11/08 17:10:43 kernel vmnet: Port 0
03/11/08 17:10:43 kernel vmnet: bridge-en1: got dev 0x47e2604
03/11/08 17:10:43 kernel vmnet: bridge-en1: wireless interface detected.
03/11/08 17:10:43 kernel vmnet: bridge-en1: up
03/11/08 17:10:43 kernel vmnet: bridge-en1: attached
03/11/08 17:10:43 kernel vmnet: VNetUserIfFree: freeing userIf at 0x8a8e000.
03/11/08 17:10:48 com.apple.launchd[1] (org.samba.nmbd) Throttling respawn: Will start in 3 seconds
03/11/08 17:10:48 configd[14] AppleTalk startup complete
03/11/08 17:11:00 kernel AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Disco Time Capsule
03/11/08 17:11:00 kernel AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Disco Time Capsule
03/11/08 17:13:55 ntpd[27] time reset +1.161678 s
03/11/08 17:16:48 /usr/sbin/ocspd[796] starting
03/11/08 17:24:54 kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Disco Time Capsule
Do you know how to remove the update ?
Thanks
M.

Did you disconnect all devices from your computer when troubleshooting? Did you restart your computer?
If yes to the above, you may wish to try the repair disk option. Run +repair disk+ from your software install DVD.
"How to get support from Apple ?"
By calling Apple Tech Support.
CLICK---> International Support Phone #s to find the Italia number.
If you have AppleCare and/or your computer is still under its one year warranty, the call is free. If you are out of warranty, you will be charged for tech support.
Please be advised that these are _*user to user*_ forums.
"This is software bug !"
Then notify Apple by completing CLICK---> Product Feedback
The only way I know of removing AE update is to do an Archive & Install. Then use Software Update to upgrade your OS and software. Stop at the AE upgrade you do not want.
http://docs.info.apple.com/article.html?artnum=301270 Scroll down to "Archive and Install”
IMPORTANT: Make sure you select "preserve user preferences and data" when you performed the A&I?

Airport problems after leopard update

Similar Messages

Maybe you are looking for