I've had an M1 Mac mini since July 2021, but late last year I've started having this problem where the computer keeps changing its name. It's done this about 10 times. Not an important issue, but confusing. Any ideas as to why it's doing this?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
My Mac keeps changing its name
- Thread starter awshucks
- Start date
- Sort by reaction score
... and you don't have any other Mac mini systems on your network which have an administrator account set up with the user first name "Han" ?
I did a search for these keywords:
mac network name keeps changing
One of the interesting possibilities I hadn't previously considered is a loop in the LAN configuration:
discussions.apple.com
In short, some part of the network, or a device on the network, is creating a loop, so that when the M1 Mac mini sends multicast packets, it ends up detecting itself, perhaps on a different interface. For example, if the Ethernet and Wifi are on separate subnets, and something like a switch happens to connect the two subnets, then when the mini sends a packet on Wifi it ends up appearing on its Ethernet interface, which causes the Wifi mDNS name-collision-avoider to act as if there's another computer that already has the name it wants to use. The reality is that it's responding to itself, but doesn't realize this.
The short answer to "Why does the name keep changing" is "Because a device on the network says it's already using that name". If there are no other devices at all, then the logical conclusion is that the Mac mini is responding to its own mDNS packets. That could be a loop in the network, or it could be something unusual with the network configuration of the Mac mini. The '
If the problem is a network loop rather than a host misconfig, then you may need to reset your router to factory settings, and temporarily disconnect all devices other than the Mac mini.
Another thing you can try is to temporarily turn off all of the mini's network interfaces except one, say Wifi. If that works, then enable the interfaces one at a time and see what happens. If the name-conflict alert appears, you know the problem is with that interface.
I think you'll need to describe your network in some detail. That means things like router model, any switches, all other devices, and exactly how the router is configured (guest networks, separate subnets for Wifi & Ethernet, etc.).
mac network name keeps changing
One of the interesting possibilities I hadn't previously considered is a loop in the LAN configuration:
macOS keeps changing computer name - Apple Community
In short, some part of the network, or a device on the network, is creating a loop, so that when the M1 Mac mini sends multicast packets, it ends up detecting itself, perhaps on a different interface. For example, if the Ethernet and Wifi are on separate subnets, and something like a switch happens to connect the two subnets, then when the mini sends a packet on Wifi it ends up appearing on its Ethernet interface, which causes the Wifi mDNS name-collision-avoider to act as if there's another computer that already has the name it wants to use. The reality is that it's responding to itself, but doesn't realize this.
The short answer to "Why does the name keep changing" is "Because a device on the network says it's already using that name". If there are no other devices at all, then the logical conclusion is that the Mac mini is responding to its own mDNS packets. That could be a loop in the network, or it could be something unusual with the network configuration of the Mac mini. The '
ifconfig command in a Terminal window will list all the interfaces, so that might be something to consider posting.If the problem is a network loop rather than a host misconfig, then you may need to reset your router to factory settings, and temporarily disconnect all devices other than the Mac mini.
Another thing you can try is to temporarily turn off all of the mini's network interfaces except one, say Wifi. If that works, then enable the interfaces one at a time and see what happens. If the name-conflict alert appears, you know the problem is with that interface.
I think you'll need to describe your network in some detail. That means things like router model, any switches, all other devices, and exactly how the router is configured (guest networks, separate subnets for Wifi & Ethernet, etc.).
Last edited:
Why not change the hostname to one of your choosing, rather than letting the system decide on a default name?
Problem develops when the generic default hardware name is less random than you might think, and, when your system finds another, identical hostname on whatever your network is at the time, it is forced to change your hostname.
Problem develops when the generic default hardware name is less random than you might think, and, when your system finds another, identical hostname on whatever your network is at the time, it is forced to change your hostname.