Computer Name changes when waking from sleep

Hi,


I'm running OS X Lion Server on a Mac Mini 2ghz Core 2 Duo and every time it wakes from sleep I get a message saying "There is already a computer on the network named MacServer, renaming to MacServer (2)".


It only happens when waking from sleep. If I reboot or use the mini for hours without sleeping it's fine, but once it's gone to sleep it renames on wake. When it sleeps overnight it's named MacServer (5) by the morning, as it wakes up every two hours or so to re-register itself on the network and each time it renames itself.


I don't have any other compters on the network with the same name. The only other computer is a MBP and has a completly different name.


Here's my setup;


  • My Mac Mini is wired via ethernet to a Time Capsule. AirPort is turned off (I've tried on and off).
  • My Mac Mini has a static IP address (x.x.x.40) with DHCP for everything else (DNS, etc.)
  • The Time Capsule is wired to an ADSL router via ethernet.
  • The ADSL router manages DHCP and NAT, with IP pool x.x.x.2 through x.x.x.30.
  • DHCP and NAT are turned off on the Time Capsule (bridged mode).
  • Wireless is turned off on the ADSL router.
  • Time Capsule is handling wireless.


I've tried resetting the ADSL router. I've tried resetting the Time Capsule (to factory defaults).


The problem seems to be with mDNSResponder, as the log seems to suggest that it is this daemon that thinks there's a duplicate computer name. I've even looked at the source code for mDNSResponder and the last mod-log entry suggests that a fix was put in for this issue in 2009. It doesn't look like it's fixed it, though.


I've tried doing a fresh install of OS Server several times now and, after the last install, it started happening before I got a chance to restore from a Time Machine backup. i.e. on a completly fresh install and assigning a completely new computer name.


Can anyone help me on this issue? It's driving me insane!

Mac mini, Mac OS X (10.7.3), 2ghz Core 2 Duo, 8Gb Ram, 500Gb HDD

Posted on Apr 11, 2012 8:56 AM

Reply
34 replies

Jul 2, 2012 4:29 AM in response to SwampFoetus

Does everyone who's experiencing this problem have either a TimeCapsule or AirPort Extreme on firmware version 7.6.1? If so, have you tried downgrading to 7.6.0 as this is what's working for me. I'm awaiting Apple fixing the issue in the next firmware.


The current version of AirPort Utility on the Mac doesn't let you downgrade, put the iOS version lets you do it. I think you can also download an older version of AirPort Utility on the Mac to do it.


I'm 99% certain it's Bonjour Sleep Proxy from the mDNSresponder messages in the syslog.

Jul 8, 2012 7:33 AM in response to SwampFoetus

I run an AirPort network with one 4thG Extreme, a 1stG Extreme, and two older Expresses (for music).


Things worked fine until AirPort firmware 7.6.1. After careful review, eliminating all possible irregularities, that update apparently caused my MacMini to auto-increment its name after sleep, caused the older Extreme to regularly hang, and caused a general slowdown in speed. One other side-effect was that my iPad and iPhone Remote apps for iTunes control of the Mini also lost connection every time the computer name incremented.


Did reading here and around the traps, and after several months of head-scratching, back-slushed to firmware 7.6.0 (using AirPort Utility 5.6). Problems gone, speed back to normal, and my old Extreme seems stable (so far).


Annoying problem, and maybe even a real bug. Hopefully Apple will be able to address it in their next update.


Closing thought: Bugs come in all shapes and sizes, with shadings for every installation. While Apple's closed universe keeps things generally consistent and easy to diagnose, there are still irregularities. So, a small observation to those helpful individuals out there who post: if you don't have direct personal experience with a particular problem, it might be best to stay quiet. Grabbing at straws, telling people to reboot, restart, clear this and that, just increases frustration if they aren't true cures. To those folks who did their detective work, many thanks.

Jul 8, 2012 8:30 AM in response to Joachim Blunck1

Grabbing at straws, telling people to reboot, restart, clear this and that, just increases frustration if they aren't true cures. To those folks who did their detective work, many thanks.

yes, ditto that. many thx. but it's a real crapshoot out here Joachim... the internet is so full of crud, ya need tall boots! but at least things are better in here...

Jul 8, 2012 9:07 AM in response to coocooforcocoapuffs

Tall boots, indeed.


I have great respect for the patient helpers who try and glean useful information from generally inexperienced users in order to assist them. But as we know, once the inexperienced get a little knowledge they get dangerous. This issue is a case in point. If you search on the dozen or so variants of how this problem appears in forums, you get everything from reboots to rebuilds. What many fail to notice is the cause and effect of changes they make to their systems. This problem nagged me for awhile but frankly I didn't have the time to investigate thoroughly until today.


Ninety percent of the replies and offers of help were shoot-from-the-hip without grounding in the issue. A few more geeky types drilled deeper but most often down insane rabbit holes. The simplest answers are always found in the question, what's different?


I haven't done much looking, but perhaps the discussions here need a small section on how to help productively...

Jul 10, 2012 1:52 AM in response to benfrommiramichi

benfrommiramichi wrote:


it may be picking up the other computers names since it is on the server depending on whether you have the sync services on the server correctly set up

If you'd read the original post you'd see that it happens when there's no other computers on the network and whenever there is they don't have names anything like the server's name. Also, this happens immediately after a clean install of the OS so it’s not a misconfiguration issue.

Jul 10, 2012 8:21 PM in response to SwampFoetus

Hi Joachim,


You may not want to hear this but there are other WiFi AP/Router products out there. You may want to demote your Airport and just run it as an AP.


Last year I got fed up with similar issues on Linksys/Cisco and replaced the two I owned with other hardware running the DD-WRT open source Linux distribution. There are trade-offs with open source but consider that the cost of defect correction for cheap closed consumer grade Linksys/Apple network products is effectively infinite.


The low cost of these gadgets is such that the only economic fix for defects is really just to replace the gadget.


I have found DD-WRT solution to be as good as Apple's and much better than Linksys. It is some comfort that if I do have a problem I can, in principle, fix it myself without increasing landfill.


Good luck with the Airport microcode.

Jul 10, 2012 9:35 PM in response to SwampFoetus

I have the same issue and here is what I have tried and so far it is working for me. It's been only a day or so but the name has not changed.


I have a Mac Pro which was doing the changing and a macbook pro not changing.

Cable internet, Airport Extreme, upstairs airport express set to bridge off into a netgear giga switch Mac pro into netgear with two other computers XP and a open indiana.


1. open airport utility click Network tab click plus to add a DHCP Reservation add the address of the Mac Pro to the list my case 10.0.0.7 and update the extreme.


2. Mac Pro, system prefreneces, network, Configure IPv4: to Using DHCP with manual address, set address to the asme as you put into the extreme. my case 10.0.0.7


This seems to have stopped the numbering up, but I still had the Mac Pro (5) and that bugged me.


3. Mac Pro system preferences, sharing, change the name to whatever you want, then I changed it back to Mac Pro the (5) was gone and has not come back.


Hope this helps a bit.

Jul 11, 2012 2:30 AM in response to MacPro110

MacPro110 wrote:


1. open airport utility click Network tab click plus to add a DHCP Reservation add the address of the Mac Pro to the list my case 10.0.0.7 and update the extreme.


2. Mac Pro, system prefreneces, network, Configure IPv4: to Using DHCP with manual address, set address to the asme as you put into the extreme. my case 10.0.0.7

I've got the same setup, which is what I refer to in the 2nd point of my original post where I state I’m using a static IP address. It’s interesting that it works for you, though.


I also think the issue goes away when using wireless, but I haven’t confirmed this as I just use a wired connection. I do this for the extra speed I get over ethernet for backing up and restoring.


Can anyone confirm if the issue occurs when using 7.6.1, static IP and Wi-Fi combination?

Jul 11, 2012 2:33 AM in response to piperspace

piperspace wrote:


I have found DD-WRT solution to be as good as Apple's and much better than Linksys. It is some comfort that if I do have a problem I can, in principle, fix it myself without increasing landfill.


Can you configure mDNSResponder/Bounjour/SleepProxy on DD-WRT? I need this so that I can see my server and iOS devices on the network when they are asleep.

Jul 11, 2012 10:49 AM in response to piperspace

The latest:


From my earlier post: Backing down to 7.6.0 seemed to help for a day, then the problem reoccurred. I backed down to 7.5.2, no dice.


Noted MacPro110's recommendation to assign a DHCP reservation to the computer in question. I upgraded back to 7.6.0 (staying away from 7.6.1 because of performance issues with my older 1stG Extreme). Added a reservation as described in his post. Rebooted the modem, AirPorts and computers.


Problem is gone for now. I put the computer to sleep six times. Each time it woke up happy, stable, and most importantly, with its original name intact. We shall see...


Incidentally, for those who are interested: My network is a cable modem into a 5thG Extreme (sorry, I had said 4th). Wireless to one MacBook, one MBPro, one MBAir, one MacMini (only computer with the naming problem), a few iPads, a few iPhones, two APExpresses, and finally wireless to a 1stG Extreme that bridges to a MacPro via ethernet.


I'll report back to this thread if the situation remains stable. A guarded thanks to MacPro 110.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Computer Name changes when waking from sleep

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.