Getting File Transfer Errors When Using MacNFS to Connect w/ Mavericks Mac

[supernova777]

to those others interested in investigating this issue further these are other properties of the appleshareclient
whether or not manipulating these values will make a difference in enabling a connection to a mac os 9 file share remains to be seen!

(mtn lion) defaults read /Library/Preferences/com.apple.AppleShareClient {     "afp_active_timeout" = 0;     "afp_allow_submounts" = 1;     "afp_allow_system_uams" = 0;     "afp_allow_user_uams" = 0;     "afp_debug_level" = 5;     "afp_debug_syslog" = 1;     "afp_disabled_uams" =  ();     "afp_forceKerberosOnly" = 0;     "afp_host_prefs_version" = 15;     "afp_idle_timeout" = 0;     "afp_immutable_dirs" = 1;     "afp_maxDirCache" = 60;     "afp_maxFileCache" = 60;     "afp_maxIOToleranceMSecs" = 0;     "afp_maxQuantumNbr" = 0;     "afp_maxQuantumSize" = 0;     "afp_maxSingleIOToleranceMSecs" = 0;     "afp_minDirCache" = 5;     "afp_minFileCache" = 5;     "afp_minIOToleranceMSecs" = 0;     "afp_minQuantumNbr" = 0;     "afp_minQuantumSize" = 0;     "afp_minSingleIOToleranceMSecs" = 0;     "afp_mount_defaultFlags" = 0;     "afp_no_caseSensitiveVols" = 0;     "afp_no_kQueues" = 0;     "afp_no_volChange_caching" = 1;     "afp_prefer_IPv4" = 1;     "afp_reconnect_allow" = 1;     "afp_reconnect_interval" = 10;     "afp_reconnect_max_time" = 600;     "afp_softautomount_vols" = 0;     "afp_softmount_vols" = 0;     "afp_wan_quantum" = 0;     "afp_wan_threshold" = 0; }

(snow leopard) defaults read /Library/Preferences/com.apple.AppleShareClient {     "afp_active_timeout" = 0;     "afp_allow_submounts" = 1;     "afp_debug_level" = 5;     "afp_debug_syslog" = 1;     "afp_forceKerberosOnly" = 0;     "afp_host_prefs_version" = 9;     "afp_idle_timeout" = 0;     "afp_immutable_dirs" = 1;     "afp_maxDirCache" = 60;     "afp_maxFileCache" = 60;     "afp_maxIOToleranceMSecs" = 0;     "afp_maxQuantumNbr" = 0;     "afp_maxQuantumSize" = 0;     "afp_maxSingleIOToleranceMSecs" = 0;     "afp_minDirCache" = 5;     "afp_minFileCache" = 5;     "afp_minIOToleranceMSecs" = 0;     "afp_minQuantumNbr" = 0;     "afp_minQuantumSize" = 0;     "afp_minSingleIOToleranceMSecs" = 0;     "afp_mount_defaultFlags" = 0;     "afp_no_caseSensitiveVols" = 0;     "afp_no_kQueues" = 0;     "afp_no_volChange_caching" = 1;     "afp_prefer_IPv4" = 1;     "afp_reconnect_allow" = 1;     "afp_reconnect_interval" = 10;     "afp_reconnect_max_time" = 600;     "afp_softautomount_vols" = 0;     "afp_softmount_vols" = 0;     "afp_wan_quantum" = 0;     "afp_wan_threshold" = 0; }

comparing the major differences here we see
"afp_host_prefs_version" has a different value on snow leopard compared to mtn lion..
could this be why the connection is denied?

another difference is:
afp_allow_system_uams" = 0;
afp_allow_user_uams" = 0;

0 we all know = no.. 1=yes.. maybe toggling these to 1?

[supernova777]

found a post directing people to this site:
http://www.applefool.com/se30/

