Extending wireless network fails after 7.5.2 update

I have two Airport Extremes; one creating a network that is allowed to be extended and the other is used to extend the network. This worked fine until the 7.5.2 update I installed. Now the relay is unable to connect and I get the error "This wireless network cannot be extended". All I did was to update the firmware on both airports; I am running the latest 5.5.2 Utility, latest Snow Leopard.
Did Apple break this feature?

Welcome to the discussions, Paul!
Did Apple break this feature?
Not that we can tell based on forum questions, and our own experience, but anything is possible, especially if you tried the update over wireless.
Have you power cycled the complete network? If not...
Power everything down, order is not important. Wait a few minutes
Start the modem first and let it run by itself for 4-5 minutes
Start your AirPort Exptreme the same way
Start your AirPort Express the same way
Start your devices the same way
Any other troubleshooting steps that you have taken to this point?

Similar Messages

Wireless networking fails after AirPort Extreme Update 2007-003

I have just tried installing AirPort Extreme Update 2007-003 on a MacBook Pro and wireless networking, which used to work, now no longer works.
My wireless network consists of the MBP and a Thomson Speedtouch 585 ADSL modem/router.
The symptom is that no connection can be obtained - the Airport menubar item flashes continually about once a second, as does the WLAN activity light on the 585.
The Console.log reports (repeatedly) that "configd crashed" and the corresponding information in /Library/Logs/CrashReporter/configd.crash.log says that:
"Command: configd
Path: /usr/sbin/configd
Parent: launchd [1]
Version: ??? (???)
PID: 473
Thread: 1
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0xb1e0cf60"
(There is a lot more diagnostic info - which I can supply if it helps)
All system software is up to date (Tiger 10.4.9) - I had just run the system updater.
If I disable Airport (i.e. wireless networking) and connect the MBP to the 585 by Ethernet, then it all works fine.
Something similar happened to my system about 4 weeks ago - I got around it that time by rerunning the MacOS 10.4.9 Combo update - but this time that doesn't work.
Any suggestions on why configd is crashing and how to stop it?
MacBookPro 15" Core Duo Mac OS X (10.4.9)

