High Sierra 10.13.3 File Sharing Issue "Connection Failed"

Have the same problem: macbookpro with SSD/APFS; iMac with Fusion both on latest High Sierra.

I first could not connect at all.

Erased users of sharing. Entered them (from drop-down list). Yes I could connect.

But, now I can drop a file ('holiday pictures') in the destination machine. But it copies only one file, then says the file is there already and quits.

Awkward. My three macs wore working so well some (long?) time ago. . .

Maybe this is a separate issue?

I'm having this exact issue as well. New MBP's can't connect to each other except for screensharing and ssh... not direct filesystem connection (SMB or AFP). Older Macs (MBP and iMac) can connect to each other and the new MBP with filesharing (SMB or AFP) as well as with screensharing and ssh. This all started happening with the upgrade to High Sierra for me I think.

Having this issue as well.

• Mac Book Air (MBA) is able to access shares on the iMac, but not vice versa ('Connection Failed').
• Mac Mini can see shares on the iMac, but not on the MBA ('Connection Failed').
• iMac can not see shares on the MBA or the Mini ('Connection Failed').
• All three machines can access shares on my Synology NAS.

All three can screen share with one another. All three are on the same subnet, the MBA is connected via WiFi and the iMac and Mini are both wired. All three Macs are fully patched 10.13.6. I don't have SMB enabled on any of the machines (NAS included), only AFP.

I disabled SMB on all machines in an attempt to resolve an issue where I was continually having to Force Quit finder to reconnect to shares.

I tried adding Share-only users and that made no difference.

Ran out of time to edit apparently, to clarify what does and does not work:

• The MacBook Air (MBA) is able to access shares on my iMac, but not on my Mac Mini (Connection Refused).
• The iMac is not able to access shares on either the MBA or the Mini (Connection Refused).
• The Mini is able to access shares on the iMac, but not on the MBA (Connection Refused).
• All three machines can access shares on my Synology NAS.

I only get the 'Connection Refused' message if I enter a username and password that is valid on the machine that I'm attempting to 'Connect As' to.

I just upgraded to a brand new 2018 MBP. Same issues. Interestingly enough I can connect back to the shares on this new MBP from a PC laptop running Windows 10. All the other problems I previously described still apply.

I have an interesting situation with File Sharing between a Macbook Pro with High Sierra APFS and a Mac Mini with Mac OS X 10.4.11 (Tiger) formatted Mac OS Extended (journaled). Let's call the first Sierra and the second Tiger.

With both SMB and AFP enabled in File Sharing Options on Sierra and Personal File Sharing and Apple Remote Desktop enabled on Tiger, I can connect -- with full control and Screen Sharing -- from Sierra to Tiger through afp:// . From Tiger I can log in as a Sierra registered user but the connection is not completed properly and this is the screen that comes up.

On Sierra, the startup disk and Home folder as selected as shared volumes but nothing shows here.

This happens every time.

Have tried all kinds of steps but it makes no difference. These include setting up a Sharing Only user on Sierra, running legacy launchctl commands for disabling and enabling AppleFileServer and SMB, Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1 - Apple Support, disabling System Integrating Protection, but attempts to connect from Tiger always end up as above.

It really does not make much difference as I can move files either way through the Sierra connection.

Maybe Mojave will fix it, but better not hold your breath.

I've been having exactly the same issue, such a basic functionality of a network that doesn't work! I've got my Mac X which I'm trying to connect to from my MacBookPro Y, the connection constantly drops out from Y to X if it actually connects in the first place (normally it states 'connection failed'). Yet when I try and go from my Mac X to MacBook Y it connects. I've just upgraded my OS on my MacBook and will be trying the same on my Mac to see if this helps, but I'm not impressed at all with this lack of basic functionality.

Ditto.

The previous 'solution' was a fluke. It did not take. This has been escalated to engineering. I just need to find time to work through it with them and will report back later...

Not happy about APFS. Many problems with net connection with other *NIXes. Going to search if possible to initialize an SSD in HFS+. Maybe via Terminal.

Just curious, do you have Google Fiber? I do, wondered if the IPv6 issues was related to their router.

I am unable to connect via file sharing from my MBP (client) to my iMac (host) with or without IPv6 enabled. File sharing works in the opposite direction with identical settings.

I don't see any evidence here Apple broke anything. They did upgrade it.

Your own usage (filesystem settings) may need to be upgraded after a "major upgrade".

Settings has a network aware sharing that is highly capable (ie, can allow walking logins, sharing, lots of things).

Like someone else said above: even if you have your settings right (and there's no confirmation above you do), you still have to have your filesystem settings right as well, and a "good network connection".

i think it's far too soon to put the blame anywhere yet. we need to know more.

Except that many of us are reporting very similar issues related to file sharing (and this is not the only thread on it).

My three Macs are all using APFS on High Sierra or Mojave, sharing settings and firewalls are identical on every Mac, all are on the same subnet, but yet one Mac is inaccessible only for file sharing (whereas screen sharing and ssh work fine).