![]() The use of cmd-K (then entering the IPv4 address) would avoid use of IPv6. My knowledge of IPv6 is sketchy at best, but I’m now wondering if Monterey might be preferentially attempting to connect to the mini using IPv6 when one clicks on the icon in a Finder window’s sidebar. The failure might due to a limitation in Connect to Server, or might be due to a bug in the IPv6 implementation. ![]() I don’t know if the Connect to Server dialog is IPv6 literate. But attempting to connect with smb:// :445 fails If I use the Connect to Server method, the first two addresses always succeed. The latter is the self-generated Link-local IPv6 address of the Mac mini. The Mac mini is advertising itself as an SMB server with three addresses for SMB over TCP/IP: Using a Bonjour browser utility, I looked at the Bonjour broadcasts on the LAN. I’ve done a little more investigation, and I think the issue might be related to addressing. What’s the mechanism by which you think DNS might be an issue? I may be overlooking something… But file sharing from one Mac on the LAN to another is entirely local. Is it even in the loop for resolving local IPs? Resolving a host name in your example above (“ ”) requires a query to a DNS somewhere in cyberspace to obtain the server’s public IP address. It’s also a good way to rule out DNS issues when you can test smb://192.168.1.6 vs smb:// Insights or suggestions will be most gratefully received. Apple can’t possibly have botched implementation of file sharing in Monterey… There’s gotta be something pretty basic that I’ve overlooked. The Mac mini has its internal SSD, plus an external 2TB drive dedicated to TM backups (another major headache), and a 4TB RAID drive which is the family repository for photos, movies, music, s/w distros, and other the digital detritus that one collects.I ruled out any mystery WiFi issues by buying a USB-C adaptor and connecting the MacBook Air with an ethernet cable directly to the same GigE switch connecting the Mac mini.WiFi coverage is a pair of Unifi 802.11ac access points, one upstairs, one downstairs.However, an Early-2015 MBAir running Mojave handles file sharing connections to the Mac mini just fine. My wife’s MBAir (still on 14.3) exhibits the same problem. I’m pretty sure that this is a Monterey issue. Nor did the recent update to 14.3.1 (an 8-hour download ordeal). In any event, the re-install of Monterey made no difference. That odyssey took over 24 hours to download the 14.3 installer (over my 500 Mbps fibre connection)! Parenthetically, I’ve determined why the download from Apple’s update server was so sluggish. He eventually suggested that I boot the MBAir into the Recovery partition and re-install Monterey from scratch. He apparently sent the massive log files off to Engineering, but no insight was obtained. He had me install their Capture Data utility on both machines, and use it to capture detailed logs from the MBA and the Mac mini simultaneously while attempting a connection. I contacted Apple support, and eventually made my way through the AppleCare gauntlet to a Senior Advisor who took an interest. Or smb://miniserver.local (the miniserver’s mDNS name). While investigating this headache, I found that I can successfully connect using Finder/Go/Connect to Server… (Cmd-K shortcut), and then entering smb://192.168.1.6 (the IP of the Mac mini). If I then select one with a double-click, it generally take 30 seconds before the list of files & folders on the volume appears. Occasionally, after 10-20 seconds, the list of available volumes available on miniserver will appear. This solicits the Name and Password pop-up window to establish the connection, which then usually fails with an error box: “ There was a problem connecting to miniserver. This usually fails after 30s (with Connection Failed), but I’ve seen it take as long as 4:30 to timeout and report failure.Īnother way of connecting is with the Connect as button at upper-right of the Finder window. Clicking on miniserver displays Connecting… at the top of the Finder window. The miniserver appears in the list of locations in the sidebar of a Monterey finder window (as it should). Attempts to connect to ‘miniserver’ from a Finder window on the MBA are problematic. I have an M1 Mac mini (Big Sur) running on our network as a household file server, among other things. I’m hoping the TidBITS brain trust might have some insights on what’s going on. More hours on the phone with Apple support have been fruitless. Hours troubleshooting and searching on Google, without success. The latter shipped with Monterey, and has been nothing but headaches, not the least of which is an on-going problem with something as basic as file sharing. At the start of the year, I retired a much-loved 2015-vintage MacBook Pro running Mojave and replaced it with an M1 MacBook Air.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |