Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

5 points

Lion: Connecting to legacy (pre-Lion) AFP services - and Mac OS X (server)

After upgrading to MacOS X Lion, it was discovered that it was not possible to logon to Novell-shares and NAS-boxes (e.g. Qnap).

Here is a recipe that has been tested OK with the following combinations:

* Mac OS X Lion -> Novell shares

* Mac OS X Lion -> Mac OS X 10.5 server

* Mac OS X Lion -> Mac OS X Lion

Please note that the command-lines themselves must not have CR/NL-characters. Copy the commands to a text-editor and remove format-inserted CR/NL-characters.

Another note: Your logon will be less secure with these changes. Later when e.g. Novell and/or your NAS-box support native Lion-logon, then please remove the AppleShareClient-parameter changes again with the first block.

Recipe:

The following block can be skipped if you have not previously changed AppleShareClient-parameters:

sudo -s

chmod o+w /Library/Preferences

cd /Library/Preferences/

rm com.apple.AppleShareClient.plist*

! Restart

The following block makes it possible to logon to: (1) Novell-shares (2) Pre Lion Mac-OS-X-volumes - and possibly non-native Lion logon NAS-shares:

sudo -s

chmod o+w /Library/Preferences

defaults write /Library/Preferences/com.apple.AppleShareClient afp_host_prefs_version -int 1

! Restart

You now have to logon a real account (non-guest) on another Mac OS X Lion volume

to catalyst a creation of AppleShareClient-files. (See Apple-support-link) (Is this necessary?)

! instead?:

/bin/sleep 60

chmod o+w /Library/Preferences

defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "Cleartxt Passwrd" "MS2.0" "2-Way Randnum exchange"

defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "DHX2"

defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "DHCAST128"

chmod o-w /Library/Preferences

PS:

Possibly all volume-links may be deletes and recreated to use the new logon-parameters?

Sources for command-bricks:

OS X Lion: Connecting to legacy AFP services:

http://support.apple.com/kb/HT4700

AFP changes in OSX Lion:

http://www.novell.com/communities/node/13155/afp-changes-osx-lion

AFP support for DHX2 authentication mechanism on OES:

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7008 683&sliceId=1&docTypeID=DT_TID_1_1

"/bin/sleep 60":

Making My NAS Work in Lion:

http://krypted.com/mac-os-x/making-my-nas-work-in-lion/

Example:

bash-3.2# chmod o+w /Library/Preferences

bash-3.2# cd /Library/Preferences/

bash-3.2# rm /Library/Preferences/com.apple.AppleShareClient.plist*

bash-3.2# chmod o-w /Library/Preferences

bash-3.2#

! Restart

Last login: Fri Aug 12 14:41:58 on console

$ sudo -s

Password:

bash-3.2# chmod o+w /Library/Preferences

bash-3.2# defaults read /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams

2011-08-12 14:42:31.172 defaults[188:707]

The domain/default pair of (com.apple.AppleShareClient, afp_disabled_uams) does not exist

bash-3.2#

! Restart

Last login: Fri Aug 12 14:47:31 on console

$ sudo -s

Password:

bash-3.2# chmod o+w /Library/Preferences

bash-3.2# defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "Cleartxt Passwrd" "MS2.0" "2-Way Randnum exchange"

bash-3.2# defaults read /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams(

"Cleartxt Passwrd",

"MS2.0",

"2-Way Randnum exchange"

)

bash-3.2# defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "DHX2"

bash-3.2# defaults read /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams

(

DHX2

)

bash-3.2# defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "DHCAST128"

bash-3.2# defaults read /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams

(

DHCAST128

)

bash-3.2# chmod o-w /Library/Preferences

bash-3.2#

Also posted here:

Lion: Connecting to legacy (pre-Lion) AFP services - and Mac OS X (server):

http://forum.qnap.com/viewtopic.php?f=30&t=48143

http://forums.macrumors.com/showthread.php?p=13166617

Mac OS X (10.7)

Posted on Aug 12, 2011 1:36 PM

46 replies

Craig Best

Level 4

1,166 points

Jun 5, 2012 6:07 PM in response to Superfly-SP

Problem is even if you buy a new NAS what guarantee is there is will work with Lion or Mountain Lion?

For me my NAS is part of my router which is only 6 months old so sould be up-to-date. I think the best option is just to connect the HDD up to the PC and share it from there but put another internal HDD in the PC and use it.

I do feel for those who have a NAS for backing up and can no longer access that network drive.

BTW I'm not going to dig around in my command line and stuff something up. The whole point of Mac and OS X is it's meant to be easier to use. Surely there is a simple solution Apple could provide or 3rd parties need to step up there game and provied firmware updates.

Jun 18, 2012 5:00 AM in response to Craig Best

Has there been any Apple input on this forum? I would like to know that this is going to be fixed in Mountain Lion. I don't see any indication that Apple even acknowledges that they caused this problem. How about some Apple help here?

Jul 21, 2012 9:31 PM in response to BobbieMac

hello APPLE ????? anyone there?

Craig Best

Level 4

1,166 points

Jul 22, 2012 6:41 AM in response to BobbieMac

I'll just wait and see if Mountain Lion fixes things, in the mean time I've moved the HDD plugged into the router and it will now be another USB drive plugged into the new iMac... when Apple releases it LOL

Jul 22, 2012 12:55 PM in response to Craig Best

Craig

This isn't something that Apple are likely to "fix" as it was an intentional change.

