AirPort Extreme Causes WinXP to Restart

I installed a new AirPort Extreme yesterday in compatabiity mode.
1. Works perfectly with my MacBook.
2. Works perfectly with my WinXP laptop.
3. Causes my WinXP desktop (freshly installed) to restart when attempting to connect to the network... every time.
There is no error message or blue screen... just a sudden restart. I suspect it is a compatibility issue with the Linksys WMP11 wireless network adapter and installed the latest driver from Linksys.
Are there any settings that need to be changed to correct this?

Thanks for the welcome.
In a sense, it is an AEBS issue as the Linksys adapter works with other routers. The problem began with the introduction of the AEBS into the network.
As in marriage counseling, the issue is not with one or the other but between the two (not that I would know).

Similar Messages

Have to reboot my airport extreme every time i restart my PC.

Hello,
Why is it that i have to reboot my Airport Extreme every time i restart my PC? I am able to connect to the network but not the internet, unless/until i restart my base station.
My phones and tablets are connected to the internet, so i know the my ISP is not the issue.

It is impossible to work this out without lots of details.
Like what PC OS do you run?
What connection, wireless or ethernet?
What you use test with the other if possible. Does it work for example swapping from wireless to ethernet??
I presume wireless as it is the most trouble prone.. When you start the PC does the wireless connect? Do you get IP by DHCP .. if so does it match what you get after a reboot.. look particularly at dns and gateway addresses.
Is the PC showing location as home or work/public.. it must be home to work properly.. also firewall might matter.
Also what type of wireless card is used.. poor windows drivers abound.. particularly Intel cards in laptops.
Is the wireless name SMB compliant.. ie short, no spaces and pure alphanumeric?
Is the wireless password mix of only case and numbers.. nothing non-alphanumeric?

Connecting HDD to Airport Extreme causes orange death light...

I am in a small office network with mix of pc and mac (7 pc's, 1 iMac, 1 wireless iMac, and 3 wireless macbook pro's). Internet connection comes into building directly to airport. Airport then feeds a couple of systems directly and a Dlink 24port ethernet switch which connects all other hardwired network connections.
I just purchased a Seagate Freeagent Desk 1.5TB external USB2 drive to be used as a network storage drive (not with time machine just grabbing and dumping files for interoffice sharing). Removed preloaded software and formatted fat32. Disk will be mounted and recognized when connected to any mac directly. When connected to the usb port on the airport extreme it begins to initialize and then bombs. Airport gives the orange death light and there is no connectivity to the router for all (ie internet connection, etc.) When you unglug the HDD the router reboots and then goes back to green light of peacefulness. What am I missing? Setting? Order of connection? Not hitting it hard enough on the ground with a large 10lb sledge hammer? Help me out...

you may need to restart the AEBSn with the drive plugged in.
since it might have been long since the AEBSn was restarted and anything else attached to it.
or a restore to factory settings...
i know not the best you want to hear, it should just work.
make sure all the AEBSn updates are there...etcetc
i was having this problem the past month or so and it started working again flawlessly after a few restarts.

Airport Extreme & Express in unending restart loop

After downloading and installing hardware/software updates (unsure which it was) for Airport Extreme and Express, the Airport Utility has for 24 hours been in an endless restart loop. I can't force quit the Airport Utility. There seem to be mention of a lot of similar problems and suggested solutions, but none make sense or have worked for others. Help anyone?

