Server 3, 2nd user to log in creates a folder called "Networ" and has no access to home folder

I have this exact same issue. Things worked fine prior to Mavericks upgrade. I'd like to try logging into Server 3.0 with a mountain lion client as i'm not sure it's server issue but a client issue. I logged into a machine with "user a" (on the graphical screen). I also logged into the machine via ssh with an admin account. After logging out with "user a" I noticed that the "user a" auto mount home directories are still mounted. So, why aren't the home directories dismounting? Just like you, user b get the home directory unavailible error.

Similarly, on reboot, all works well for user b.

I'm using SMB to share - it appears to work fine. Either AFP or SMB gives me the same results. Some folks have suggested forcing cifs.

I've seen the AFP users showing up as connected for a long time now even though things were working fine (when I was using ML server and lion clients - just a month ago). My understanding is the AFP connections showing up in file sharing is a record - not an active connection - which I dont understnad because if I reboot a machine it goes away and it also indicates idle time. crazy.

I do have one user actually using the mail app (everyone else uses gmail) and mail will not remember his password.

I'm still using WGM to manage all of my clients - but I haven't added any new. I guess I will refrain from doing so.

I think for now since several of us have dupped the problem and apple marks the case as duplicate; we all hurry up and wait for a mavericks client update....For now, I just tell my users instead of clicking logout, click reboot when they leave the room, then it's ready for the next teacher to login. Seems to be a fine workaround so far....

Not sure if you are still having this issue but I have been suffering from it for about 4 months and thanks to a very helpful person at Apple we have finally identified what causes this to happen.

Basically it is the location of your network users home folders. When you place these in the server/Users directory this behaviour occurs. If you setup a new directory e.g. server/network homes and create the users home directory in there everything works.

You can migrate existing network users by:

1) create a new shared folder

2) make it available for home directories over AFP

3) login as root

4) copy the network user directories from server/users to server/network homes

5) edit the user record within the server app to tell them where their home directory now is

Note I left any local users (including guest) within the server/users folder. i.e. only move network users

Hope this helps someone.

This helped - but I actually determined that (maybe as implied by you) the problem still exists when sharing via SMB. If you change the shares to AFP it begins working. In other words, performing the steps above if you were sharing home folders via SMB - problem still present. Performing steps and changing shares to AFP - problem goes away.

I dont know how to mark this as "this solved my problem."

That;s a bit strange. I switched mine over to using SMB and it still worked. However I had updated to 10.9.2 before doing so.

CCSchool wrote:

I dont know how to mark this as "this solved my problem."

I am guessing that only the person who first logged the question can do this.

We ran into this same problem and figured it out!

Turns out Mavericks is not disconnecting the network account after logout. In our case we have a Synology NAS where all user accounts are stored and you can see that the user is still connected after logout. This then causes a problem for any other network account user who tries to login after. I created a logout hook that disconnects the network volume.

sudo umount -f /Network/IPofServer/NetworkVolumeName

Hopefully this helps some other IT admins!