looks like its worth checking out
yep they have DETAILED chart of what can connect to what!!
check it out! >> Apple Filing Protocol Ethernet Networks
This section is for reference only. Some areas may not be exactly accurate, but are listed as best as our testing could indicate.

at the bottom u see clearly this :

Personal to-do list for this Guide:

    Determine how much memory System 7 will address in 24 bit mode.
    Test Optima and Maxima with a 24-bit only application -- i.e. The Dungeon of Doom, Thexder, Rex Nebular... in System 6. Report on memory available.
    Test IPNetRouter.
    Play with MacWWW under System 6 and report the results.
    Using 10.7 and 10.8, test the "legacy" AFP authentication mode with 8.1 or suitable "old client" and 9.0, 9.1 and 9.2. If connection is successful, create new AFP 10.7 and 10.8 sections.
    Can a 512K with the HD20 init read 400KB HFS disks? Can the 128Ke borrow the HD20 init to read the same?
    Try using LocalTalk Bridge on a bridge mac to communicate a 10.5+ Mac through the bridge Mac with LocalTalk bridge to something like a Plus. Note: has to be something like a G3/233 beige model with 9.2.
    Fiddle with MacTerminal 1.1 and see what happens on a 512K. If positive results are produced, add section under the terminal emulators area. Also test it on a 128K if you can, and if you add the section, toss this link in a passing note.
    AFP bridge test with Netatalk and Windows 2K Server with AS1.1.
    Verify that 10.6 setup and procedure is like 10.5.

so it seems many experts still havent done thorough testing enuff to say for sure

[supernova777]

i just personally tested ..
booting into mountain lion (because its the highest os i have, i dont have mavericks atm)
and i could connect just fine to my AFP fileshare thats running nas4free os..
WORKS 100%

i have to figure out what version of afp nas4free uses
because this works fine for any os.. 9->10.8
there must be a source of information to detail what is happening differently
with the mac os 9 AFP version vs the Nas4free AFP version
other then simply the different version spec of AFP


http://doc.freenas.org/index.php/Apple_%28AFP%29_Shares
states : FreeNAS® uses the Netatalk AFP server
if freenas uses this... nas4free most likely uses it aswell.

[supernova777]

http://www.dikant.de/2011/08/10/lion-and-legacy-afp-connections/

this page says u need to repair perms + reboot for the change to become effective!!
(which i did not do!)

After another reboot, the AFP shares are now working again.

tried a reboot.. no change still.
legacy doesnt neccessarily mean this version of afp that os9 is using.. but
there must be a way to make it work. i still believe;)

defaults read /Library/Preferences/com.apple.AppleFileServer

[supernova777]

another compare

mtn lion defaults read /Library/Preferences/com.apple.AppleFileServer {     TCPQuantum = 1048576;     activityLog = 0;     activityLogPath = "/Library/Logs/AppleFileService/AppleFileServiceAccess.log";     activityLogSize = 1000;     activityLogTime = 7;     admin31GetsSp = 0;     adminGetsSp = 1;     afpServerEncoding = 0;     afpTCPPort = 548;     allowRootLogin = 0;     attemptAdminAuth = 0;     authenticationMode = "standard_and_kerberos";     clientSleepOnOff = 1;     clientSleepTime = 24;     createHomeDir = 1;     errorLogPath = "/Library/Logs/AppleFileService/AppleFileServiceError.log";     errorLogSize = 1000;     errorLogTime = 0;     fullServerMode = 0;     guestAccess = 1;     idleDisconnectFlag =     {         adminUsers = 1;         guestUsers = 1;         registeredUsers = 1;         usersWithOpenFiles = 1;     };     idleDisconnectMsg = "";     idleDisconnectOnOff = 0;     idleDisconnectTime = 10;     kerberosPrincipal = "afpserver/LKDC:SHA1.9F783E87D7F7B4559A9A60E659E978D88A2B963F @LKDC:SHA1.9F783E87D7F7B4559A9A60E659E978D88A2B963F";     loggingAttributes =     {         logCreateDir = 1;         logCreateFile = 1;         logDelete = 1;         logLogin = 1;         logLogout = 1;         logOpenFork = 1;     };     loginGreeting = "";     loginGreetingTime = 0;     maxConnections = 10;     maxGuests = 10;     noNetworkUsers = 0;     recon1SrvrKeyTTLHrs = 168;     recon1TokenTTLMins = 10080;     reconnectFlag = "no_admin_kills";     reconnectKeyLocation = "/private/etc/AFP.conf";     reconnectTTLInMin = 1440;     replyCacheQuantum = 32;     sendGreetingOnce = 0;     shutdownThreshold = 3;     specialAdminPrivs = 0;     tickleTime = 30;     updateHomeDirQuota = 1; }

