Time Machine turns itself on after my Mac Pro wakes from sleep (every time)

Hi,
I have a 2009 Mac Pro and it currently has Lion on it (10.7.4), but the problem I am about to explain started when the machine was running Snow Leopard, so it doesn't appear to be an OS-specific issue.
I do not currently use Time Machine, I use Carbon Copy Cloner and some online backup solutions to handle backups. I did use Time Machine for a short time on this machine just after it was introduced, but I didn't end up using it for long and the external drive I used for the backups is no longer in service.
The problem is this:
I have Time Machine off and I have all of my drives (I have 4 drives in my Mac and an external drive) set not to be backed up for good measure. Time Machine will stay off like it should except in one instance. If I put my machine to sleep, when my Mac wakes, Time Machine is instantly turned on and I get a warning telling me no backup drive has been selected and that I should pick one. I go into the Time Machine preferences and turn it off. It will remain off (I've checked the preferences to be sure) until the next time the machine is put to sleep. Time Machine will remain off, even through reboots. It is only waking from sleep that causes this.
I've tried zapping the PRAM, getting rid of the Time Machine preferences and even logging into a new, unused user account and testing it from there and the problem continues. This is really starting to annoy me. I wouldn't mind having TM on, but having to click through the warning every time my Mac wakes from sleep is frustrating.
I don't want to have to buy a new external hard drive and let TM backup to the drive because, as I said, I've got my backup solutions handled already and I'm not willing to put yet more money to use a feature I don't need right now.
I've done searches online and asked around and no one has been able to help me yet. So I thought I'd try here.
Anyone have any ideas?

Do you see a wake reason in Applications>Utilities>Console?

Similar Messages

Late 2013 Mac Pro wake from sleep crashes - which logs to look at?

I started encountering wake-from-sleep crashes with my late 2013 Mac Pro a couple of weeks ago. Prior to that the system had been pretty solid. Other than app and OS updates installed from the App Store, I can't think of any software changes that might be responsible.
What logs should I be looking for that could be helpful in diagnosing the problem? Looking at other posts where people have been trying to diagnose similar issues I see people posting portions of panic logs that show which modules were loaded and might help point to a culprit, but I can't seem to find a log with a panic message in it.
I had thought I'd determined my Anker USB3 powered-hub was related to the crashes, as when I disconnected it from my system I went several days without a crash. Today I reconnected the hub with just a few devices on it and got a crash. I disconnected the devices but left the hub attached but got another crash. I then disconnected the hub again, assuming I'd proved it was the culprit, but the machine has now crashed twice without the hub attached.
I'm running OS 10.9.4. Looking at other reports people reported some specific programs that added kernel extensions that were suspected to be the problem, but I don't have any of those programs installed on my Mac. The problem doesn't happen every time I wake the machine, but has happened at least four times today alone (after about three days of no crashes.)

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report.
I know the report is long, maybe several hundred lines. Please post all of it anyway.

2006 Mac Pro - wakes from sleep after 3-5 seconds

Folks, I have a 2006 Mac Pro (2.66 x 2-core) that refuses to stay asleep. The system.log shows this:
Dec 17 12:40:40 Mac-Pro-Wired-1 kernel[0]: System Sleep
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: Wake reason = UHC2
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: System Wake
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: USB (UHCI):Port 2 on bus 0x3d has remote wakeup from some device
OK, so it's a USB device that's keeping the computer from sleeping. According to System Profiler, here is what is on bus 0x3d - Apple wired keyboard (the white one) and a Logitech MX518 gaming mouse is plugged into the USB port on the keyboard.
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2689
PCI Revision ID: 0x0009
PCI Vendor ID: 0x8086
Bus Number: 0x3d
Hub in Apple Pro Keyboard:
Product ID: 0x1003
Vendor ID: 0x05ac (Apple Inc.)
Version: 4.10
Speed: Up to 12 Mb/sec
Manufacturer: Mitsumi Electric
Location ID: 0x3d200000
Current Available (mA): 500
Current Required (mA): 50
USB-PS/2 Optical Mouse:
Product ID: 0xc01e
Vendor ID: 0x046d (Logitech Inc.)
Version: 22.00
Speed: Up to 1.5 Mb/sec
Manufacturer: Logitech
Location ID: 0x3d210000
Current Available (mA): 100
Current Required (mA): 98
Apple Pro Keyboard:
Product ID: 0x020b
Vendor ID: 0x05ac (Apple Inc.)
Version: 4.10
Speed: Up to 12 Mb/sec
Manufacturer: Mitsumi Electric
Location ID: 0x3d230000
Current Available (mA): 250
Current Required (mA): 50
Is the keyboard on port 2, or is it the mouse?
If I unplug the mouse and use the keyboard to place the computer into sleep mode (Option + Command + Eject), the same thing happens. It appears the wake is coming from the keyboard or the keyboard's built-in hub.
I have:
- installed update 10.5.6 using the downloaded combo update.
- reset the SMC (a few times)
- reset PRAM
- repair permissions
and no dice!
I could sure use some help figuring this out.
Thanks...

The sleep feature hardly works on Macs if at all. I had that same issue while on Tiger. Same thing. Mine was a PCI card that would awake it after a period of time. I have had issues with it NOT going to sleep also due to a PCI card and USB hub. I even disconnected everything and had gone back to stock and that still did not resolve it without having to reset the power management controller in Terminal. That was how I got it to work again on my old PPC machine.
One test to try is to disconnect all the USB gear including the hub and let the machine go into sleep on it's own. If it wakes up- it's not related to USB but probably an internal timer that is out of whack or a PCI based issue.
I had so many issues way back in 2004 that I finally gave up and just set it to never sleep. I have never had any issues after that! LOL
So, getting back to the timer deal. There are times when the internal timer in the power management portion of OS X and it can actually flip to a wake command. Best thing to do in your case is to go in and trash the plist file for power management and restart. That should help in that case. If it doesn't make a bit of difference and the issues persist, then there's something other than that going on.

My Mac Pro doesn't chime every time at startup

I've heard this is not a good sign, but the kid on the phone at Apple says he can connect it to no known problem. My computer chimes at startup after a PRAM reset and never again after that. Does anyone feel comfortable or uncomfortable with this acceptance?

Uh-oh. I returned from a trip to find my Mac did not chime on powering up the other day. Just now it didn't wake from sleep after dinner. It finally restarted after I held the power button for a while, but again no chime, although I do have the white apple/grey screen that you're talking about.
It's not looking good.
Verify Disk found no issues. I was kind of hoping it was from the recent update with the Mac App Store, somethign that would be fixed with the next update.
Looks like it could be a hardware issue even though this thing is just 21 months old.

Power Mac G4 Wake from Sleep Crash

I have been having wake from sleep issues since I installed Mac OS 10.5 on my Power Mac G4 three months ago. Technically, this machine is supported by Leopard: it's an 867 MHz G4 with 512 MB of RAM. And indeed, the Leopard installer allowed me to install fine, and while it runs slower than I'd like, it seems to run all the applications just fine. The major problem is that it does not properly wake from sleep. Nearly every time the machine wakes up from sleep, it crashes and needs to be rebooted. It may be a display issue -- the screen frequently looks corrupted when it has crashed -- but the console logs have not given me any clues. It does seem to be related to the amount of time that the machine has spent sleeping, but I have had it crash after a sleep of as little as a few minutes. I have a USB 2.0 PCI card installed, but removing that for a week didn't have any noticeable effect on the problem. I'm stumped, and preparing to downgrade to 10.4, as the machine takes too long to boot for me to live with the option of shutting down and starting up every time I use it.
I've been very happy with this machine for years and years and frankly I've never had this much of an issue with the Mac OS on an allegedly "supported" machine. As a last resort, I thought I'd ask here whether anyone has another idea that I can try.

I'm having a similar problem, though with my Powerbook G4, since installing Leopard. It's a 1.5 Mhz model. Everything seems to work properly, but it takes 10 to 12 seconds to wake from sleep. When it is woken, it shows the old screen image and remains frozen for over 10 seconds, before displaying the updated screen and coming back to life. It seems to me that this pause is progressively getting longer. It was only a few seconds to start with, but is now over 10 seconds.
Any clues?

Time Machine turns itself on?

I never turned it on, never configured it or designated a volume to back up to. Earlier toady, I took a look and it showed it was off, but later, it showed to be on. I turned it off and clicked the padlock icon.
I'm guessing it's been running every day and that's why every two days I have a full startup disk.
Anyone else have this problem?

DMorgan wrote:
I never turned it on, never configured it or designated a volume to back up to. Earlier toady, I took a look and it showed it was off, but later, it showed to be on. I turned it off and clicked the padlock icon.
I'm guessing it's been running every day and that's why every two days I have a full startup disk.
Anyone else have this problem?
That's not been reported, that I can recall.
What might have happened is, you connected a drive, OSX asked if you'd like to back up to it, and you accidentally said yes. Then you ejected the disk. Apparently if this is done in just the right way, at just the right instant, TM doesn't realize the disk is gone, but backs up to a "phantom" disk in your /Volumes folder. That's the only way I know of that it would put backups on your startup disk.
From a Finder window's menubar, select +Go > Go to Folder+ and type /Volumes in the prompt. The resulting list should have an alias for every disk/partition on your system. If anything listed there is not an alias, that's probably where the "phantom" backups are. If there's a folder containing a Backups.backupdb folder, that's it. Delete it (it will take a long time to empty the trash).
Are you on Leopard or Snow Leopard? Your profile says Tiger (please update it).
If you're on Snow Leopard, there is a way to stop OSX from asking if you want to use disks for Time Machine. Click here to download the +Tinker Tool+ app. Click the +Snow Leopard+ icon in the toolbar.

Get Back to my Mac to Wake from Sleep

Hello. I am having trouble accessing my home iMac over the internet when it is in sleep mode. I am running Mountain Lion with an Airport Extreme. I have Back to My Mac enabled. I have no problem accessing the computer over the internet when the computer is awake. My Airport Extreme is running in Bridge mode. The AE is connected to a Verizon Wireless Router/Modem via an Ethernet cable. I read somewhere to enable the NAT mode on my Airport Extreme, but this gives me a double NAT error message. I also have several Ethernet cables connected to my Verizon Router that I currently use. I do not use the Verizon wireless feature and would be happy to have it disabled.
I think that the problem may be related to the Verizon router. Any help would be appreciated!
Thanks!

network wrote:
I think that the problem may be related to the Verizon router.
That is likely. Although the Bonjour Sleep Proxy is open source, I do not know of any routers other than Apple's that support it. The router must send a "magic packet" over wireless to wake a sleeping Mac.
Double NAT will also be a problem. BTMM is likely to spontaneously start working for you, if you can find a way to disable the Verizon's router function, using it strictly as a modem, and configure the Extreme as your router instead.
Populate the Back to My Mac fields in AirPort Utility > Base Station with your Apple ID(s). This may or may not be optional; my tests have not yet reached a conclusion.
Make sure you can get it to wake while you're at home, if it does, then proceed with troubleshooting it while away from home.
Leave the iMac's Ethernet port disconnected for now. Over several months of testing I concluded that a sleeping iMac cannot be woken up over the Internet if Ethernet is connected at all, even though it may not be first in the service order. It will wake on Gigabit Ethernet when the "wake" request originates from within the LAN (local Bonjour). This is the same whether I use a Time Capsule or an Extreme.

Intel Mac Mini wakes from sleep (for no reason) after installing leopard

My mac mini keeps waking after its been put to sleep (both by selecting sleep by hitting the power button or using the apple menu item.
This only happens now I've upgraded to leopard; with tiger, all was fine.
Any ideas what's going on? The iChat logging in noise blasting through my speakers at 1am last night gave me a bit of a fright!

This may be something like a driver, application or external device which is not fully Leopard compatible, or even a component of MacOS if you upgraded to Leopard rather than did a clean install. To start the process of troubleshooting, first download and install the full 10.5.1 update from http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1051update.html , even if you have already updated to 10.5.1 using software update. The full updater has been reported to resolve a number of minor issues.
Next, assuming that doesn't resolve it, start up your mini, put it to sleep and then disconnect everything. If it continues to wake unpredictably, the issue is with the mini itself, and you may be best to backup all your data and do an erase and install to resolve any residual issues caused in the upgrade. If, on the other hand, the system remains sleeping, it points to an external device being the culprit, in which case plug each one in, one at a time until you can create the unpredictable waking again. Whichever component was last plugged in, is the primary suspect!

IMac wakes from sleep every night at 8:00 PM but no wake time set.

My iMac (new fall, 2007) running 10.5.2 wakes every night at 8:00 PM Eastern day savings time. Before day light saving time started it woke at 7:00 PM. In the energy control panel "schedule section" the "start up or wake option" in NOT checked.
The exact same problem occurs in a mini Mac purchased last fall which is also running 10.5.
I applied the new firmware update to the iMac last week hoping it would correct this problem but it did not.
Does anyone have any idea how to stop these computers from waking at 8:00 PM every night.

Setting the wake time to 8:00 PM did stop the computer from waking up every night at 0:00 GMT.
See this discussion: http://discussions.apple.com/thread.jspa?messageID=7075146&#7075146
I view this as a work-around and not a fix. The Apple technical support representative, that I talked to, knew nothing about this problem.

Laptop wakes from sleep multiple times throughout day

My laptop has been doing this for the past couple of weeks. When I put it to sleep, it will wake up after a couple of hours stay on for a few minutes and return back to sleep. It repeats this process again and again. In the event logs, the wake source is unkonow. There are no wake timers activated, and no devices are allowed to wake the computer. After spending many hours working on this and reading almost everything possible online, I am stuck. How should I proceed?

Is the computer near a television, DVD player or audio video receiver? Microwave oven? Keep investigating. Interference is hard to pin down.
Download Air Radar. You can use it free for a few weeks. Use the application to display all of the visible networks in your area. It's also possible that there are "hidden" networks in your area. Can't do much about that or the new security system that one of the neighbors installed.
You will see your network and others in the display. Look for the channel that your wireless is on and compare it to the other channels in use. If your network is on the same channel or a close adjacent channel to another network, this can be a source of interference. Post back if you need instructions on how to change your channel. Ideally, you want to be as far away from other channels as possible. If there are "hidden" networks around you, all you can do is try a few different settings to see if that helps.
If you have a desktop or the computer usually stays in the same place, there is nothing better than an ethernet connection. If you can't run the wires to the router, then take a look at a pair of ethernet powerline adapters that use the wiring in your home to transmit an ethernet signal. This will be a faster and more reliable connection than wireless.
Please post back on your findings.

Black screen after MacBook Pro wakes from sleep; reason, solution?

Greetings!
I have 2 MacBook Pro machines; both are running the latest versions of OSX for their age.
The 2 GHz Core Duo is using 10.6.8 (2GB RAM) and 2.5 GHz Duo Core 2 is using the 10.7.x (4GB RAM).
Both are routinely used with external monitors. Every so often when either of the machines are put to sleep, the external monitor disconnected, and finally when the machine is woken, the native screen remains black and unlit. If the machine is connected to the external monitor, it shows its appropriate desktop but the finder bar is unavaible so nothing can be done short of forced shut down and a reboot.
Am I forgetting some simple short cuts (key-bases) to bring the native screen to life or is forced shut-down really necessary?

"..but that thread is marked as "Answered" with a "solved answer" available, when *clearly it is not."*
It was for the original poster of that thread you linked.
+"the bug no longer happen in snow leopard."+
"I've opened this new thread to re-examine the issue in hopes of a true solution. (Is there some other thing I should do to report the bug to Apple?)"
File a bug report and/or post your concerns over in Product Feedback.
If you have AppleCare, have you contacted them?

Probelm With EArly 2008 8-core Mac Pro on Wake From Sleep

Well, after more than a year of being a flawless machine, I am now starting to have trouble with my 8-core 2.8 GHz Mac Pro purchased in January of 2008. A few days ago I noticed that when I woke the Mac Pro from sleep, the desktop came up momentarily, and then the screen went went black after a second or less. The power light on the front of the Mac Pro was still burning brightly, but I could not do anything but do a power button forced reboot. I did so, and the machine booted up to a blue screen, but would proceed no further. I then did a second power button forced reboot. The Mac Pro then booted up perfectly this time and all was well.
However, I have noticed since then that often when I wake the Mac Pro up from sleep, the desktop comes up and everything looks normal, but I have absolutely no ability to do anything. I can move the cursor on the screen but clicking the mouse on anything (menu items, icons, etc.) does nothing. I cannot do anything but a forced reboot to regain control of the machine.
I have booted from my drive that has the clone of the OS perfectly with no problems. I have used disk utility to check the Mac's main boot drive and all checks out fine. I have repaired permissions. I have reset the SMC, but nothing has helped. This morning when I went to wake up the Mac Pro, the desktop came up, but absolutely nothing was operative. Mouse cursor moved on the screen, but I could not get any menu item or icon to respond when I clicked on it. I did a power button reboot and the machine is working again, but every time I do one of these power button reboots Time Machine takes 15-20 minutes to prepare and do its backup. Clearly something is wrong, but short of never putting my Mac Pro to sleep again I am out of ideas as to what to do next.
For over a year I have been using a Logitech wireless keyboard and mouse, but I don't know if this is involved in the wake from sleep problem or not. I should add that this keyboard/mouse combination has never previously given any trouble at all.
I would greatly appreciate any suggestions that anyone may have.
Tom

Glad to hear you were already using SuperDuper and (use to) use Disk Warrior.
Can't be rushed. Take a look at how long it takes Micromat and SoftRAID to update their products to get a ballpark idea of time and work to have compatible versions. Or do like others, wait for "SP1" or a year, wait for Adobe and others to be ready before fully supporting.
The best time to upgrade to (Jaguar, Panther, Tiger, and now Leopard) is a year out, even when the product is at its end release-point, not when it is just 1.0.
Minor but things First Aid misses, and can mean all the difference in the world. Major is bad enough that after recovering files you need, you should reformat and restore due to keys out of order, overlapped extents, corrupt journal (there is a tip about turning journaling off and back on to fix some problems).
I would wait for Disk Warrior (4.1.1) before upgrading to Leopard, rather than the other way around.
Alsoft can't work on an update until they have in their hands a stable and released version. And Disk Utility does and has changed during the last 18 months.
Apple is in the habit and you will find that developers are left in the dark during the last stage. Then 10.5.0 had too many bugs and problems. 10.5.2 was stable-ish, and changed the "rules of the game." 10.5.6 has had a few wrinkles of its own.
Apple warns to NOT use older versions of its own Leopard Disk Utility with the latest (10.5.6) when it comes to repairing permissions (see MacFixit).

Bluetooth Unresponsive After Wake from Sleep

I have an issue where when my macbook pro wakes from sleep, the bluetooth mouse will not connect, and BT becomes unresponsive. Sometimes I can turn bluetooth off then back on and be OK, BUT 95% of the time, I have to restart the computer to get bluetooth back.
After waking, the BT appears to be on, I get the popup on the screen which tells me "connection lost" with a picture of a mouse. I can open BT preferences and turn BT off, but nothing happens. I can even recheck "on" but it is completely unresponsive.
Things tried:
Allow BT to wake this computer is UNCHECKED
in activity monitor I have forced quit BLUED, but BT does not come back.
I have trashed the BT preference file Mac HD/library/preferences/com.apple.bluetooth.plist
I have reset SMC and PRAM
Tried a Logitech V470 and mighty mouse
Fresh install of 10.6.0, then upgraded to 10.6.1, then 10.6.2 (using combo)
Tried disabling steermouse, fresh batteries, holding my mouth right...
When the BT is not responding, the BT name either changes to 2.2.4f3 (which is the Apple BT software version), or it says "name not available".
Also in system profiler, when BT is not responding the BT "Hardware settings" section is missing. It starts with "services".
This is driving me crazy. Could this be hardware related? I feel it is more software, since on restart, the BT mice pair perfectly and work great. The never randomly disconnect.
This issue only happens when the computer resumes/wakes from sleep.
Everyone please provide feedback. I am the only one with this issue? I have scoured the net, and find very little regarding this exact issue. I am within my 90 days from buying, should I call Applecare or is it a waste of my time?
Thanks for your help,
Jeff
Spec's:
mid-2009 aluminum uni-body, Intel 2.66Ghz, 4GB Ram, 320GB HD
Snow Leopard 10.6.2 (Clean install to 10.6, then upgraded)
Login items: Steermouse, PleaseSleep, and Windows Live Sync
Also running at startup, but not in Login items: Paragon NTFS, Flip4Mac,
MacFuse, LogMeIn

I've got what sounds like the same problem with my new unibody MacBook Pro.
I've had the problem with both 10.6.1 and 10.6.2.
I also find that a reboot fixes things. In my case, I can sleep/wake multiple times with
no problem, but once the BT goes unresponsive upon wake, every subsequent sleep/wake
will suffer the problem until I next reboot.
I also discovered that in my case I can re-pair the non-responsive devices (two flavors
of Logitech mice and an Apple wireless keyboard) while in sick-BT mode and they will
work until I next sleep/wake, whereupon they will again fail to connect and my
choice is either to re-pair yet again, or reboot and have the problem go away, at least
for awhile.
I'm trying to correlate my activity with my BT going out to lunch, but have yet to narrow
it down definitively. I have one or two data points that make me suspect it goes south
after I use VMware Fusion (Version 2), but I cannot yet rule that one completely in or out.
/Kevin

Mail unresponsive after wake from sleep.

When my Retina Macbook Pro wakes from sleep, when i go to mail, it will often become unresponsive for a period of a few minutes - if i go and use safari/ other apps, it will normally resume normal use in its own time, alternatively, i must force quit and reopen to gain use of mail again.
I cant think of any configuration changes which caused this problem to begin, not after any particular software update of anything, am running the most up-to-date version of Mountain Lion - is anyone else seeing this problem and have a solution?

my problem on mail, is that sometimes when i quit it (cmd + Q) it will not quit. although the mail window is gone, but the app is still running in background. and i have to force close it only i can re-open it. and if i didn't force close it, i can't turn off my mac. using MBPr as well in Mountain Lion. really hoping for a solution to this problem.

No IPv6 after wake from sleep

Hello,
     When my MB pro wakes from sleep there is no IPv6 connectivity. In order to restore IPv6 I need to stop/start the Thunderbolt Ethernet adapter (make service inactive/make service active) or reboot.
     Details on my configuration:
     OS X 10.9.2
     Thunderbolt Ethernet Adapter used for network connectivity (Wi-Fi OFF)
     Native IPv6 network (not tunneled)
     IPv6 and v4 manual config (no DHCP or SLAAC)
     Dual stack TCP/IP configuration
     IPv4 works
     IPv6 works until MB goes into sleep mode
ifconfig
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
          options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
          ether a8:20:xx:xx:xx:xx
          inet6 fe80::aa20:xxxx:xxxx:xxxx%en2 prefixlen 64 scopeid 0x4
          inet6 2001:xxxx:xxxx:1::2 prefixlen 64
          inet 8.x.x.2 netmask 0xffffffc0 broadcast 8.x.x.63
          nd6 options=1<PERFORMNUD>
          media: autoselect (100baseTX <full-duplex,flow-control>)
          status: active
^---- Looks good (to me).
netstat -nr -f inet6
Internet6:
Destination                             Gateway                         Flags         Netif Expire
default                                 2001:xxxx:xxxx:1::1             UGc             en2
::1                                     ::1                             UHL             lo0
2001:xxxx:xxxx:1::2                     a8:20:xx:xx:xx                  UHL             lo0
fe80::%lo0/64                           fe80::1%lo0                     UcI             lo0
^--- This looks good too (to me).
Ping my Thunderbolt Ethernet Adapter
PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::2
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=0 hlim=64 time=0.129 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=1 hlim=64 time=0.233 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=2 hlim=64 time=0.225 ms
16 bytes from 2001:xxxx:xxxx:1::2, icmp_seq=3 hlim=64 time=0.227 ms
^--- Yay!
Ping the default route
PING6(56=40+8+8 bytes) 2001:xxxx:xxxx:1::2 --> 2001:xxxx:xxxx:1::1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
ping6: sendmsg: No route to host
ping6: wrote 2001:xxxx:xxxx:1::1 16 chars, ret=-1
^--- Boo
This causes problems for IPv4 as well because apps like Firefox and Safari try using the IPv6 DNS servers and give up before falling back to the IPv4 servers. So this problem breaks more than IPv6.
Is this a bug or do I have something misconfigured?
Thanks.
                               --Tom

I see this (sort of) behaviour as well. When I look into the tcp/ip tab of the network (system prefs) I see
fe80::1:1 as router, that is why v6 stops working. After turning v6 off and on again the correct router IP appears.
NB. this is on wifi
Rudi

Time Machine turns itself on after my Mac Pro wakes from sleep (every time)

Similar Messages

Maybe you are looking for