Thanks for your help
Curiouser & curiouser!
My answer was going to be that keychain had nothing to do with the problem. If I log in as a different user (even a freshly-created one), I still get the same symptoms. I was also getting the same symptoms with a rescue copy of 10.4.9 on an external hard disk.
However, I thought I would have a look at my keychain using the Keychain Access utility (which, I seem to remember, has some recovery/repair functions). Lo and behold, the Keychain Access utility crashes after about 2 seconds and the crash report in ~/library/logs looks similar to one for configd. Here is a sample:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Host Name: Wombat
Date/Time: 2007-05-06 23:08:16.114 +0100
OS Version: 10.4.9 (Build 8P2137)
Report Version: 4
Command: Keychain Access
Path: /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
Parent: WindowServer [71]
Version: 3.3.2 (27693)
Build Version: 64
Project Name: KeychainAccess
Source Version: 276930000
PID: 2302
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0xc3110ce0
Thread 0 Crashed:
0 libstdc++.6.dylib 0x90b4441a cxxabiv1::__si_class_type_info::__do_upcast(__cxxabiv1::__class_typeinfo const*, void const*, _cxxabiv1::__class_type_info::__upcastresult&) const + 54
1 libstdc++.6.dylib 0x90b4442e cxxabiv1::__si_class_type_info::__do_upcast(__cxxabiv1::__class_typeinfo const*, void const*, _cxxabiv1::__class_type_info::__upcastresult&) const + 74
2 libstdc++.6.dylib 0x90b43fb7 cxxabiv1::__class_type_info::__do_upcast(__cxxabiv1::__class_typeinfo const*, void**) const + 69
3 libstdc++.6.dylib 0x90b43c27 cxxabiv1::__class_type_info::__do_catch(std::typeinfo const*, void**, unsigned) const + 57
4 libstdc++.6.dylib 0x90b42d45 _cxa_getglobals + 351
5 libstdc++.6.dylib 0x90b4342a _gxx_personalityv0 + 658
6 libgcc_s.1.dylib 0x90bd7acb UnwindRaiseException + 147
7 libstdc++.6.dylib 0x90b43747 _cxathrow + 87
8 com.apple.security 0x9117319b Security::CssmError::throwMe(long) + 91
9 com.apple.security 0x911750e3 Security::KeychainCore::KCCursorImpl::next(Security::KeychainCore::Item&) + 123
10 com.apple.security 0x91174f1d SecKeychainSearchCopyNext + 125
11 com.apple.keychainaccess 0x00009456 0x1000 + 33878
12 com.apple.keychainaccess 0x00008f18 0x1000 + 32536
13 com.apple.keychainaccess 0x00008beb 0x1000 + 31723
14 com.apple.keychainaccess 0x0000874a 0x1000 + 30538
15 com.apple.keychainaccess 0x000085ad 0x1000 + 30125
16 com.apple.keychainaccess 0x00008477 0x1000 + 29815
17 com.apple.keychainaccess 0x00007db7 0x1000 + 28087
18 com.apple.Foundation 0x927df17b nsnotecallback + 230
19 com.apple.CoreFoundation 0x908573e6 __CFXNotificationPost + 345
20 com.apple.CoreFoundation 0x9084ebd1 _CFXNotificationPostNotification + 600
21 com.apple.Foundation 0x927d7724 -[NSNotificationCenter postNotificationName:object:userInfo:] + 121
22 com.apple.keychainaccess 0x0000322c 0x1000 + 8748
23 com.apple.Foundation 0x927de6c9 -[NSNotificationCenter postNotificationName:object:] + 55
24 com.apple.keychainaccess 0x0000340c 0x1000 + 9228
25 com.apple.AppKit 0x93281e94 -[NSApplication _postDidFinishNotification] + 124
26 com.apple.AppKit 0x93281d7e -[NSApplication _sendFinishLaunchingNotification] + 67
27 com.apple.AppKit 0x9328187d -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 273
28 com.apple.AppKit 0x93281448 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 96
29 com.apple.Foundation 0x927e4e65 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 447
30 com.apple.Foundation 0x927e4c8f _NSAppleEventManagerGenericHandler + 91
31 com.apple.AE 0x9151afb5 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 147
32 com.apple.AE 0x9151aee6 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
33 com.apple.AE 0x9151adb2 aeProcessAppleEvent + 190
34 com.apple.HIToolbox 0x92ddc0e4 AEProcessAppleEvent + 37
35 com.apple.AppKit 0x9327f63d _DPSNextEvent + 1044
36 com.apple.AppKit 0x9327f056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
37 com.apple.AppKit 0x93278ddb -[NSApplication run] + 512
38 com.apple.AppKit 0x9326cd2f NSApplicationMain + 573
39 com.apple.keychainaccess 0x00003146 0x1000 + 8518
40 com.apple.keychainaccess 0x00014755 0x1000 + 79701
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xc3110ce0 ebx: 0x90b436fd ecx: 0xbfffead0 edx: 0xa11a6680
edi: 0x003d1be0 esi: 0xa11a66c0 ebp: 0xbfffea98 esp: 0xbfffea80
ss: 0x0000001f efl: 0x00010287 eip: 0x90b4441a cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
Binary Images Description:
0x1000 - 0x46fff com.apple.keychainaccess 3.3.2 (27693) /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
0x8fe00000 - 0x8fe4afff dyld 46.12 /usr/lib/dyld
0x90000000 - 0x90172fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901c2000 - 0x901c4fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x901c6000 - 0x90203fff com.apple.CoreText 1.1.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x9022a000 - 0x90300fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x90320000 - 0x90775fff com.apple.CoreGraphics 1.258.61 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x9080c000 - 0x908d4fff com.apple.CoreFoundation 6.4.7 (368.28) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90912000 - 0x90912fff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x90914000 - 0x90a07fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a57000 - 0x90ad6fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aff000 - 0x90b63fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
0x90bd2000 - 0x90bd9fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x90bde000 - 0x90c51fff com.apple.framework.IOKit 1.4.6 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90c66000 - 0x90c78fff libauto.dylib /usr/lib/libauto.dylib
0x90c7e000 - 0x90f24fff com.apple.CoreServices.CarbonCore 682.21 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x90f67000 - 0x90fcffff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x91007000 - 0x91045fff com.apple.CFNetwork 129.20 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x91058000 - 0x91068fff com.apple.WebServices 1.1.3 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x91073000 - 0x910f1fff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x91126000 - 0x91144fff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x91150000 - 0x9115efff libz.1.dylib /usr/lib/libz.1.dylib
0x91161000 - 0x91300fff com.apple.security 4.5.2 (29774) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913fe000 - 0x91406fff com.apple.DiskArbitration 2.1.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9140d000 - 0x91414fff libbsm.dylib /usr/lib/libbsm.dylib
0x91418000 - 0x9143efff com.apple.SystemConfiguration 1.8.6 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x91450000 - 0x914c6fff com.apple.audio.CoreAudio 3.0.4 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x91517000 - 0x91517fff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x91519000 - 0x91544fff com.apple.AE 314 (313) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x91557000 - 0x9162bfff com.apple.ColorSync 4.4.9 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x91666000 - 0x916d9fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x91707000 - 0x917b0fff com.apple.QD 3.10.24 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x917d6000 - 0x91821fff com.apple.HIServices 1.5.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x91840000 - 0x91856fff com.apple.LangAnalysis 1.6.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91862000 - 0x9187cfff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x91886000 - 0x918c3fff com.apple.LaunchServices 182 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x918d7000 - 0x918e3fff com.apple.speech.synthesis.framework 3.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x918ea000 - 0x91929fff com.apple.ImageIO.framework 1.5.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x9193c000 - 0x919eefff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91a34000 - 0x91a4afff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91a4f000 - 0x91a6dfff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91a72000 - 0x91ad1fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91ae3000 - 0x91ae7fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91ae9000 - 0x91b6dfff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91b71000 - 0x91baefff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91bb4000 - 0x91bcefff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91bd3000 - 0x91bd5fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91bd7000 - 0x91cb5fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x91cd2000 - 0x91cd2fff com.apple.Accelerate 1.3.1 (Accelerate 1.3.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91cd4000 - 0x91d62fff com.apple.vImage 2.5 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x91d69000 - 0x91d69fff com.apple.Accelerate.vecLib 3.3.1 (vecLib 3.3.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x91d6b000 - 0x91dc4fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x91dcd000 - 0x91df1fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x91df9000 - 0x92202fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x9223c000 - 0x925f0fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x9261d000 - 0x9270afff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x9270c000 - 0x92789fff com.apple.DesktopServices 1.3.6 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x927ca000 - 0x929fafff com.apple.Foundation 6.4.8 (567.29) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92b06000 - 0x92b10fff com.apple.framework.AppleTalk 1.2.0 (???) /System/Library/Frameworks/AppleTalk.framework/Versions/A/AppleTalk
0x92b14000 - 0x92b2bfff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92b36000 - 0x92b8efff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92ba2000 - 0x92ba2fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92ba4000 - 0x92bb4fff com.apple.ImageCapture 3.0.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92bc3000 - 0x92bcbfff com.apple.speech.recognition.framework 3.6 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x92bd1000 - 0x92bd6fff com.apple.securityhi 2.0.1 (24742) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x92bdc000 - 0x92c6dfff com.apple.ink.framework 101.2.1 (71) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x92c81000 - 0x92c84fff com.apple.help 1.0.3 (32.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x92c87000 - 0x92ca5fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x92cb7000 - 0x92cbdfff com.apple.print.framework.Print 5.1 (192.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x92cc3000 - 0x92d26fff com.apple.htmlrendering 66.1 (1.1.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x92d4a000 - 0x92d8bfff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x92db2000 - 0x92dbffff com.apple.audio.SoundManager 3.9.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x92dc6000 - 0x92dcbfff com.apple.CommonPanels 1.2.3 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x92dd0000 - 0x930c5fff com.apple.HIToolbox 1.4.9 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x931cb000 - 0x931d6fff com.apple.opengl 1.4.16 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93266000 - 0x93266fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x93268000 - 0x9391efff com.apple.AppKit 6.4.8 (824.42) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x93c9f000 - 0x93d1afff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x93d53000 - 0x93e0dfff com.apple.audio.toolbox.AudioToolbox 1.4.5 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x93e50000 - 0x93e50fff com.apple.audio.units.AudioUnit 1.4.2 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x93e52000 - 0x94013fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x94059000 - 0x9409afff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x940a2000 - 0x940dcfff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x940e1000 - 0x940f7fff com.apple.CoreVideo 1.4 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x94211000 - 0x94222fff com.apple.securityfoundation 2.2.1 (28150) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x94230000 - 0x9426efff com.apple.securityinterface 2.2.1 (27695) /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x9428a000 - 0x94299fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x942a0000 - 0x942abfff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x942f7000 - 0x94311fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x949f2000 - 0x94a0ffff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x94bbb000 - 0x94c93fff edu.mit.Kerberos 5.5.24 /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x95b86000 - 0x95b8afff com.apple.URLMount 2.1.7 /System/Library/PrivateFrameworks/URLMount.framework/Versions/A/URLMount
0x9742b000 - 0x9746afff com.apple.AppleShareClientCore 1.5.2 /System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShare ClientCore
So it looks as if something is messing up my keychain (all my keychains?) and that in turn crashes both configd and keychain access.
Do you have any suggestions on where to go from here? There are two issues:
How to stop keychain getting corrupted again?
How to repair the corrupted keychain if I can't use Keychain Acess? - can you just delete the keychain file and then re-enter passwords as and when necessary?
Meanwhile I can experiment with reloading my rescue copy of 10.4.9. If this fault is reproducable, then I guess I ought to file a bug report with Apple

Reganining (Wireless) Network Scanning after 10.8.2 update

Up to 10.8 I hab no issues printing and scanning wirelessly through my Canon MP620 whoch is connected directly to my Wireless network. They showed up as two devices (Printer / Scanner) in my System Preferences.
However, after updating to 10.8.2 - though the scanner was still there in the system prefs - it just didn't wotk anymore and would not be found.
the scanner worked well, since when connected directly to the Mac it showed up immediately and worked fine.
I tried a couple of things that didn't help before I came across the solution.
First, what didn't work:
- updating drivers through software update
- updating drivers through CANON
- reconfiguring the Printer/Scanner through Canon LJ Network Tool (Version 4.0)
- Restarting, rebooting machine, Printer etc.
What did help finally: Restarting printer system (right-click in print/scan prefs) and reboot.
Now the printer as well as the scanner showed up and could be re-added.
OPne more glitch I had to overcome was that the scanner was detected, yet it gave me a communication error that went away, after I printed the first page.
Now, everything works as expected.
Since there is a lot of discussions about this going on I thought I'd share this.

Very strange, you're not the only one with the old build#... I wonder...
Hmmm, did you try the direct download & install method?
http://support.apple.com/kb/DL1611
I think that's it, but shows the original date!?

802.1x Authentication for University Network Fails After 10.5.5 Update

Hi everyone, I hope that someone might be able to help me with my problem. I used to connect to the internet through my university's network at my dorm using the ethernet connection. Even before when I was using 10.5.4 I had to do the 802.1x authentication manually after every boot.
Now that I updated to 10.5.5 everytime I try to connect it tells me "802.1x Authentication has failed", does anyone have similar problems, solutions??? This is everything the IT department's homepage has to offer: http://www.unibz.it/ict/8021x_mac1/index.html?LanguageID=EN&
Thanks a lot!
Btw, it seems the update somehow messed up Timemachine as well, but that doesn't bother me as much as the internet connection.

Hi,
You probably need to install a root certificate into your Mac's system keychain so that your Mac knows it can trust the University's Certificate Authority (CA).
They should be able to provide you with a file for the CA and instructions.
cheers

Airport express can't extend wireless network

Airport express(A1264) can't extend wireless network. It seems that Airport express can't find my home Wi-Fi network. Amber light is blinking, and AirPort Utility of MacBook also can't find Airport express.
If AE is connected with TC via LAN cable, amber light is blinking with message "Wireless Network" (This Airport base station is set up to join a specific wireless network that can't be found...)
It was successful only once, but all failed after that.
Is there solution for this problem?
[My system]
Time capsule 4th generation
Airport express 1st generation (A1264)
[Settings]
Time capsule (ethernet connected)
- Create a wireless network
- 802.11a/n - 802.11b/g/n (Automatic)
- 2.4GHz / 5GHz Channel (Autmatic)
- WPA2 Personal
Airport express
- Extend a wireless network
- WPA2 Personal
- 2.4GHz Wi-Fi network name and Password is set up

If AE is connected with TC via LAN cable, amber light is blinking with message "Wireless Network" (This Airport base station is set up to join a specific wireless network that can't be found...)
Sorry, I misunderstood what you wanted to do.
Since you did tell us that you had the Express connected with an Ethernet cable, I assumed that was how you wanted to configure the Express.
But I want to extend a wireless network (not using ethernet)
Because Airport Express and Time Capsule cannot be connect via ethernet cable.
Follow the same setup as above....and do not connect an Ethernet cable.
Keep the Express near the Time Capsule for the setup. Once you have a green light, move the Express to a point that is about half way between the Time Capsule and area that needs more wireless coverage.
If you reset the Express several times and try the setup several times without success, I think you have to suspect a defective Express.

How do I know "Roaming Network" is working with Airport Express and Airport Extreme and should I use extended wireless network for third Express?

Attempting to eliminate a dead spot in Wifi coverage [and implement AirPlay] have one Airport Extreme 802.11n and two Airport Express 802.11n's.
http://support.apple.com/kb/HT4145
The Airport Extreme is of course connected to cable modem and Ethernet switch, and one Airport Express is connected to the Ethernet network. As per instructions for creating a "Roaming Network", Airport Express is set to same SSID, security type, and Password.
Questions:
1. How does the client device know which Airport to connect to? In other words, will it switch to the closer WiFi transmitter automatically? The WiFi reception problem is intermittent in the fringe areas so what I do not want it for it to stick with the more distant Airport Extreme in the basement when the Airport Express which is closer will work better.
2. How can I tell which of the Airports the attached client device is using?
The third Airport Express will be in a third location - I was planning on using it also for expanding coverage but after reading the warnings about performance suffering when purely using WiFi for the expansion in this location ("Wireless Extended Network" without an ethernet connection) I have figured that the single wired Airport Express will be adequate and will use the third Express to do Airplay only.
http://support.apple.com/kb/HT4259
Question: Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??
Mitch

1. How does the client device know which Airport to connect to?
The Mac computer will automatically connect to the wireless access point with the strongest signal...which is probably the closest AirPort. An iPhone or iPad may not do this and will tend to stay connected to one AirPort.
2. How can I tell which of the Airports the attached client device is using?
On a Mac, open Macintosh HD > Applications > Utilities > AirPort Utility. Click on one of AirPorts. In the area to the right, locate the AirPort ID and jot that down. Then do the same for your other AirPort.
Move your Mac near one of the AirPorts and log on to the wireless. Hold down the option key on the Mac while you click the fan shaped AirPort icon at the top of the screen. Look for the BSSID. That is the AirPort ID of the device to which you are connected.
If you are close to the "remote" AirPort, and you see the AIrPort ID of the "main" router when you are testing, then you know that the network is not configured correctly.
Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??
There will be a modest 10-15% bandwidth loss with the "extend" setup, assuming that the Express is located where it can receive a strong wireless signal from the AirPort to which it is associated. You can avoid the bandwidth loss if the Express is also connected via Ethernet as part of the roaming configuration.

I have installed Airport Extreme on my iMac, but want to extend the wireless network with Airport Express. Everything is fine until I try to select Extend the wireless network. I select Extend Wireless network but have no success. Ideas?

I have installed Airport Extreme on my iMac, but want to extend the wireless to rooms with a weak signal. The internet connection is fine with the basic setup. As soon as I go into Airport Utility to select Extend Wireless Network and fill in what I believe is proper information, I get an error message that Airport Extreme no longer has an IP address, the internet connection is broken, and under Wireless, that there is a wireless network in existence that can't be found. Rebooting the modem only brings the Airport Extreme back to the starting gate so that the internet is once again available. I assumed (naively) that with the All Mac All-the-Time context, adding Airport Express would truly be Plug and Play. I got the plug, but no play. I asked a Comcast technical specialist about it and he said that I needed to reset the Airport Express settings back to their default, factory status. I looked that process up online and found out that the way to do that was to hold down the reset button, then plug Airport Express into the socket and wait for the green light to flash four times. Then wait 45 seconds and the default settings will return. I did all that, only to find out that after the initial flash of green, green never appeared again. I got a fast flashing yellow light, followed by the light going off. Apparently this didn't reset it properly. So, after hours trying to get this system to work, I appeal to someone who can see through this mess and provide the key to success!
highFly376

Let's see if I can get this straight.
You have an Airport Extreme base station that is set to "Create a wireless network" and you have the box checked for "allow this network to be extended"....
Then you have an Airport Express that is set to "Extend a wireless network" which you selected the name of your network in the box...
Correct?
See this Apple document:
http://support.apple.com/kb/HT4259?viewlocale=en_US&locale=en_US
The wireless unit on the right of the diagram can be either of the newer Apple base stations.
Extreme, Express, Time Capsule

Extending wireless network many times – works with limitations (why?)

Hi all! I want to extend wireless network in big 2 floor house without ethernet cables. My current setup is attached in picture file.
Time Capsule – connected directly to Internet.
TimeCaps-Front – this is AirPort Express configured to extend network from Time Capsule.
TimeCaps-Back – this is AirPort Express configured to Bridge mode (it accepts local network via ethernet cable plugged to its WAN) and this AirPort creates new network with the same name and password as Time Capsule do.
2nd-floor-main – this is AirPort Express configured to extend the network from TimeCaps-Back (NOT from Time Capsule because 2nd extension doesn't work).
This setup is WORKS (unbelievable)!!!
But when Time Capsule is rebooted, any client can't connect to any base station, even to Time Capsule (error - connection timed out). For this solution work, it needed to reboot each device individually each after previous… Also I noticed, if after Time Capsule reboot, turn off "TimeCaps-Back" we can again connect our wireless clients to Time Capsule.
So the question is – how to optimize (if possible) this setup?

It sounds a bit corny to say that a chain is only as strong as its weakest link, but it remains a valid concept. In your case, the weakest link is the wireless connection between the Time Capsule and AirPort Express.
The reason for this is that an extending device can only extend the quality of signal or bandwidth that it receives. So, the stronger the connection at this point in the network, the better the whole network will perform in terms of speed and stabiity. At least half of your entire network depends on a single wireless connection between the Time Capsule and the AirPort Express.
If things are working fine, there may be no need to check further. If you want to be a bit more scientific, then you can use a good utility like WiFi Explorer to examine the Signal to Noise (SNR) at various points on the network.
In that regard, I would first measure the SNR of the Time Capsule signal at the location of the first Express to make sure that it was acceptable and even experiment if possible by moving the Express closer to the Time Caspule or minimimizing any obstructions that might be limiting the SNR at this point.
The wireless connection between the Time Capsule and AirPort Express supports the other half of the entire network, so any weakness at this link in terms of bandwidth will be passed down to the other devices on the network.

Multipmultiple Airport Extreme Base Stations: WDS Or "Extend Wireless Network" To Have Wired -- Wireless Bridge?

Hello there!
I've been looking for this info, but have as yet been unable to find it. Here's my scenario:
I have two Airport Extreme Base Stations (both are dual band) and 3 airport expresses. The main internet connection in my house is in one room, where I have an AEBS as the main wireless router. In another room, I have a bunch of ethernet-only devices. I'd like to use the 2nd AEBS in this room, plug the ethernet devices into it and have the 2nd AEBS act as a wired <--> wireless bridge (connected to the same wireless network as the 1st AEBS). I've attempted this via "extend a wireless network," but the ethernet devices don't get past the AEBS they're plugged into. Should I instead be implementing WDS?
I mention the airport expresses as I'd like to have airtunes & wireless signal in other areas, but would like to keep the set-up as simple as possible (i.e., not config the AXes for WDS unless it's required).
Thanks in advance for any help!

Unlike the 802.11n AirPort Express Base Station (AXn), the 802.11n AirPort Extreme Base Station (AEBSn) cannot be configured as a wireless Ethernet bridge.
However, there are at least two ways to configure it to provide wired clients access:
Connect the second AEBSn back to the first by Ethernet; reconfigure the second AEBSn as a bridge and disable its wireless radios, or
Reconfigure both AEBSns into an extended wireless network. For 802.11n AirPorts, this would be called a dynamic WDS. The AEBSn, connected to the Internet would be the "main" base station and it would only require that you enable the "Allow this network to be extended" option in the AirPort Utility. The extending AEBSn would need to be configured with the option, Wireless Mode = Extend a wireless network, enabled.
In both configurations, the second AEBSn's Ethernet ports would be enabled for wired clients.

Extend Wireless Network using a Telstra technicolor Gateway wireless Router to Airpot extreme but Airport will only except join not extend and I can not get a network on the Airpor Extreme ethernet ports but can ping Airport extreme from Technicolor Rout/

Extend Wireless Network using a Telstra technicolor Gateway wireless Router to Airpot extreme but Airport will only except "join a wireless network (which it does) not "extend a wireless network" (Led turns yellow and I can not get a network working on the Airpor Extreme ethernet ports but can ping Airport extreme from Technicolor Router.
Airport gets it address DHCP.

Funny how I can ping the Extreme but the Hard Ethernet ports dont seem to work correctly.
When the AirPort Extreme is configured to "Join" a wireless network, the Ethernet ports are not enabled.
Oddly, the AirPort Express has a special feature that will allow it to to "Join" virtually any wireless network.....and the Ethernet port can be enabled. So, an Express would work for your purpose to provide an Ethernet connection to the media player. This assumes that the Express is located where it can receive a strong wireless signal from your main router.
Note that the Express will not provide any additional wireless coverage when it "Joins".

Airport Express as very slow in "extend wireless network" mode

Hi!
I am using a Airport Extreme (fourth generation) as a wireless router and a Airport Express 802.11n in "extend wireless network" mode.
I've set the Airport Extreme mode to 802.11n only - and all devices connect to the Airport Extreme as 802.11n Clients properly.
But as soon as they connect to the Airport Express, they only work in 802.11b/g mode (although they are capable of n)
and the connection is very slow - around 1Mb/s:
http://imageshack.us/photo/my-images/804/bildschirmfoto20111211u.png/
Can i force the Airport Express station to accept only "n" connections to speed up my file tranfers?
Thanks for any help!
matt

Where is the AirPort Express located in relation to the area that needs more wireless coverage?
Ideally, it would be at a point that is about half the distance between the AirPort Extreme and the area that needs more wireless coverage....and....there would be no obstructions like walls and/or ceilings in the signal path....tough to do in most homes, so do the best that you can.
Avoid placing the Express down low on the wall and use an extension cord to get it up as high as possible with a free look into the room.
The Express will normally "extend" what it receives, but you could try the following to see if it helps:
Temporarily, change the Wireless Mode setting on the AirPort Express to "Create a wireless network" and change the Radio Mode to "802.11n only".
(You may have to hold down the option key on your Mac while you click on the Radio Mode selection box to see the "802.11n only" choice). Then change the Wireless Mode back to "Extend a wireless network" and Update.

Airport Express wouldn't extend wireless network

Am posting this in case it helps someone else. I have an Airport Extreme set up as a base station and couldn't get an Airport Express to "extend wireless network". I finally found a checkbox in the "Wireless" tab of the "Manually Configure" dialog box for the Extreme that says: "Allow this network to be extended". I could not find this referenced anywhere in Apple documentation, so you have to know to go and check this box. Apologies to the techies if this is a no-brainer, but I only found it by accident. Apple should include a brief paragraph in their wireless troubleshooting guide on extending your network.

When you configure the Express to "join a wireless network" it becomes part of the network so that you can stream AirTunes to the device or use a remote printer connected to the USB port, but it does not provide any additional wireless coverage in this type of configuration.
"Extend a wireless network" does the same thing as above, except the Express will also provide more wireless coverage in the area where it is located.

Extending Wireless Network with Airport Express / DLink Wireless

I have a DLink wireless router WBR-1310. I own two Airport Express 802.11n's. Can anyone help me out with how I can properly set-up an extended network with these products? All help is greatly appreciated.

You would need one AirPort Express located near the D-Link router and connected to the D-Link with an ethernet cable. This Express would be configured to "create a wireless network" and "allow this network to be extended"
If you have two areas that need more wireless coverage, you would locate an AirPort Express approximately 1/2 the distance between the "main" AirPort Express and the area that needs more wireless coverage.
Then do the same with the second area that needs more coverage.
Without knowing your room layout, I can't honestly tell you whether you need only one "extending" Express or more than that.
It will help to remember that the "extend" setup works like the hub and spokes of a wheel. Your "main" Express connected to the D-Link would be the "hub". Each of the "extending" Express devices would be at the end of a spoke. The Express devices at the ends of the spokes communicate directly to the hub, not to another Express at the end of another spoke.
So, to work well, hopefully your D-Link router and Express will be located in a central area of your home so the extending devices will work around the perimeter.
I would recommend that you study Apple's support document on extending wireless networks before you make a final decision on what to do.
http://support.apple.com/kb/HT4145
Finally, consider if you can connect the two Express devices you have now back to the D-Link using ethernet cables. This would provide much better performance than a wireless only situation.

Network mode: Create a wireless network vs. Extend wireless network via ethernet

Can some one tell me the difference between configuring AirPort Utility : Network mode: Create a wireless network vs. Extend wireless network via ethernet? I connect my cable modem to my Airport Time Capsule to a network switch via ethernet. The switch contacts to three Airport Express (AE connects to two Apple TVs via Ethernet) and another TC. Which is the best mode to configure my network?
Thanks

Create a wireless network is used only when the Airports have an Ethernet connection. If you are using the setup wizard.....the setting will read Extend using Ethernet during the setup. If you go back in using AirPort Utility to check the Network Mode setting.....you will see that it is really Create a wireless network.
Extend a wireless network is used only if an AirPort is connecting to another AirPort using wireless.......not Ethernet.
Every one of the Airports on your network must be configured to Create a wireless network.
If you do connect an Ethernet cable to an AirPort that is already set up to Extend a wireless network......that will create a massive feedback loop that will crash the network until you remove the Ethernet connection to the device.
The bottom line here might be if you are using the setup wizard, it will make the correct choice for you.

Extending wireless network with an aiport express

I have a netgear wireless router set up in my house on the second floor, but my room being located on the first floor i get a poor signal so i bought an airport express to extend my network. i tried going through the aiport exress setup assistant but that wouldnt work, so i ended up hooking it to my netgear router on the second floor to set it up in airport admin utility and then brought it back down to the first floor. my itunes worked with the speakers for about.. ten seconds then stopped. and my signal is just as weak as before.. any suggestions?

Unfortunately, it is simply not possible to use an Airport Express to wirelessly "extend" the wireless range of any model of Netgear wireless router. Netgear's wireless routers do not support Apple's implementation of a wireless distribution system (WDS), which is a necessary requirement for setting up an extended wireless network with the Airport Express. And no - it doesn't work the other way around either (Airport Express as base station, Netgear wireless router to "extend").
It sounds like you did successfully configure your Airport Express to "join" your existing wireless network - which will allow you to print and stream iTunes to the Airport Express. The problems you are having with Airtunes "hanging" on your Mac are almost certainly due to the poor wireless signal quality problem that you are already aware of.

Extending wireless network fails after 7.5.2 update

Similar Messages

Maybe you are looking for