I am currently trying to look up the ip address of a mounted smb share for the purpose of accessing it via rclone. Ive tried many solutions, including the ones specified in [This Thread](https://apple.stackexchange.com/questions/10956/finding-the-remote-ip-address-used-by-a-mounted-smb-share) , but these didnt work as the commands couldnt identify the name:

-c 1 nas-smb.local

yielded

: cannot resolve bread._smb._tcp.local: Unknown host

and

lookup bread._smb._tcp.local

to resolve: filename too long

All i have is the local name bread._smb._tcp.local i know from mounting it via Finder - i tried pinging bread.local with the following result:

36 bytes from xyxyxyxy.t-ipconnect.de (unrelated IP): Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 9c79   0 0000  3f  01 f817 192.168.1.189  192.168.100.10

I assumed the Destination 192.168.100.10 the IP im searching but trying to connect to that IP directly or mounting to it yielded no result either. How can I look up these IP addresses for .local on macOS?

Is there a way to make dns-sd just list a service and then exit? I am using

dns-sd -L "abcdef123@MySpeaker" _raop._tcp. local.

To list an AirPlay device's details but it keeps running once that is done. Context: I have an AirPlay speaker that is slow to show up in the AirPlay speaker list on devices. The AppleTV shows up instantly so I was hoping to get some stats on when the speaker is slow to show up vs. not; as a way to understand what the issue might be.

In the sharing pane of System Preferences (or with scutil --set LocalHostName) you can change the Bonjour name. I have done this and in Terminal this works, scutil --get LocalHostName shows the new LocalHostname. But Apple Remote Desktop on other systems keeps seeing the old Bonjour name. Several reboots etc. haven't helped. Any tips how I can get this fixed?

I have AirPrint-compatible printer, and it works fine in my local network. Also I have a VPN (OpenVPN, TUN mode) server on my local network running on a Raspberry Pi. If I connect to my local network through the VPN I can access local resources, like shared disks, but AirPrint printer does not show up. How can I connect to my printer over VPN?

I'm struggling with the configuration of an HP Envy 7920e on MacOS 13.5. I added the printer but if I use the default driver (HP ENVY Inspire 7900 series-AirPrint 3.0), I get the error "Encryption Credentials Have Expired". I've already tried to renew the certificate (that's valid, by the way) and to re add the printer many times (see here: https://superuser.com/questions/1761248/encryption-credentials-have-expired-when-trying-to-print-to-network-printer-on-m) , but such an error persists. EDIT: I tried to download the certificate from the web interface of the printer manually, but then I can't add it to my keychain (I get Error: -25294)

**Question:** how can one re-create Apple’s defunct ‘Back To My Mac’ service with specific open-source tools or, if necessary, with limited custom (non-commercial) software? *(Ideally, this would be done in a way that would preserve integration with Apple applications such as Finder or Terminal; that might, however, happen automatically as soon as a VPN allowing network discovery is enabled on a particular computer.)* - - - **Background:** Apple discontinued the '[Back to My Mac](https://en.wikipedia.org/wiki/Back_to_My_Mac) ' service in (https://support.apple.com/en-gb/HT208922) after twelve years of operation. As I understand it, this used a combination of Wide-Area Bonjour, a VPN, and probably some sort of iCloud database/directory to automatically keep all of the Macs signed in under a particular AppleID on a VPN so that they could communicate and use built-in services such as file sharing (AFP/SMB), screen sharing, and SSH through NATs and with dynamic IP addresses. No network configuration was required, once one had signed into a computer with their AppleID and enabling the checkbox for 'Back to My Mac' in Settings. The other computers appeared in the Finder (and in other applications, such as Terminal) just as they currently do if they were on the same network. I believe the AppleTV (and possibly other devices) were also used to provide Wake-on-LAN functionality. --- **Conjecture:** It is possible that Apple discontinued this for any number of these (or other) reasons: 1. to minimize their engineering / maintenance costs 2. to drive iCloud Drive storage revenue 3. they had been licensing some of the underlying technology since the beginning, and wanted to avoid those costs 4. a key component was found to be covered by someone else's patent, patent(s) they were unwilling or unable to license It is of note, however, that they disabled the feature for all existing installations of older operating systems, instead of just making it an unsupported / depreciated feature. - - - **Possible starting points:** - if either of the last two reasons are true, does anyone know the patent numbers (or patent holders) and technologies that were licensed? - are there any open-source replacements for this functionality (beyond what Apple mentions in the above link)? - what technical references are available documenting Apple's implementation and what is still missing to create an open-source replacement? - do you know of any other online discussions of this topic that can be linked to this question? - - - **Technologies used by some iteration of BTMM:** - DNS-based Service Discovery (DNS-SD; RFC 6763 , RFC 8553 , RFC 8552 ) to announce host reachability information - Dynamic DNS update (RFC 2136 ) to refresh the DNS resource records (RRs) when a host detects network changes - DNS Long-lived Queries (LLQ / DNS-LLQ) to notify hosts immediately when the answers to their earlier DNS queries have changed (Wikipedia and IETF ) - IPv6 Unique Local Address (ULA; RFC 4193 ) as the host identifier - NAT Port Mapping Protocol (PMP / NAT-PMP; RFC 6886 ) to assist NAT traversal - Kerberos (RFC 4120 ) for end-to-end authentication - IPsec (RFC 4301 ) to secure data communications between two end hosts - - - **References:** - Understanding Apple's Back to My Mac (BTMM) Service - RFC 6281 *(June 2011)* - Take Control of Back To My Mac - Publishing Network Services - *Apple Developer Library Archive* - Authentication and Identification in Depth - *Apple Developer Library Archive* - Is it possible to use Back To My Mac DNS or routing information from the command line? - *AskDifferent* - Looking for information about the inner workings of Back To My Mac - *AskDifferent* - Did You Realize Apple’s “Back To My Mac” MobileMe Service Uses IPv6? - How does Back To My Mac work without UPnP or NAT-PMP? - *AskDifferent* - - - Thank you!! *(and thanks to jksoegaard for comments to the previous question)* *Note to moderator(s): this is a edited restatement of a previous question, “What technical and/or patent information exists for Apple's discontinued 'Back to My Mac' (BTMM) service, and/or what are possible replacements ”, that was recently auto-deleted; if you close this current question in the future, please consider doing so in a way that allows it to remain as a searchable reference for future users.*

Somewhere around macOS Ventura or Monterey, Apple changed the built-in Wi-Fi kernel driver so that the virtual device for AWDL represented in ifconfig now passes the activation state of AWDL data transfer calls through to the interface state directly. This means that disabling AWDL via ifconfig awdl0 down no longer works; any services using AWDL will immediately reenable it in less than a second. Previously, disabling the AWDL interface disables it for a long time, usually until the Mac wakes from sleep. Allowing AWDL discovery when it is unneeded causes significant jitter and overall degraded network performance on Wi-Fi if there are many Bonjour-discoverable devices in the proximity, especially noticeable on latency-sensitive protocols such as remote access (ssh) or remote desktop, and the only known workaround is now broken too. Is there a way to temporarily (or even permanently) disable the awdl0 virtual interface in Ventura? Possible ideas: - Unload the awdl0 interface - Both ifconfig awdl0 delete and ifconfig awdl0 unplumb fails with SIOCIFDESTROY: Invalid argument - Interface is loaded by the Airport driver (AirportBrcm*) alongside normal Wi-Fi driver functionality, unloading the driver will remove internet access - Disable or modify frameworks that applications use to make kernel calls for AWDL functionality - Requires changes inside the system image, bad for security as this requires bypassing signing - Disable the interface whenever it goes up by watching ifconfig - Doesn't solve lag spikes --- Edit: Latency graph demonstrating AWDL's new behaviour on Ventura and impact on wireless performance, plotted with gping at 20 pings per second to another host. Notice that it is not a flat latency increase, but adds incredibly high amounts of jitter. It isn't just AirDrop that can spontaneously enable AWDL; simple Bonjour discovery or even Apple TVs can activate it too.

My workplace uses Cisco AnyConnect VPN (but I have seen same problems with other VPNs as well, eg. here ) and it seems to break AirDrop, Sidecar and similar Apple's local network services. While I am connected to VPN on my macbook, I cannot AirDrop files to my macbook, and Sidecar doesn't start (shows a timeout error after a while). When I disconnect, everything works again. Is there a know set of things (ports, port ranges, network broadcasts?) I could change or enable in VPN settings so that the 'Apple stuff' would still be routed to a local network at home? It seems that now everything gets routed into work VPN. Thanks! I googled, but so far found only threads asking for help, with no solution.

# Background # I'm trying to implement AirPrint through static DNS, like documented on http://dns-sd.org/ServerStaticSetup.html . The iPad gets the dns search domain "lan" through DHCP, and I verified that in Settings-WLAN. I think I created all necessary entries in the right places, the iPad however doesn't find my printer or if it happened to find it, it showed a lock after the printers name and didn't print. (iOS version is 6.0.1) Has anyone here a clue, as to why iOS does not find the printer or if it finds it, why it shows it as locked? This is my setup (simplified with example domain) ## DNS entries ## ### Redirect to browse domain ### PTR b._dns-sd._udp.lan = bonjour.lan PTR lb._dns-sd._udp.lan = bonjour.lan ### Printer entries ### PTR _ipp._tcp.bonjour.lan = TestPrinter._ipp._tcp.bonjour.lan PTR _universal._sub._ipp._tcp.bonjour.lan = TestPrinter._ipp._tcp.bonjour.lan SRV TestPrinter._ipp._tcp.bonjour.lan = 0 0 631 mfp.printer TXT TestPrinter._ipp._tcp.bonjour.lan txtvers=1 qtotal=1 rp=Print ty=Toshiba MFP adminurl=http://mfp.printer note=Shared MFP priority=0 product=(Toshiba eStudio 351c) printer-state=3 printer-type=0xC0B0DE Transparent=T Binary=T Fax=F Color=T Duplex=T Staple=F Copies=T Collate=T Punch=F Bind=F Sort=T Scan=T pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf URF=none

I need to access Bonjour to get information from my printer and wonder where Bonjour has gone from Safari version 11.

I am currently running an application via Docker for Mac. I have ensured that the application is properly forwarding the ports via a docker-compose file. I have forwarded port 8083 from the application container to the host machine. I can access the application via "localhost:8083" in the host machines browser. Other computers on the network are experiencing a strange issue. I can access the application via other computers by using the host computers Bonjour (mDNS) address like so: "neptr.local:8083". However, I cannot connect to the application using the host machines IP address. "192.168.7.99:8083" does not connect to the application from any other computers on my network. Unfortunately, I need to be able to connect directly using an IP address as the application is intended to be used via a device that cannot resolve mDNS addresses. My networking setup is fairly mundane, an Eero system. The host computer is connected to a network switch via ethernet.

I have a Mac Mini and MacBook connected within my local network. Both Macs have System Preferences > Sharing > Screen Sharing turned **On**. For weeks I have seen each computer in the other's Finder sidebar. From there I was able to initiate Screen Sharing, browse the file system, etc. Suddenly, today, they are no longer appearing. I have restarted both Macs multiple times. I can also not connect directly to them with the Screen Sharing app. Typing the computer's name in the Connect To: results in the error: > Unable to resolve “MacName.local” > Verify the name you entered and make sure your network connection is working. Finder > Go > Connect to Server... similarly does not list any local Macs. Pressing + does strangely (re)add a shortcut to the Mac, which I've connected to before. But attempting to connect to it results in the error(s): > There was a problem connecting to the server. > URLs with the type “:” are not supported. > > There was a problem connecting to the server “MacName.local”. > The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again. **In modern macOS**, Big Sur or Monterey or newer, how can I reset this situation and see local network Macs in the Finder sidebar? The solutions offered in a [similar previous question](https://apple.stackexchange.com/questions/148649/shared-devices-not-appearing-in-network) no longer seem to apply in modern macOS. Those plist files are no longer present on my machines. Is there a modern way to reset this network sharing?

Scanning for Bonjour devices on my network shows a long and obscure string associated with my AirPort Base station using this Bonjour protocol _acp-sync._tcp. What is this? What is it for?

Well, I've never seen this one before - or have any idea how this would happen if you need to be in recovery to modify the file. This was the current output of my com.apple.mDNSResponder.plist when I was digging to disable Bonjour Multicast Advertisments:

Disabled
	
	Label
	org.apache.httpd
	EnvironmentVariables
	
		XPC_SERVICES_UNAVAILABLE
		1
		OBJC_DISABLE_INITIALIZE_FORK_SAFETY
		YES
	
	ProgramArguments
	
		/usr/sbin/httpd-wrapper
		-D
		FOREGROUND
	
	OnDemand

What would these settings accomplish? Because these are different than default, to me it looks like its trying to divert the DNS queries somewhere else. This could also be a result of hardening, but again, not sure how that would be possible if you need either SIP disabled, or need to be in recovery to accomplish.

---------- ---------- **tl;dr** In the Catalina terminal *ping lan-services.local* works but *ping lan-services* does not ---------- ---------- I have a 2012 Mac mini that I just installed Catalina on from scratch (i.e. blank SSD and USB install) connected to a home network via Ethernet that cannot find servers / devices on the LAN without appending '.local' to the name. This was not needed before Catalina on the same LAN set-up (i.e. the only thing I can think of that's changed is the OS on the Mac). e.g. ~% ping lan-services ping: cannot resolve lan-services: Unknown host ~ % ping lan-services.local PING lan-services.local (192.168.1.10): 56 data bytes 64 bytes from 192.168.1.10: icmp_seq=0 ttl=64 time=5.480 ms ... ^C ### Network Config for Ethernet ### - IPv4 configured *Using DHCP* - IPv6 configured *Link-local only* - DNS set to *1.1.1.1* and *208.67.220.220* (set by router) - Advanced / DNS / Search Domains is *local* (no dot as per help examples) - Mac Firewall is *OFF* - Everything else has not been changed (i.e. default to Catalina) ### /etc/hosts file ### No entries have been added (where not needed on Mojave) ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost ### VPN and Anti-Virus ### - VPN software installed BUT **NOT** active - this is the same as the previous Mojave install - Two VPNs Windscribe and Bitdefender (I could not load Bitdefender without its VPN software) - Disabling Bitdefender 'Shield' does not help ### Target servers / devices ### - Internet router is DNS server with a default domain as *local* - Some set up as static IPv4 in their config files - some dynamic - Internet router has static IPv4 assignments for the servers / devices - ISP does not support IPv6 so the router is set to RADVD (link-local) but NOT bound to an external interface - Finder correctly shows the server I am trying to PING - Finder opens the server shares fine (it is a Pi using Netatalk / AFP for file sharing **NOT** SMB) - Some devices have IPv4 only, some have IPv4 and IPv6 stacks loaded - No devices has any firewall settings that would stop PING or SSH ### scutil --dns output ### DNS configuration resolver #1 search domain : local nameserver : 1.1.1.1 nameserver[1] : 208.67.220.220 if_index : 5 (en1) flags : Request A records reach : 0x00000002 (Reachable) resolver #2 domain : local options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 300000 resolver #3 domain : 254.169.in-addr.arpa options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 300200 resolver #4 domain : 8.e.f.ip6.arpa options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 300400 resolver #5 domain : 9.e.f.ip6.arpa options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 300600 resolver #6 domain : a.e.f.ip6.arpa options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 300800 resolver #7 domain : b.e.f.ip6.arpa options : mdns timeout : 5 flags : Request A records reach : 0x00000000 (Not Reachable) order : 301000 DNS configuration (for scoped queries) resolver #1 search domain : local nameserver : 1.1.1.1 nameserver[1] : 208.67.220.220 if_index : 5 (en1) flags : Scoped, Request A records reach : 0x00000002 (Reachable) ### Things checked ### - A search turned up this question (though it seems to be a reverse issue) and the solution of adding *mdnsactivedirectory* via *discoveryutil* but that program seems to have been deprecated in Catalina - this was not required in Mojave. - I may not be the only one having this issue (going by this Apple Forum question ) but no domain is shown and the 'hint' is either talk to Apple or look at Active Directory (not installed here). - Turning on file sharing does not help. - Checked sons Windows 10 PC - he can reach devices without the .local as well as devices with the .local (pin lan-services checked **before** pin lan-services.local) and is running iTunes for his music. - A note from above test today I'm not running iTunes as Apple changed to iTune to the Music App - Just installed Discovery - DNS-SD Browser from eh App Store (thanks to Lily Ballard for this FOC package). This shows its picking up services from AFP over TCP and picking up all the devices on my home LAN (easier to play with): ### Workarounds I'm trying to avoid ### 1. Adding entries into /etc/hosts 2. Adding .local to the end of each server name by hand - me being lazy (though this is what I am currently doing) 3. Installing ANOTHER DHCP / DNS server (e.g. pi-hole / pfSense etc) 4. Downgrading to Mojave 5. Moving to SMB shares - one server does not seem to support SMB without a whole series of faff for security and performance is pathetic. TBH also I do not have a great deal of practice with SAMBA security (basic shares fine) and no spare cash in project to upgrade old servers if Samba does not run on them.

I have a printer Canon TR4550 connected over WiFi. MacOs 10.15. When I go to Add Printer dialog, it is listed, with Kind = Bonjour. But in Use:, there is supposed to be AirPrint driver, which it is not. What should I do? Canon offers no printers, referring to AirPrint.

I've read almost every thread related to this, yet no one has quite made it easy to access a table like the following. IP Address Hostname MAC Address 192.168.1.10 | myAppleTV | 02:78:42:9b:bb:12 192.168.1.10 | myiPhone | b2:18:4a:3a:42:22 192.168.1.10 | myiMac | 09:17:a2:95:c4:00 192.168.1.10 | myCanonPrinter| a0:ea:72:77:b4:aa Most of the time I use arp -a and there is also dns-sb, but none of them make it easy to find out 3 key pieces of information whenever I am messing around on the network, i.e., IP Address, Hostname and MAC Address. I am surprised that there isn't a utility that accomplishes this!

My iMac's name is windowlick. Every time I reboot it, for some reason it detects that the name windowlick is already in use on the network and renames itself with a random suffix, e.g. windowlick (3829) or the like, and it gets a zeroconf/bonjour hostname of windowlick-2.local instead of the usual windowlick.local. I can manually fix this by going to the Sharing preferences panel, but I'd rather not have to do this, especially since I often do remote access from an external network (via ssh to another machine that gets the incoming port assignment) and if my machine rebooted due to a power failure or a system update I don't like having to guess at the hostname. My computer gets its IP address via DHCP assignment from the router (a recent Netgear); it also behaved this way on my previous router (an Apple Time Capsule). It has a reserved IP address for its wired Ethernet port, but it connects via both Ethernet and Wi-Fi (which does not have an address reservation). I suspect that something to do with name assignment is doing something weird with the order of operations on the Wi-Fi vs. Ethernet interfaces. Unfortunately, I cannot simply disable Wi-Fi, as I make use of OS features that require that my Wi-Fi be active (for example, Unlock with Apple Watch). Is there any way to tell macOS to not be "polite" and rename itself if it sees "another" machine by the same name? This seems similar to https://apple.stackexchange.com/questions/55416/my-mac-minis-computer-name-keeps-changing-when-it-resumes-from-sleep but I don't have the problem when resuming from sleep, it's only after a reboot, and I already have the static IP assignment per the accepted answer on that question. Also, this doesn't happen on my MacBook (which does not have a static assignment).

Using a MBP running Catalina 10.15.6 I am unable to print to a networked Xerox printer. It discovers it just fine with Bonjour, connects, but when I print anything, it instantly pauses the printer, and in the printer job list dialog, it fails saying Ready to Print - 'Backend' failed, 2 pages. I've tried re-adding the printer, Reset the printing system with the right-click in the printer list, rebooting the machine. I have an old iMac also running 10.15.6 which can print to it, so I know the printer works. Any other ideas?

While know what AirPrint does, I am confused about what it is. It claims to be a bunch of technology standards used together such as mDNS, IPP and multicasting. However, the term Bonjour is also thrown around as well, which also appears to be based on the same technologies. What makes it even more confusing is that Bonjour is just a rebrand of Rendezvous. Is AirPrint a rebrand of Bonjour, the same way Bonjour is a rebrand of Rendezvous, or is AirPrint distinct from Bonjour?