same here. using one Extreme as Access Point and second device to "extend" the 2.4 GHz network
"Jan 05 16:12:19 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
Jan 05 16:12:19 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
Jan 05 16:12:19 Gewichtung: 5 Rotated CCMP group key.
Jan 05 16:12:21 Gewichtung: 5 Internet configuration leased [IPv4] -- host <192.168.2.155/255.255.255.0> gateway <192.168.2.1> dns <192.168.2.1> wins lease <86400> domain <speedport.ip>
Jan 05 16:12:34 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
Jan 05 16:12:34 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
Jan 05 16:12:34 Gewichtung: 5 Rotated CCMP group key.
Jan 05 16:12:52 Gewichtung: 5 Disconnected from network.
Jan 05 16:13:05 Gewichtung: 5 Joined BSS 10:9a:dd:82:5e:fd
Jan 05 16:13:05 Gewichtung: 5 Installed unicast CCMP key for authenticator 10:9a:dd:82:5e:fd
Jan 05 16:13:05 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
Jan 05 16:13:05 Gewichtung: 5 Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
Jan 05 16:13:05 Gewichtung: 5 Rotated CCMP group key.
Jan 05 16:13:07 Gewichtung: 5 Internet configuration leased [IPv4] -- host <192.168.2.155/255.255.255.0> gateway <192.168.2.1> dns <192.168.2.1> wins lease <86400> domain <speedport.ip>
Jan 05 16:13:15 Gewichtung: 5 Disconnected from network.
"

My airport extreme has to be restarted to allow a new device to connect. How do I get it to connect automatically?

My airport Extreme will not allow new devices to join automatically. I have to restart it every time someone visits. Does anyone know how to get it to see new devices automatically?

In its default configuration, the AirPort Extreme Base Station (AEBS) has its DHCP Server service enabled which would "listen" for requests from network clients that have the counterpart DHCP Client enabled (this would be the clients' default as well).
It sounds like something is amiss with the DHCP Server service on your AEBS. I would recommend performing a "hard" reset on the AEBS to see if this resolves the problem.

Seagate Backup Plus 3 HFS formatted drive when plugged in to new Airport Extreme causes it to shut off and shows constant amber light. Please help.

I just purchased a new 3tb Seagate Backup Plus 3 to attach to my new Airport Extreme. When I plug the Seagate's USB in to the AE, the drive starts spinning, clicks and then the AE light turns amber and the wifi connection is lost. After I unplug the HDD the signal comes back and the AE light turns green. I have even tried using 3 partitions on the drive to see if that would work. I have a 1tb portable drive that has worked on the AE but this new drive doesn't. I have formatted both drives with Macdrive 9 pro and only the portable drive has worked. I've tried everything I could find on the internet to resolve this. I hope someone out there can help.

When it blinks amber, use the airport utility to peek at the status to see what error it's telling you. I'm guessing you MAY need to use a powered hub...

Airport Extreme causes ssh_exchange_identification for SFTP

I get ssh_exchange_identification during a client SFTP session to webserver behind a Load balanced server.
SFTP works with Lion and Snow Leopard but does not work with my Airport Extreme in place. SFTP also works with other firewalls in other networks. It seems the Airport is the culprit. This should be straight forward as its just a client session going out. Tried many modification to OSX but not sure if they are really needed since SFTP works fine without the Airport Extreme. Aiport is running 7.6.1. Below is the SFTP log.
$ sftp -v -v -v [email protected]
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX] port 22.
debug1: Connection established.
debug1: identity file /Users/USER/.ssh/id_rsa type -1
debug1: identity file /Users/USER/.ssh/id_rsa-cert type -1
debug1: identity file /Users/USER/.ssh/id_dsa type -1
debug1: identity file /Users/USER/.ssh/id_dsa-cert type -1
ssh_exchange_identification: Connection closed by remote host
Looks to me a connection is started on port 22 then gets clipped. Any help would be greatly appreciated.

my IP did not sure. i am positive of that.
The DNS problem is not constant, sometimes it works without pinging the others i have to ping manually.
by the way, i am trying to SSH into the same computer i am using :S
i know it is stupid not to SSH user@localhost
yes, @localhost works, but before that day, i used to ssh @my IP
HTTP works perfectly again, it was a DHCP error

Airport Extreme causing "Connection Failed" to connected disk

I have a relatively new Airport Extreme, with a MyBook 500GB external hard drive connected to it. There are 2 Macs (a MBP and Mac Mini) that backup to that hard drive wirelessly with Time Machine. Both Macs have no problem connecting to the disk drive for a couple of days or so, and then all of a sudden, Time Machine reports an error, and when trying to open the drive in Finder, I get the error message "Connection Failed". Every time this happens, I can fix it by unplugging the drive from the Airport Extreme, and plugging it back in. That will usually make it work for a couple of days, but sometimes less time than that.
I can't see it being a formatting issue with the disk, or any kind of connection issue, since it does work for a period of time. But why is does it suddenly stop working for both Macs?

Welcome to the discussions!
Your drive is formatted correctly if you have been able to make Time Machine backups.
Part of the problem may be that Apple does not officially support Time Machine backups to a drive at the USB port of the AirPort Extreme. That doesn't mean it won't work...it's just that Apple will not provide any help when difficulties arise with this configuration.
Some users report that this works well for them and others report intermittent to constant problems.
You might try using Disk Utility to check and repair permissions on your computers that are backing up to the Time Capsule.
Hard Drive > Applications > Utilities > Disk Utility
Click the disk on the left that exactly matches the name of the hard drive on your desktop. If you have not renamed it, it will be Macintosh HD.
Click Repair Permissions. This will take 30-60 minutes on average.

Airport Extreme Causing Mail to Quit?

Since I changed my internet connection to a wireless one, getting an Airport Extreme today, Mail quits whenever I try to reply to someone's email...very strange.
On a possibly unrelated note, Software Update doesn't recognize my internet connection, telling me that I'm not connected when I clearly am.
Any thoughts? Thanks.

I think this is what you're looking for (sorry if I pasted too much!):
Host Name: Lee-Cohens-Computer
Date/Time: 2007-03-19 07:02:44.011 -0400
OS Version: 10.4.8 (Build 8L2127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [74]
Version: 2.1.1 (752.3)
Build Version: 1
Project Name: MailViewer
Source Version: 7520300
PID: 737
Thread: 17
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x92644811 -[NSConnection sendInvocation:] + 2126
4 com.apple.Foundation 0x925fc148 -[NSInvocation invoke] + 174
5 com.apple.syncservices 0x95749607 -[ISyncConcreteManager _performSelectorOnServer:numberOfArguments:] + 961
6 com.apple.syncservices 0x9574a7b8 -[ISyncConcreteManager _performSelectorOnServer:withArg:withArg:] + 62
7 com.apple.syncservices 0x9576d58f -[ISyncConcreteManager _registerSyncAlertConnection:forClientWithIdentifier:] + 479
8 com.apple.syncservices 0x9576d86f -[ISyncConcreteManager setSyncAlertHandler:selector:forClient:notifyServer:] + 426
9 com.apple.syncservices 0x9577d85a -[ISyncConcreteClient setSyncAlertHandler:selector:] + 282
10 com.apple.Mail.Syncer 0x16babc43 0x16ba5000 + 27715
11 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
12 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
13 com.apple.MessageFramework 0x9a16cd7c _invokeInvocationRequest + 85
14 com.apple.MessageFramework 0x9a16c995 -[MainThread handlePortMessage:] + 154
15 com.apple.Foundation 0x92646a4c __NSFireMachPort + 307
16 com.apple.CoreFoundation 0x90839773 __CFMachPortPerform + 136
17 com.apple.CoreFoundation 0x90829a14 CFRunLoopRunSpecific + 2904
18 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
19 com.apple.HIToolbox 0x92dcdb90 RunCurrentEventLoopInMode + 285
20 com.apple.HIToolbox 0x92dcd1ce ReceiveNextEventCommon + 184
21 com.apple.HIToolbox 0x92dcd0ee BlockUntilNextEventMatchingListInMode + 81
22 com.apple.AppKit 0x9326f465 _DPSNextEvent + 572
23 com.apple.AppKit 0x9326f056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
24 com.apple.AppKit 0x93268ddb -[NSApplication run] + 512
25 com.apple.AppKit 0x9325cd2f NSApplicationMain + 573
26 com.apple.mail 0x00094df2 0x1000 + 605682
27 com.apple.mail 0x00094d19 0x1000 + 605465
Thread 1:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.unsanity.ape 0xc0001d12 _apeagent + 307
2 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 2:
0 libSystem.B.dylib 0x90048a47 semaphoretimedwait_signaltrap + 7
1 com.apple.Foundation 0x92693dbc FCONDITION_WAITTIMEOUT + 128
2 com.apple.Foundation 0x92693d06 -[NSConditionLock lockWhenCondition:beforeDate:] + 101
3 com.apple.MessageFramework 0x9a15f821 -[InvocationQueue _drainQueue] + 210
4 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 3:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x9262adc6 -[NSRunLoop runMode:beforeDate:] + 182
4 com.apple.Foundation 0x9262acc2 -[NSRunLoop run] + 75
5 com.apple.MessageFramework 0x9a1645af +[_NSSocket _runIOThread] + 97
6 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
7 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 4:
0 libSystem.B.dylib 0x90048a47 semaphoretimedwait_signaltrap + 7
1 com.apple.Foundation 0x92693dbc FCONDITION_WAITTIMEOUT + 128
2 com.apple.Foundation 0x92693d06 -[NSConditionLock lockWhenCondition:beforeDate:] + 101
3 com.apple.MessageFramework 0x9a15f821 -[InvocationQueue _drainQueue] + 210
4 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 5:
0 libSystem.B.dylib 0x90019d3c select + 12
1 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 6:
0 libSystem.B.dylib 0x90048a47 semaphoretimedwait_signaltrap + 7
1 com.apple.Foundation 0x92693dbc FCONDITION_WAITTIMEOUT + 128
2 com.apple.Foundation 0x92693d06 -[NSConditionLock lockWhenCondition:beforeDate:] + 101
3 com.apple.MessageFramework 0x9a15f821 -[InvocationQueue _drainQueue] + 210
4 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 7:
0 libSystem.B.dylib 0x90048a47 semaphoretimedwait_signaltrap + 7
1 ...apple.AddressBook.framework 0x9476c646 -[ABRemoteImageLoader workLoop] + 158
2 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
3 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 8:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x9262aa9b +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 259
4 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 9:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x92651c4e +[NSURLCache _diskCacheSyncLoop:] + 206
4 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
5 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 10:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x9262adc6 -[NSRunLoop runMode:beforeDate:] + 182
4 com.apple.Foundation 0x9262acc2 -[NSRunLoop run] + 75
5 com.apple.WebKit 0x9512064d +[WebFileDatabase _syncLoop:] + 198
6 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
7 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 11:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.MessageFramework 0x9a1664ff _handleRequestWithTimeout + 3189
4 com.apple.MessageFramework 0x9a16931e -[_NSSocket readBytes:length:] + 145
5 com.apple.MessageFramework 0x9a168f23 _readBytesFromSocket + 69
6 com.apple.MessageFramework 0x9a168da7 _fillBuffer + 469
7 com.apple.MessageFramework 0x9a168af3 -[Connection readLineIntoData:] + 51
8 com.apple.MessageFramework 0x9a1f68fe -[POP3Connection(PrivateCommands) copyReplyLineData] + 91
9 com.apple.MessageFramework 0x9a1f763b -[POP3Connection(PrivateCommands) _getStatusFromReply] + 38
10 com.apple.MessageFramework 0x9a1f4ae5 -[POP3Connection authenticateUsingAccount:] + 783
11 com.apple.MessageFramework 0x9a1c7e1a -[Account _connectAndAuthenticate:] + 363
12 com.apple.MessageFramework 0x9a214c8e -[Account authenticatedConnection] + 99
13 com.apple.MessageFramework 0x9a1f81dd -[POP3FetchStore fetchSynchronously] + 579
14 com.apple.MessageFramework 0x9a225a5e -[POPAccount fetchSynchronously] + 211
15 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
16 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
17 com.apple.MessageFramework 0x9a155910 -[MonitoredInvocation invoke] + 128
18 com.apple.MessageFramework 0x9a15f954 -[InvocationQueue _drainQueue] + 517
19 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
20 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 12:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.MessageFramework 0x9a1664ff _handleRequestWithTimeout + 3189
4 com.apple.MessageFramework 0x9a16931e -[_NSSocket readBytes:length:] + 145
5 com.apple.MessageFramework 0x9a168f23 _readBytesFromSocket + 69
6 com.apple.MessageFramework 0x9a168da7 _fillBuffer + 469
7 com.apple.MessageFramework 0x9a168af3 -[Connection readLineIntoData:] + 51
8 com.apple.MessageFramework 0x9a16899e -[IMAPConnection(MFPrivate) _readDataOfLength:] + 125
9 com.apple.MessageFramework 0x9a168566 -[IMAPResponse initWithConnection:] + 126
10 com.apple.MessageFramework 0x9a168483 -[IMAPConnection _copyNextServerResponseForCommand:] + 63
11 com.apple.MessageFramework 0x9a170adf -[IMAPConnection _copyNextTaggedOrContinuationResponseForCommand:] + 240
12 com.apple.MessageFramework 0x9a16f5d0 -[IMAPConnection(MFPrivate) _responseFromSendingCommands:count:] + 213
13 com.apple.MessageFramework 0x9a19051b -[IMAPConnection _doListCommand:withReference:mailboxName:options:] + 462
14 com.apple.MessageFramework 0x9a1902cb -[IMAPConnection separatorChar] + 76
15 com.apple.MessageFramework 0x9a18fe38 -[IMAPAccount _synchronizeAccountWithServer] + 319
16 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
17 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
18 com.apple.MessageFramework 0x9a155910 -[MonitoredInvocation invoke] + 128
19 com.apple.MessageFramework 0x9a15f954 -[InvocationQueue _drainQueue] + 517
20 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
21 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 13:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.MessageFramework 0x9a1664ff _handleRequestWithTimeout + 3189
4 com.apple.MessageFramework 0x9a16931e -[_NSSocket readBytes:length:] + 145
5 com.apple.MessageFramework 0x9a168f23 _readBytesFromSocket + 69
6 com.apple.MessageFramework 0x9a168da7 _fillBuffer + 469
7 com.apple.MessageFramework 0x9a168af3 -[Connection readLineIntoData:] + 51
8 com.apple.MessageFramework 0x9a1f68fe -[POP3Connection(PrivateCommands) copyReplyLineData] + 91
9 com.apple.MessageFramework 0x9a1f56b0 -[POP3Connection idForMessageNumber:] + 109
10 com.apple.MessageFramework 0x9a1f86a4 -[POP3FetchStore fetchSynchronously] + 1802
11 com.apple.MessageFramework 0x9a225a5e -[POPAccount fetchSynchronously] + 211
12 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
13 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
14 com.apple.MessageFramework 0x9a155910 -[MonitoredInvocation invoke] + 128
15 com.apple.MessageFramework 0x9a15f954 -[InvocationQueue _drainQueue] + 517
16 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
17 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 14:
0 libSystem.B.dylib 0x90009857 machmsgtrap + 7
1 com.apple.CoreFoundation 0x9082969a CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
3 com.apple.Foundation 0x92644811 -[NSConnection sendInvocation:] + 2126
4 com.apple.Foundation 0x925fc148 -[NSInvocation invoke] + 174
5 com.apple.syncservices 0x95749607 -[ISyncConcreteManager _performSelectorOnServer:numberOfArguments:] + 961
6 com.apple.syncservices 0x9574a7b8 -[ISyncConcreteManager _performSelectorOnServer:withArg:withArg:] + 62
7 com.apple.syncservices 0x9576d2fe -[ISyncConcreteManager setSyncAlertToolPath:forClient:] + 77
8 com.apple.syncservices 0x9577d739 -[ISyncConcreteClient setSyncAlertToolPath:] + 55
9 com.apple.Mail.Syncer 0x16babb62 0x16ba5000 + 27490
10 com.apple.mail 0x000ef651 0x1000 + 976465
11 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
12 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
13 com.apple.MessageFramework 0x9a155910 -[MonitoredInvocation invoke] + 128
14 com.apple.MessageFramework 0x9a1557a1 +[WorkerThread _execute:] + 80
15 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
16 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 15:
0 libSystem.B.dylib 0x90029a6c wait4 + 12
1 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 16:
0 libSystem.B.dylib 0x90024427 semaphorewait_signaltrap + 7
1 com.apple.MessageFramework 0x9a1455e9 _MFAcquireObjectLock + 402
2 com.apple.MessageFramework 0x9a163711 _lockWithPriority + 48
3 com.apple.MessageFramework 0x9a1636dc -[NSObject(LockingAdditions) lockWithPriority] + 14
4 com.apple.MessageFramework 0x9a16f528 -[IMAPConnection(MFPrivate) _responseFromSendingCommands:count:] + 45
5 com.apple.MessageFramework 0x9a19051b -[IMAPConnection _doListCommand:withReference:mailboxName:options:] + 462
6 com.apple.MessageFramework 0x9a1902cb -[IMAPConnection separatorChar] + 76
7 com.apple.MessageFramework 0x9a1aae60 _sendCommandForMailboxes + 315
8 com.apple.MessageFramework 0x9a2227f3 -[IMAPAccount _fetchUnreadCountsForMailboxUid:recursively:connection:checkForNewMessages:] + 989
9 com.apple.MessageFramework 0x9a222abf -[IMAPAccount _fetchUnreadCountsCheckForNewMessages:] + 448
10 libobjc.A.dylib 0x90a57c56 objc_msgSendv + 54
11 com.apple.Foundation 0x925fc43e -[NSInvocation invoke] + 932
12 com.apple.MessageFramework 0x9a155910 -[MonitoredInvocation invoke] + 128
13 com.apple.MessageFramework 0x9a15f954 -[InvocationQueue _drainQueue] + 517
14 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
15 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 17 Crashed:
0 com.apple.CoreFoundation 0x9087b68b CFReadStreamGetError + 17
1 com.apple.ISSupport 0x9824c03e -[ISS_DAVRequest(Private) _readStreamEvent:] + 1132
2 com.apple.CoreFoundation 0x90876d4e _CFStreamSignalEventSynch + 281
3 com.apple.CoreFoundation 0x90829379 CFRunLoopRunSpecific + 1213
4 com.apple.CoreFoundation 0x90828eb5 CFRunLoopRunInMode + 61
5 com.apple.ISSupport 0x9827997b +[ISS_AYOperation _dispatchNextOperationInQueue] + 872
6 com.apple.ISSupport 0x98279b04 +[ISS_AYOperation _workerThread] + 230
7 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
8 libSystem.B.dylib 0x90023d87 pthreadbody + 84
Thread 17 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x9087b688 ecx: 0xa0a52184 edx: 0x00000001
edi: 0x16d8c510 esi: 0x00000000 ebp: 0xb07bb7c8 esp: 0xb07bb7a0
ss: 0x0000001f efl: 0x00010286 eip: 0x9087b68b cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

TS2587 AirPort Extreme full unable to restart

My time capsule has only 400kB of 500Gb left and I can't get it to restart. Is the problem it is so close to capacity. If yes how can I delete files while starting up or is it just failing and not a capacity problem?

If you are saying that the power light indicator on the Time Capsule is out and the device will not power up, this would have no relation to the amount of data that might be on the drive.
Can you clarify what you mean by "restart"?

Airport Extreme Causing Kernel Panics - Looking for Options

I have an iBook G4/1.42 gHz/512MB (mid-2005) that is now out of warranty. All of a sudden, it starts throwing kernel panics. I read through the panic log and the log has references to the built-in Airport card. Keep in mind this is the model with the Airport card that is not easy to remove.
I turned off the Airport card and the KP's have stopped. At this point, I'm looking for suggestions. Am I better off trying to replace the Airport card or is there an external device that will suffice at lower cost. Thanks for your input.

I'm in the same boat ... the kernel panics made me think I was using a windows machine. I should have known something was starting to go wrong when the internal fan was turning on more and more -- it must have been trying to cool the airport card off!
Right now, I have airport and bluetooth turned off and I haven't seen panic since and the fan has stayed off. I'm using a firewall connection and internet sharing to my work laptop so my wife can use her email (a very temporary solution).
The www.ifixit.com site has 'cards' for $70 and claim the installation is "difficult" -- they don't even offer installation instructions.
For now, I think I'll run a wire from the airport to the where the iBook normally resides. And maybe when I concede that my iBook won't get fixed by itself, I order one of the external USB 802.11b/g dongles.

Frequent restart of AIRPORT EXTREME necessary for USB printing

My AIRPORT EXTREME needs to be restarted about once every week through the AIRPORT UTILITY software in order to get the connected USB printer (Brother HL-1450) working.
The AIRPORT is powered 24h a day and connects to the internet flawlessly but the printer dissappears from the "bonjour" printer list frequently.
Anyone having an idea?
(latest AIRPORT software V5.7 installed)
powerbook Mac OS X (10.4.7)

Hello jlford30. Welcome to the Apple Discussions!
You may already have everything set up properly...
Unfortunately, not all USB printers are compatible with AirPort base stations.
Take a look at one of these iFelix Unofficial AirPort Printer Compatibility links, depending on which AirPort base station you have:
- 802.11g AirPort Extreme Base Station (AEBS)
- 802.11n AirPort Extreme Base Station (AEBSn)
If your printer isn't listed, it doesn't necessarily mean it won't work, but simply that it has not been verified. iFelix also provides the following workaround for printers not on the list that would certainly be worth a try.
Also, you may find the following Apple article helpful.

I just purchased a new airport extreme 802.11ac I set it up and runs fine when i put my mac to sleep i come back and it can not find my airport i have to restart

I PURCHASED THE NEW AIRPORT EXTREME 802.11AC I SET IT UP AFTER I PUT MY MAC TO SLEEP I COME BACK AND IT SAYS CAN NOT FIND AIRPORT EXTREME I HAVE TO RESTART AND IT FINDS IT.

Try the following, in order, until (hopefully) resolved:
1a. Delete Preferred Network(s)
System Preferences > Network > Wi-Fi > Advanced > Wi-Fi tab
Under "Preferred Networks," delete the network(s) you regularly use from the list.
1b. Delete AirPort Keychain Entries
Launch the "Keychain Access" application located in Applications/Utilties.
In the windows on the left side: Select login for Keychains and "All Items" for Category.
Click on the "Kind" filter at the top, and look for any "AirPort network password" entries...and delete them.
1c. Add Preferred Network(s)
System Preferences > Network > Wi-Fi > Advanced > Wi-Fi tab
Add the preferred network(s) using the "+" button.
Restart or log out then back in.
2. Move System Configuration Files
(Note: You will have to reestablish your network connections settings.)
Go to /Library/Preferences
Move the SystemConfiguration folder to the desktop.
Restart your Mac. (Note: OS X will rebuild the files that are now sitting on your desktop. If this doesn't resolve the issue, you can move the folder back to it's original location.)

USB and AirPort Extreme

Does anybody know if taking out a USB hard drive from a Airport Extreme causes any problems. I have taken a USB stick out and didn't know if I was hurting the Stick because I didn't eject it.
Thanks

It can.
Basically, depending on the file system in use and what's going on, you may have inadvertently removed the drive when it was in the middle of a write, possibly corrupting a file or the file system on the drive.
Further, if it's a USB-powered drive, it could also cause physical damage to the disk itself when it suddenly loses power.
If you're worried about it, run Disk Utility on the drive to check for any damage, and then don't do it again.

I keep getting write errors (-50) when I try to create new files or folders on my Gen 5 Airport Extreme USB disk.

Write errors (-50) when I try to create new files or folders on my Airport Extreme USB disk. Restarting the Airport Extreme seems to solve the issue. Any idea why this occurring? It doesn't seem to be OS specific, meaning I can't write to the drive from a Windows PC or a MacBook Pro.

Although, I would consider it rare, it is quite possible that this drive is just not 100% compatible with the AirPorts. Typically, in these cases, the AirPort will not even recognize the drive at all ... or it will, but not allow you to access it. I actually haven't come across a case where you can read but not write to a drive consistently or vice versa ... except from Windows-based computers. Sorry!

AirPort Extreme Causes WinXP to Restart

Similar Messages

Maybe you are looking for