hrhost.blogg.se - Apple thunderbolt ethernet adapter mac address unexpected

#Apple thunderbolt ethernet adapter mac address unexpected mac os#
#Apple thunderbolt ethernet adapter mac address unexpected code#
#Apple thunderbolt ethernet adapter mac address unexpected Bluetooth#
#Apple thunderbolt ethernet adapter mac address unexpected windows#

To direct clients to browse a different domain, substitute that domain in place of PTR In the list of services below, the SRV records will typically reference dot-local Multicast DNS names. The number suffixed hostnames are visible when using the Apple provided DNS Service Discovery utility dns-sd:įor example, using hostname my-mbp-hostname, it might show up like the following entries dns-sd -Z _ssh._tcp

#Apple thunderbolt ethernet adapter mac address unexpected mac os#

Somehow the entry is seen as duplicate and triggers the Mac OS suffix renaming behavior. This could be some kind of race condition. Somehow, the prior hostname of the Macbook or Apple device gets persisted somewhere in mDNS, or perhaps some form of ARP table + hostname information which is discovered and stored by the Macbook or Apple device.

#Apple thunderbolt ethernet adapter mac address unexpected windows#

My theory is that somehow mDNS also known as Bonjour ( Avahi to Linux users, or Zero-conf Networking to Windows users) may be partly to blame. That is to say: Through all my research online and testing I have not been able to determine definitively why Mac OS decides that the name is already in use when it clearly is NOT and never has been.

The true cause of the "trigger" of this behavior is unknown and unverified.

#Apple thunderbolt ethernet adapter mac address unexpected Bluetooth#

In ALL of my testing, the hostnames I've chosen have NEVER been used before on the network and additionally had NEVER been used for any Bluetooth devices as well.

#Apple thunderbolt ethernet adapter mac address unexpected code#

The cause of this behavior is due to some daemon code running in Mac OS which attempts to add a numbered suffix (N) any time that the same hostname is found on the network. I've observed this number to immediately be set to either (4) or (5) recently after using the scutil -set commands above. This is usually < 24 hours, but sometimes the ComputerName even changes immediately to have a suffixed number in parentheses (N). In my experience, setting the hostname this way, or through the standard System Preferences→Sharing→Computer Name only lasts a short period of time. Shut down and reset ALL networking hardware

Sudo launchctl load -w /System/Library/LaunchDaemons/ Sudo launchctl unload -w /System/Library/LaunchDaemons/ # Check for mDNSResponder with: ps auxww | grep -i mDNSResponder # Check for discoveryd with: ps auxww | grep -i discoveryd Turn Bonjour off and back on # Yosemite (10.10) (and other versions with discoveryd?)

Ensure you have only one connection to the local network.

If you find that none of this is doing any good, there are some other reported solutions which include: Then, retry again to reset your computer name using above scutil commands. If this still did not work, try killing the mDNSResponder service: sudo killall -HUP mDNSResponder Sudo discoveryutil mdnsrestartregistrationsĪfter flushing mDNS cache, retry renaming your machine using the commands above. # check if you have discoveryutil command with: which discoveryutil # check if you have dscacheutil command with: which dscacheutil If this did not help, try flushing your mDNS cache: # El Capitan (10.11) and later You may also try forcing ComputerName back by using the System Preferences→Sharing→Computer Name text field preference.

Once off, rename your machine using the commands above to finish.

System Preferences→Energy Saver→Wake for Wi-Fi network access → Unchecked.

If the Macbook keeps immediately renaming ComputerName back with a suffix, you may be able to make it stop by turning off Wake for Network Access. My_hostname='your-hostname-here' for key in LocalHostName ComputerName HostName do sudo scutil -set $key $my_hostname doneĪfter running this command, you can check that all places where they store hostname are the same with this one-liner:įor key in LocalHostName ComputerName HostName do sudo scutil -get $key done Like other users, I'm plagued by this annoyance but have found a semi-satisfactory workaround: