

- #NETATALK AFP SERVER SET UP USER MAC OS X#
- #NETATALK AFP SERVER SET UP USER UPDATE#
- #NETATALK AFP SERVER SET UP USER FULL#


#NETATALK AFP SERVER SET UP USER MAC OS X#
Now your WD sharespace WILL work wth AFP again in Mac OS X Lion 10.7 Sudo defaults write /Library/Preferences/ afp_disabled_uams -array “Cleartxt Passwrd” “MS2.0” “2-Way Randnum exchange”
#NETATALK AFP SERVER SET UP USER FULL#
This will cause the AFP Client to create the full preferences file Launch /Applications/Utilities/Terminal and do:ĭefaults write /Library/Preferences/ afp_host_prefs_version -int 1įrom Finder, select an AFP server, or use “Connect To…”.So until then (whenever that is) lets just turn DHCAST128 back on and the problem goes away… There is no timeframes as to when WD will release the AFP 3.3 version of the firmware, as the protocol itself is still in beta and it would be very stupid of them if they released a firmware with beta software in it… This WILL be the new standard and WD are working on a beta firmware right now which has AFP 3.3 in it. Now, there is a new version of netatalk 2.2 which is in beta atm that is a new version of AFP called AFP 3.3. Lion uses netatalk 2.1.3 which is functionally identical to 2.1.2 but with one change to AFP 3.2 which is causing this problem.Īpple in their wisdom, figure that a particular authentication protocol within the implementation of AFP 3.2 called DHCAST128 is very insecure, so they turned it off… It hasn’t been removed, but just turned off within Lion.īecause WD Sharepaces use AFP 3.2, WD did the right thing and used DHCAST128 (As per Apple’s guidelines) so its not WD’s fault that this problem arose, its Apple’s fault for changing the standard… This problem only happened when we all updated to Mac OS X 10.7 (Lion)
#NETATALK AFP SERVER SET UP USER UPDATE#
What that means is if you update your WD sharespace to the latest firmware (as of this post) it WILL work with Mac OS X 10.2 - 10.6.8 WD Sharespace’s firmware currently supports AFP 3.2 Netatalk’s current release version is 2.1.2 which makes AFP 3.2 happen I have found a solution! (WD Engineers read this as well)Īfter Speaking with the WD Level 2 Techs yesterday I found out that that the problem with AFP not working in Mac OS 10.7 (Lion) comes down to Apple changing the AFP protocol itself.Īll Mac OS X OS’s use an software API called “netatalk” which is the software built into the OS that makes AFP happen