Apple no longer wish to support legacy file sharing protocols as they are "insecure" compared to what is now currently available.

I spent hours on the phone to Apple, it is something that their own engineers are frustrated with but, as I say very unlikely to change and they haven't formally acknowledged people are p***ed off with it.

Unfortunately, the only option I found was to upgrade my NAS to one that is "Apple compatible" - that is until their next upgrade! 🙂

All the best,

Craig Best

Level 4

1,166 points

Jul 22, 2012 3:23 PM in response to Ken Clarke

I get that Apple probably won't 'fix' it which is a shame as I have a near new router which I was using as a NAS but hooking up a USB HDD, unfortunately it wasn't working with Lion and I got it less than a year ago, after Lion was released, it should be compatible.

Right now my only network HDDs are inside a WinXP PC which is much older, all other drives (4x 2Tb) are running off my Mac and will hook right up to my new iMac.

Jul 23, 2012 5:41 AM in response to Craig Best

ended up at buying an new NAS... that is frustrating enough.. but the time it took to figure out because Apple doenst mention it anywhere... annoying

Aug 24, 2012 1:38 PM in response to Superfly-SP

That's the point: Apple did not mention it CLEARLY before!

It's a shame. Thousands of people own older NAS (me too) and I earn my money supporting those NAS.

What do you think my customers will say if I tell them: "I cannot support your hardware. Buy a new one."

I'll restore my system back to Snow Leopard. It's too bad about the money. Not for the ML App but all the other software upgrades with costs.

Craig Best

Level 4

1,166 points

Aug 24, 2012 3:39 PM in response to t-bird.de

I was wondering does anyone make a USB NAS hub? something you could take any USB ext HDD hook them up and share them over a network. Idealy it would have say 4 USB ports for 4 HDDs

If I get a NAS it will be after I get my new iMac and make sure it works with ML.

Aug 24, 2012 6:14 PM in response to Craig Best

So the big news is that Apple's Genius Bar says simply,"Time Machine won't always work over a network." Pressed for more detail, I could only get "if you want Time Machine to work, attach a hard drive with USB or Firewire." Basically that has been my problem. I can see the disk drives on my Mac Mini server (which is running Mountain Lion Server) from my Macs running Mountain Lion. Can read and write as appropriate, but Time Machine doesn't work.

I have downloaded, but not configured, an app called "Carbon Copy Cloner" which seems to work-at least it finds the network drives which is more than Time Machine does. More when I have it working completely. I will say that the download is free for the first 30 days, so you get a chance to use it before paying.

My conclusions:

1) TIme Machine DOESN'T work over a network. I wasted many hours trying to get it running reliably.

2) Apple has not been willing to deal with the network issues introduced by the recent OS upgrades. We need to hold their feet to the fire in every possible way.

Craig Best

Level 4

1,166 points

Aug 24, 2012 10:07 PM in response to BobbieMac

I've used CCC for years with a FW HDD and it works great, a few months back I needed to repair a problem with my main HDD so just booted off the backup and it worked great, fixed the minor problem and booted back to my normal HDD.

I looked at getting Apple Time Capsule but decided to just get another (bigger) FW HDD from my next iMac, I will however be switching to Time Machine. I'm also considering periodic CCC backups to a 2nd HDD, once a week. After a scare a few years back I say you can't have too many backups!

Aug 25, 2012 1:29 AM in response to BobbieMac

BobbieMac

You can't say it "DOESN'T" work over a network when it clearly does.

I've had Time Machine running over USB for years and over a network for a couple more. The only issue I ever encountered was the support for my old NAS when upgrading to Lion ( as posted earlier in this discussion ).

Please stick to the facts as comments like that do not help newcomers troubleshoot problems

Aug 25, 2012 8:18 AM in response to Ken Clarke

You probably should reread what I said and which was a pretty accurate quote of the Genius Bar guy. I said that the Genius Bar said, "Time Machine doesn't always work over a network." For me it was a very important statement because it stopped me wasting time on Time Machine and got me looking at other back-up solutions. The other solutions appear to work and I'll report when I am sure that they do.

When Time Machine did work, and it did for brief periods, it was extremely slow after Lion. There is still some issue in the network protocols(?) that seem to cause very slow performance across the network. I will be looking to see if this is also a Time Machine problems or whether it is indeed mainly in Time Machine.

Sep 28, 2012 8:47 AM in response to glenndk

I am sorry, I am a late comer to this conversation. I am willing to give the Unix commands in Terminal a try, but I am confused which script to use. I tend to go for the one that Apple suggests, but some lines appear to be clipped, and I am not sure what they should read (-array) (-arrays) ?

http://support.apple.com/kb/HT4700?viewlocale=en_US&locale=en_US

On the other hand this looks much simpler:

http://krypted.com/mac-os-x/making-my-nas-work-in-lion/

Any suggestions?

Thanks,

Klaus

Apr 21, 2013 11:53 PM in response to glenndk

I've used the description in http://support.apple.com/kb/HT4700 with luck on new OS 10.7 / 10.8 Macs, but it fails miserably on our older upgraded Mac Pros (upgraded from 10.6.8). The appleshareclient plist file is for some reason not filled in when I try to make an AFP connection (no matter how many reboots I perform).

The solution for me was to just copy over a working appleshareclient plist from one of our new Macs.

Lion: Connecting to legacy (pre-Lion) AFP services - and Mac OS X (server)