snow lep defaults read /Library/Preferences/com.apple.AppleFileServer {     TCPQuantum = 1048576;     activityLog = 1;     activityLogPath = "/Library/Logs/AppleFileService/AppleFileServiceAccess.log";     activityLogSize = 1000;     activityLogTime = 7;     admin31GetsSp = 1;     adminGetsSp = 0;     afpTCPPort = 548;     allowRootLogin = 0;     attemptAdminAuth = 1;     authenticationMode = "standard_and_kerberos";     clientSleepOnOff = 1;     clientSleepTime = 24;     errorLogPath = "/Library/Logs/AppleFileService/AppleFileServiceError.log";     errorLogSize = 1000;     errorLogTime = 0;     guestAccess = 1;     idleDisconnectFlag =     {         adminUsers = 1;         guestUsers = 1;         registeredUsers = 1;         usersWithOpenFiles = 1;     };     idleDisconnectMsg = "";     idleDisconnectOnOff = 0;     idleDisconnectTime = 10;     kerberosPrincipal = "afpserver/LKDC:SHA1.181CBD9AFEC66B4A2C4362B75D86278D2D9842B0 @LKDC:SHA1.181CBD9AFEC66B4A2C4362B75D86278D2D9842B0";     "lock_manager" = 1;     loggingAttributes =     {         logCreateDir = 1;         logCreateFile = 1;         logDelete = 1;         logLogin = 1;         logLogout = 1;         logOpenFork = 1;     };     loginGreeting = "";     loginGreetingTime = 0;     noNetworkUsers = 0;     permissionsModel = "classic_permissions";     recon1SrvrKeyTTLHrs = 168;     recon1TokenTTLMins = 10080;     reconnectFlag = "no_admin_kills";     reconnectTTLInMin = 1440;     replyCacheQuantum = 32;     sendGreetingOnce = 0;     shutdownThreshold = 3;     specialAdminPrivs = 0;     tickleTime = 30;     updateHomeDirQuota = 1; }

adminGetsSp = 0;
 fullServerMode = 0;
attemptAdminAuth is off instead of on
afpServerEncoding  is in mtnlion but  not sl
here i see reference to private/etc/AFP.conf in the mtn lion settings..
but sl version only has: permissionsModel = "classic_permissions";

but this is the SERVER not the CLIENT so its not much relevant i was just digging for clues

[supernova777]

http://netatalk.sourceforge.net/

2.x manual
http://netatalk.sourceforge.net/2.2/htmldocs/

3.x manual
http://netatalk.sourceforge.net/3.0/htmldocs/

ok so i've learned that basically mac os x uses the same component called "netatalk" server compiled within itself to provide this AFP support
the problem is the netatalk server component itself
in version 3.x they drop support for Appletalk over ip -consulting the manual its easy to see this appletalk section is omitted in the 3.x but present in 2.x
but in version 2.x they still support this
this is why snow leopard works while lion + above do not

im wondering if theres a way to downgrade the netatalk component compiling it yourself
to make it compatible..

[supernova777]

http://netatalk.sourceforge.net/2.2/htmldocs/configuration.html

