Clients running 10.8.5 unable to connect to FileShare

Question

Level 1

0 points

Clients running 10.8.5 unable to connect to FileShare

I have 8 clients running OS X 10.8.5 connecting to a server running OS X 10.10.5 which is running Server 4.1.5. They are unable to connect to the server. When they try it shows that they are connected (on the client machine and on the server) but the folder listed is there home folder. The home folder is not setup as a share but appears this way. When logging into the file share with an account other than the user that is currently logged into the client machine it shows the new account's home folder which is not on the machine. See screenshot below.

I do not have this issue on the 10.9.5 or the 10.10.5 clients. Is this a bug or is Apple not supporting 10.8.5 anymore?

Posted on Sep 1, 2015 1:08 PM

Reply

Answer 1

Sep 1, 2015 3:29 PM in response to GraceAdmin15

the default for Sharing in later versions is SMB. Be sure the Share Point is also shared over [√] AFP in this pane of File Sharing in Server.app. (These are my User Shares and Volume-names, yours will vary.)

.

Reply

Answer 2

GraceAdmin15 Author

Level 1

0 points

Sep 1, 2015 4:30 PM in response to Grant Bennet-Alder

Thanks for the reply. Your settings look exactly the same as my settings. So I am not sure what else it could be.

Reply

Answer 3

Sep 1, 2015 5:17 PM in response to GraceAdmin15

If you want to go down the "laundry list"...

On those workstations, can you "Lookup" (using Network Utility) the fully qualified domain-name and its reverse?

[If you can't find Network Utility.app it is available at:

/System/Library/CoreServices/Applications/Network Utility.app

Reply

Answer 4

UptimeJeff

Level 4

3,479 points

Sep 1, 2015 8:18 PM in response to GraceAdmin15

There are a number of settings not available in the GUI which you should explore.

From Terminal:

sudo serveradmin settings afp

sudo serveradmin settings smb

sudo sharing -l

Unshare all of the personal folders shared.

They were likely created due to this default:

serveradmin settings afp:createHomeDir = yes

to check the setting:

sudo serveradmin settings afp:createHomeDir

to change it

sudo serveradmin settings afp:createHomeDir=no

You need to stop/start AFP for this change to take effect.

------

AFP and SMB connections may behabe different.

its best to be explicitly connect with AFP or SMB so you know can compare.

command-k from finder

afp://10.0.0.2

smb://10.0.0.2

change the IP to match your server LAN IP

-----

hope that helps

Reply

Answer 5

GraceAdmin15 Author

Level 1

0 points

Sep 2, 2015 1:55 PM in response to UptimeJeff

That did it. For whatever reason setting the afp:createHomeDir to no solved the problem. Thanks for you help on this.

Related: Where can I go to learn more about the hidden commands in Mac Server?

Reply

Answer 6

UptimeJeff

Level 4

3,479 points

Sep 4, 2015 7:23 AM in response to GraceAdmin15

# view all the commands with

sudo serveradmin settings afp

Here's a good guide

http://krypted.com/mac-security/missing-server-app-settings-for-afp

I use this group of settinngs often.

afp:reconnectTTLInMin = 10

afp:clientSleepOnOff = yes

afp:clientSleepTime = 10

afp:idleDisconnectOnOff = "On"

afp:idleDisconnectTime = 24

afp:idleDisconnectMsg = "Idle users are disconnected from the server"

afp:idleDisconnectFlag:adminUsers = yes

afp:idleDisconnectFlag:registeredUsers = yes

afp:idleDisconnectFlag:usersWithOpenFiles = yes

afp:createHomeDir = no

Reply