clock reset

I've had a similar problem happen twice. Computer goes to sleep unexpectedly, i have to hold the power button down to shut it off and then the clock is reset and i have to re-enter the wi-fi password when I turn it back on. This is while plugged into an outlet.

One thing I noticed is that the light on my charger did not light up rightaway after this happened, maybe until the date righted itself?

Same here. Battery of late 2010 MBP Intel was drained. MBP shut itself down, and after boot and login, date was set to Jan 1, 2008, wifi password lost, and similar firewall warnings for system processes. Oh, and the desktop background image was reset to the default purple sky and stars.

Seems this issue is taking a long time to get resolved. First post was from april 2009, almost 2 two-and-a-half years ago.

Same thing as well this morning: the symptoms described on page 5 of this thread. Taking the hint from other posts, I manually set the clock date to yesterday (so I could see if it autoupdated to the correct day), set it back to autoupdate, then rebooted a couple times. (Additionally I cleared out most of the firewall exemptions.) It now has the correct time and I'm no longer getting warnings and firewall requests. I'm not sure if sleep mode failed to kick in last time I closed the MacBook (wouldn't be the first time), or if it's one of those mystery shut downs described in other posts. P.S. I was glad I keep the wifi password in a file....

It's hard to believe that this thread is two years in the making and NO SOLUTION??? I have a PowerBook g4 that , every time I unplug it (if I don't turn the screen off by setting brightness to zero), it will die almost immediately. Upon starting up again, clock is reset to before March 24th 2001 (which ends up being December 31,1969). Recent upgrade of OS from tiger to leopard yields no solution. Internal battery is tested and working. Reset of PRAM did not help.

C'mon, Apple... HELP US!

Add another one to the list. Late 2008 model Macbook 13 inch unibody, about two 1/2 years old. My battery has been getting bad lately. The only things I did different were about three weeks ago I bought aftermarket memory (went from 2 g to 4 gigs, but it was functioning fine, if not a lot faster for the last few weeks); the other thing I did different was re-calibrate the battery. Other than that I'm not sure. Just did a reset and let the clock auto-correct and nothing else has happened.

We'll see, my guess is bad PRAM batter?

Same thing is happening to me on my MacBook Pro. Clock resets to Jan 1, 2000. Then, I get the following seven error messages when I boot up:

• Your computer's clock is set to a date before Jan 1, 2008. This may cause some applications to behave erratically.
• Do you want the application "rpc.statd" to accept incoming network connections?
• Do you want the application "rpc.lockd" to accept incoming network connections?
• Do you want the application "portmap" to accept incoming network connections?
• Do you want the application "nfsd" to accept incoming network connections?
• Do you want the application "mDNSResponder" to accept incoming network connections?
• Do you want the application "configd" to accept incoming network connections?

After I fix the date and time, and click "Allow" for all of these processes, the problem seems to go away. But it's been going on for a few days now. Not comforting.

POSSIBLE SOLUTION:

This exact problem happened to me then the campus IT guys fixed it.

I run snow leopard so I dont know how this should be done otherwise.

system preferences>network

There should be some icon on the left that says wifi or airport. Delete this profile and reboot. The computer will create another one when it boots completely.

Before I completed these steps I allowed all the incoming server messages, and set the clock manually. Im not sure if this part is necessary but regardless I did it.

So this fixed it for me hope it helps a few out. If it does let everyone know please.

Your situation is most likely a dead battery. No matter the software upgrades it's still going to be a dead battery. I would either take it in to get looked at or order a replacement.

You can add me as well. 2009 MacBook Pro, 17". My MacBook Pro began freezing a week or two ago, not sure if this is connected, but it will freeze upon opening, while using it, and just plain randomly. Then this morning I turned on my Pro and I got the same messages many have gotten. The clock reset itself to December 31, 2000. I had no internet connection, etc.

I've reset my clock and had to reset my password for Apple. I turn my computer off every night, and always have. I never run off the battery, just use it plugged in. Yet this morning for the first time ever, my battery shows it's at 22%! NEVER, NEVER has this happened. Because I don't run this computer off the battery, it's always been at 98% to 99%. So I'm assuming last night, while the computer was OFF and unplugged it was using the battery, how and why? This makes no sense at all.

Please somebody answer our questions.

I fixed it by getting a new power cable. I was under apple care so it was super easy. It appears there might be multiple causes though.

Jonahhh: Did Apple suggest this? Why would these problems be caused by a defunct power cable, did they say? Thanks!

I am having this problem as well. Booted up my Mac Pro 15 inch 2008 and all my airport networks has been forgotten and clock has been resetted to jan 2001. My laptop then freezes from time to time. Help.

Same thing happened to me too.. I hope the Apple Community gives a good response to this..

Same thing happened to me - OS X 10.6 mac mini. Clock says 2000, wifi constantly requires pw. iCal is sending old reminders.

I ran permissions, iVirus then restart. No clock problems, but airport is still asking me to put in pw.

How long has this thread been active and no reply from Apple. Years? They should be ashamed.

Same thing is happening to me on my MacBook Pro. Clock resets to Jan 1, 2000. Then, I get the following seven error messages when I boot up:

• Your computer's clock is set to a date before Jan 1, 2008. This may cause some applications to behave erratically.
• Do you want the application "rpc.statd" to accept incoming network connections?
• Do you want the application "rpc.lockd" to accept incoming network connections?
• Do you want the application "portmap" to accept incoming network connections?
• Do you want the application "nfsd" to accept incoming network connections?
• Do you want the application "mDNSResponder" to accept incoming network connections?
• Do you want the application "configd" to accept incoming network connections?

This is exactly what happened to me this morning. It's not a battery issues for me (I'm on an iMac), just the reset clock and the alerts asking "Do you want the application "rpc.statd" to accept incoming network connections?" (etc.).

Those questions scared the excrement out of me, and I clicked no for all of them. Date and time went back to normal without me having to do anything other than simply open Date & Time in system preferences. Had to re-enter password for wifi, though.

Should I be worried about the requests to accept incoming network connections? Is it fine to click yes? More importantly, should I avoid doing online banking?