AFP (the Apple Filing Protocol) is the protocol Apple Macintoshes use for file services. The protocol has evolved over the years. The latest changes to the protocol, called "AFP 3.3", were added with the release of Snow Leopard (Mac OS X 10.6).

here we see its AFP V3.3 that is present in osx snow leopard.

here we see some useful info regarding different versions of AFP
https://developer.apple.com/library/mac/documentation/Networking/Conceptual/AFP/AFPVersionDifferences/AFPVersionDifferences.html#//apple_ref/doc/uid/TP40000854-CH230-SW1
>> AFP 3.4 Introduced in OS X v10.8
what is interesting to note that there isnt much changes noted from afp 3.3 (which is what is in snow leopard)
and afp 3.4 (which is what is in mtn lion)
it states that this info was updated in december of 2012 :
2012-12-13   Added information about AFP 3.4

lion was released July 20, 2011
so this whole issue about people claiming it is the AFP version that is breaking the compatibility *CANT BE TRUE* because
10.7 was released far before afp 3.4.. and thats when the compatibility was broken....
if snow leopard uses afp 3.3 then so must 10.7 lion,
unless.. it takes from july 20th 2011 till december 13th 2012 for them to update a few documents!

i think this page describes security/user authentication and illustrates
https://developer.apple.com/library/mac/documentation/networking/conceptual/afp/AFPSecurity/AFPSecurity.html#//apple_ref/doc/uid/TP40000854-CH232-SW1



here u see this illustration talking about version in the packet... "AFPVersion"
there is some configuration that has been changed i believe in 10.7+ that simply changed this version to allow
like they have disabled this from working ..

[MacTron]

the problem is the netatalk server component itself
in version 3.x they drop support for Appletalk over ip -consulting the manual its easy to see this appletalk section is omitted in the 3.x but present in 2.x
but in version 2.x they still support this
this is why snow leopard works while lion + above do not

I'm not following this thread (just by moderation request). But I have the Netatalk version problem in one of Linux machines of mine. I cant upgrade the Linux version because the Netatalk upgrade lost the ability to be connected to a Mac Os 9 machine...

im wondering if theres a way to downgrade the netatalk component compiling it yourself
to make it compatible..
this netatalk can be installed on

In linux this some times can be done force installing the old version... but this is not a ordinary procedure... may be this way in Mac Os X also...

[supernova777]

hi mactron
it would be great to figure out a way to enable true direct filesharing over AFP to mac os 9.
if it was a hack that we could understand 100% and continue to implement on even 10.10 that would be really cool
im trying to collect more information on this topic but its hard to find the details
especially when apple gives such vague error messages that tell u literally nothing

[supernova777]

http://www.macwindows.com/MacOS9.html#110300

hmm is this page is saying using the old appletalk (not over ip address) is even faster then AFP over ip?

[MacTron]

hi mactron
it would be great to figure out a way to enable true direct filesharing over AFP to mac os 9.
if it was a hack that we could understand 100% and continue to implement on even 10.10 that would be really cool
im trying to collect more information on this topic but its hard to find the details
especially when apple gives such vague error messages that tell u literally nothing

Very little I know about Netatalk and furthermore it isn't on my main interests:
It is a open source Package that runs on UNIX/LINUX based Operating Systems.
I use it on Debian to Connect it to my Mac Os 9 machines. May be there is a version for Android too... I also used on my (now broken iPad) for the same purpose. The iPad version can give some idea about the Mac Os X version, because it was a non official add-on (cydia repo)

[supernova777]

http://download.cnet.com/Microsoft-UAM/3000-2092_4-2904.html

here we have a UAM modification by microsoft for more secure AFP connection to windows 2000 servers from mac os 9
see so obviously its possible to edit/re-configure the UAM (User Authentication Method) for AFP on mac os 9

[supernova777]

