Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

aalls159

macrumors newbie
Original poster
Jun 13, 2015
28
31
Iowa
Was looking about on the forum on the intel side and and noticed they where talking about the new file system (APFS) and they had a link to a apple support document on the matter and I noticed it said this
APFS compatibility
  • Devices formatted as HFS+ can be read and written to by devices formatted as APFS.
  • Devices formatted as APFS can be read and written to by:
    • Other APFS-formatted devices.
    • HFS+ formatted devices running macOS 10.12.6 or later.
For example, a USB device formatted as APFS can be read by a Mac running macOS High Sierra, but not by a Mac running OS X El Capitan or earlier.
was wondering if any of you have any thoughts on the matter and how we could go about getting them to talk if it proposes an issue because it also said this
APFS and file sharing
Volumes formatted with APFS can't offer share points over the network using AFP. SMB and NFS are supported when using APFS. The option to enforce only SMB-encrypted share points is also available.
from my understanding the new file system APFS can be shared but can't be read be older macs?
Would like to discuss below. Thank for your input :)
 
https://developer.apple.com/library...Management/Conceptual/APFS_Guide/FAQ/FAQ.html
You cannot share APFS-formatted volumes using AFP. The AFP protocol is deprecated.

Such is :apple:.

So, SMB is the only option for Leopard/Tiger/Panther(?) to connect.

I'm just downloading the latest beta 8 update (3GB) on my copy of High Sierra under VMWare Fusion 8.5.8. When I first ran the update from a VM of Sierra, it didn't give me the "convert to APFS" option during install. So, it's still under HFS+.

Once the update finishes, I'll attach a second virtual drive and format for APFS, leaving the AFP sharing option selected in File Sharing and see how Leopard handles connections to it...

* To be continued. *
[doublepost=1503978567][/doublepost]Prepare your institution for iOS 11, macOS High Sierra, or macOS Server 5.4
AFP can’t share files on APFS. When you upgrade to macOS High Sierra, the upgrade converts systems with all flash storage configurations automatically. You can't opt-out of the transition to APFS for these systems.

So, SSDs are automatically converted and there is no "Revert to HFS+" option!
 
Last edited:
As anticipated, Leopard and Tiger can't see the APFS volume when connecting via AFP.

And for some reason I can't get the old cats to see the SMB share when I have AFP disabled. I can't connect to the smb:// server by IP address, but it works from El Cap and Sierra without a hitch.

Is there a trick to getting Leopard to connect to a Mac SMB share? It seems to connect to Windows shares okay.

I think Apple have left PowerPC up the creek without a paddle on this one.
 
As anticipated, Leopard and Tiger can't see the APFS volume when connecting via AFP.

And for some reason I can't get the old cats to see the SMB share when I have AFP disabled. I can't connect to the smb:// server by IP address, but it works from El Cap and Sierra without a hitch.

I think Apple have left PowerPC up the creek without a paddle on this one.

Is this an SMB1 vs SMB2 issue?
 
Just a thought here but Could you set up one new Mac server and one Old mac server Before El Cap and have them both connected to a windows server independently doing the magic triangle, there by having the windows domain force them to see each other and their clients?
 
I don't care about Apple File System (APFS) or Resilient File System (ReFS).

I do care about being able to read (and maybe even write) to disks and network accessible file systems. The lowest common denominator seems to be FAT for disks and SMB for network accessible file systems -- which is sad.

I like the old formats and protocols. I'd love to get an old LocalTalk network going, but alas. I do use HFS+ and FAT on PowerPC Macs, and I do use AFP, SMB, NFS, FTP, and TFTP. Some of those are not so secure, and some are a bit (a lot) buggy / flaky. Somewhere in the vast wasteland of control panels of a "modern" Wintel machine you can turn on SMB2 and SMB1 as they only turn on SMB3 by default now.

I managed to get NFS and TFTP working on my PowerMac so that I can network boot off of it using BOOTP. The NFS volume(s) showed up in the file manager on my Linux desktop (as do AFP volumes) -- w00t!

I've been reading lots of discussion about ZFS. Apple once considered going with ZFS but dropped it.
 
Possibly, yes.
Try connecting using CIFS://192.168.x.x instead of searching for the share or using SMB://

CIFS will force SMB1. Don't believe, with the exception of third party software such as DAVE and AdmitMac, that SMB2 (which Apple started using by default with Mavericks) is usable by Leopard and earlier.
 
I can't confirm this with anything official, but it looks like the SMB1 protocol has been stripped out of Sierra/High Sierra.

I have tried a series of different settings:

1. CIFS:// to force SMB1, fails to connect Leopard and Tiger to Sierra and High Sierra SMB server
2. CIFS:// fails to connect Leopard and Tiger to El Capitan, but does ask for a password (unsuccessfully)
3. Tried forcing SMB1 protocol with:
Code:
echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf
I ran this on all machines, servers and clients and also copied the conf to /etc/nsmb.conf on each, rebooted everything, but the results remain the same.

Checking the server logs on each newer Mac OS, showed the same error message:
default 10:09:20.554853 +1000 smbd 10.1.1.88 SMB client not supported - Unicode strings are required

4. Tried manually connecting with Leopard from the command line without success
Code:
mount -t smbfs //10.1.1.168/APFSVolume share
mount_smbfs: server connection failed: Connection refused

It looks like High Sierra is not the first to be incompatible with SMB on older Macs, but as most Mac users have relied on sharing over AFP, I'm sure this has gone by unnoticed.

Can anyone confirm which is the most recent Mac OS X/macOS SMB share you can connect to from Leopard?
 
Leopard failed to connect to my late 2013 13in MBP with El Capitan 10.11.6 on it and it also failed to connect to my 2017 27in Imac with sierra. It Does Connect to my Lenovo home server with windows 10 Pro. It is also odd that it failed connect to the MBP because I was downloading classic games on it about a year ago then connecting my g5 quad to my MBP to install them because it downloaded faster and I know it was El Capitan because I was planning to install Sierra on it soon when it came out in the fall.

****Edit**** Will download El Capitan and Yosemite without updates on parallels to see if they work before any updates. Can't downgrade the MBP at the moment so I will have to try in in a vm.
 
Last edited:
Leopard failed to connect to my late 2013 13in MBP with El Capitan 10.11.6 on it and it also failed to connect to my 2017 27in Imac with sierra. It Does Connect to my Lenovo home server with windows 10 Pro. It is also odd that it failed connect to the MBP because I was downloading classic games on it about a year ago then connecting my g5 quad to my MBP to install them because it downloaded faster and I know it was El Capitan because I was planning to install Sierra on it soon when it came out in the fall.

****Edit**** Will download El Capitan and Yosemite without updates on parallels to see if they work before any updates. Can't downgrade the MBP at the moment so I will have to try in in a vm.

I have a similar recollection. I set up my Mac Pro '08 running El Capitan earlier in the year with an eSATA drive to use for Time Machine backups for all of my networked Leopard+ Macs. I recall just hitting the "File Sharing" option in El Cap's Preferences, without checking the settings and I could share files, but found I couldn't assign the TM drive to the Leopard Macs. I then found I had to enabled AFP in El Cap's File Sharing options and it worked fine. So as far as I can recall, regular file sharing was working over SMB Leopard->El Cap...

I could be wrong.

I can confirm Leopard -> Snow Leopard connects over SMB without any special config, but Leopard is refusing to connect to Lion (10.7) over SMB now. (even with CIFS and/or smb_neg=smb1_only) wtf? o_O
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.