Click to expand.Such is. 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.
Hello, Does anyone know of a gui TFTP server for Mac OS Sierra?
To be continued. I don't care about (APFS) or (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. Code: echo 'default' /Library/Preferences/nsmb.conf; echo 'smbneg=smb1only' /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:53 +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. 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.
![Sierra Sierra](http://www.petenetlive.com/wp-content/uploads/2016/10/001-Same-Subnet.png)
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. 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. Click to expand.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 smbneg=smb1only) wtf?