anyway i think i will leave this be for now.
im happy to know that my osx of choice works to access mac os 9 computers directly (snow leopard)
and i literally have no use for lion, mtn lion, mavericks or yosemite..
snow leopard does everything i need;)
i dont even need to use it this way with my AFP NAS server that (MIRACULOUSLY) works with every version..
with no hack or fuss ... (Thank god)

but, maybe someone else will find some more info on this in the future.

few questions in my mind as i walk away frm this:
a) what authentication method does AFP use on mac os 9? if it is cleartext and limited to 8 characters i cant tell but i do know that my password that i have set now
that works is exactly 8 characters;) so maybe i was lucky to pick this password to avoid any problems hehe
b) what version of AFP does mac os 9 use? is it AFP2.2?

http://azchipka.thechipkahouse.com/connecting-older-afp-servers-mavericks/10017/
this was the page from which knez linked the image above

[IIO]

thats great to heat that AFP works for you with 10.5. but i believe the thread starter was talking about the outlandish combination of him & NFS & mavericks.

anyhow, if i was eone of you i would just user a server/client system to download stuff and then open it locally. on everything slower than gigabit ethernet it seems pointless to open files directly from a workgroup server.

[supernova777]

thats great to heat that AFP works for you with 10.5. but i believe the thread starter was talking about the outlandish combination of him & NFS & mavericks.

anyhow, if i was eone of you i would just user a server/client system to download stuff and then open it locally. on everything slower than gigabit ethernet it seems pointless to open files directly from a workgroup server.

i said i was using 10.6.x not 10.5 and that was in reference to connecting DIRECTLY to the mac os 9 filesharing
its confusing to say "afp works for you" because like i stated earlier there is more then one scenario to use AFP.

I reccommend using an AFP capable (http://en.wikipedia.org/wiki/Network-attached_storage) such as nas4free (http://www.nas4free.org)
it works with every mac os version from 7.5 -> thru to 10.9 + 10.10
best solution. period.
u can use this anyway u wish. opening files directly on server.
or using it just to copy files to + from modern macs to pcs to legacy macs
this way does NOT require mac os 9 file sharing to be enabled..
Why is this a plus? because mac os 9 filesharing over tcp/ip STILL REQUIRES APPLE TALK TO BE ACTIVE
and we know that this can cause problems with audio related software which is why those software prompt to
turn appletalk OFF when launched..
so really.. mac os filesharing IS NOT AN OPTION for anyone who wants stability in their audio/midi production
because we require appletalk to be disabled

[IIO]

i have never turned on appletalk in my whole life except when some dumb installer had the idea top change my system without asking.

that is of course all a matter of taste, but i tend to recommend everyone to use server/client systems and copy files instead of reading from a workgroup server. in my opinion apple and microsoft were never able to explain the average user how this stuff works, which is why most people are using different things (server sofware for private people, and (not PC based-) NAS disks when you want to load files from somewhere.)

same with websharing, itunes, sherlock ... there is only one place for these things: the trash.

oh, and when you want to connect an oldworld PPC via its ethernet card, make sure you use cat-5 or higher ... can save some headache.

[mylk]

You can get Apple combo update 10.5.8 and extract server file from it (replacing /System/Library/CoreServices one). This was last AFP server with appletalk support. This solution worked for me in ML and should work on Mav. as well. Now my OS9 machines are able to connect OSX shares.

[DieHard]

Unfortunately Mavericks has documented issues when even copying large files to a local FW drive... the copy slows down almost to the point of freezing at times.  There are several temporary "fixes" with terminal commands that I have tried, but this issue actually forced me away from Mavericks on (2) production Mac Pros. 

As stated many times, in the Intel Mac OS X Audio arena, Snow Leopard is the clear stable/speed champion.  With ML a second for those who need newer OS for Native Instruments Plugins. 

IMO, anything newer than ML seems to have quirks that really impead the Music creating process.

[IIO]

everything higher than MacOS 9.3.5 already has quirks.