Users not disconnected from file sharing

Same problem here. Got a 10.8.5 File Server and 60 mac OSX client, only 3 of them are 10.9.1 all other are 10.8.5 and only those 10.9.1 causing this 100 connexion open on the file server, and some time they making my file serveur hanging, need to stop afp and start afp to fix the issue. Really looking for a fix or workaround.

Thanks !

I have same problem. 6 Xserves running 10.9.1. For info, you can configure AFP via command line to enable the disconnect idle users functionality. However this is hit and miss and at the time of writing this, it is after ten o clock, the building has been shut for five hours and there are still over 40 users connected to my file share. This is after setting the idle disconnect to 120 mins. I so expect this of Apple these days.

Update:

Just to report, 10.9.2 and Server 3.0.3 didn't fix my issue of AFP/SMB users not being disconnected properly. I have found that making users (or forcing them) to shut down thier machines at night does indeed disconnect them in server. Also, I had the server re-starting every night automatically.

If they put thier machines to sleep instead of shutting down, server keeps the connection "alive" showing they are connected. When they come in the next day, it adds another connection for thier account. IPs are the same, and machine are the same. Eventually, between all the times of the day and then at night that their computers sleep, they can end up with 5 or more connections.

I am going to change the idle time and disconnect idle in terminal as my next attempt to fix. I will report back.

No luck with the discconnect idle users setting.

I previously turned it on and set it to 300 minutes in terminal.

My next move is to change the sleep hours from 24 to 12. I know a while back in 10.6 Admin docs it mentioned that sleeping users won't show as idle (which I think is dumb). It makes me think that sleeping users aren't considred idle, and during the default 24 hour period, would show connected beyond the set 5 hours for idle disconnect time.

Hopefully this works to at least disconnect the users overnight so that they don't show as being connected multiple times and begin to have issues.

As stated before, this is hit and miss. I have also configured clients not to sleep and this makes no difference most of the time. You may be chasing your tail if this is a bug Apple have not come clean about but obviously know about. Server app v3.1 is due imminently which is a major update, unlike the one just released. I would continue to disconnect them manually on an evening and maybe wait for the update.. ?

I agree with your comments as 10.9.2 and Server 3.03 hasnt changed a thing as I have updated all my clients and server to 10.9.2.

I have tried all the sleep, various "tickle" times via terminal, Workgroup manager settings but there is something basically flawed with the AFP at present. I looked this morning and 60 users are still connected from last Friday. I did report this as a bug with apple but it was flagged as a duplicate so maybe its being investigated etc. I hope the Server 3.1 version fixes things as you say.

Confirmed here as well. Strangely, I find on client computers that the server is named differently for each succesful login:

Server . . . . Server-1 . . . . Server-2

This has wreaked havoc working on Adobe Indesign and Photoshop files off our servers. When a new connection is established and the server path changes, Indesign and Photoshop crash. The recover file is locked and unable to resolve.

Same here as well. I can also confirm that Adobe Indesign and other Adobe apps do not like this at all. Really messing up our workflow. Calls into question the stability and dependability of the files and backups we rely on.

Apple, please address this issue.

I'm having the exact same problem. I have a fresh install of Mavericks server and an iMac client running the latest version of Mavericks as well.

When the network user logs out on the client the file sharing connection remains. Rebooting the client drops the connection. For some reason the client is keeping the connection alive after logout. Looks more like a client issue to me, not a server issue.

I was experimenting yesterday and exactly as you say the client drops the active connection once you restart the client. I had 20 persistent network user connections(AFP) from the day before this morning when I checked. All disappeared on restart via ARD. I notice that if a network user accesses a sharepoint or group folder whilst logged in that connection is terminated as the user logs out but the users file sharing remains connected.

I have been offered Server 3.1 as a preview via our Developer account to see if this pre release fixes any of the issues. I will report back if I find any fixes unless of course v3.1 is officially released beforehand which I understand is quite soon.

Well, I destroyed my open directory, deleted my Network Users home folders and started over.

This time I used AFP and turned off all SMB sharing features.

My iMac client is now able to login and out of all the Network Users accounts without any trouble. The last AFP connection still remains active after the Network User logs out however.

When another Network User logs in the old connection is dropped.

We moved to Windows Server 2012 and OS X 10.9.1 clients and the Windows servers also get full over users still connected even though the client is at login window. Causes all sorts of problems with oppurtunistic locking as the open files are locked for writing such as keychain and caches.

This makes me think this is a mavericks client not disconnecting issue, rather than a server issue.

I WAS having this problem, but no longer. I wish I could tell you what I did to fix it, because it was a frustrating problem.

I can tell you this:

My router provides DNS

I setup DNS on the server anyway b/c it seems to make it happier

I purchased a Rapid SSL cert for my server to use for OD

I erased the volume I use for Network Homes and setup file sharing over again on it.

I am using SMB for all file sharing including Network Homes

I ****suspect**** that the issue was related to permissions on the users folders.

I am still having the same issue as everyone is, I have my users home folder on a pegasus external drive, i also created network homes on the servers internal drive as a test and keeps having same issue.

I am lost what could be causing this issue, does not seem to me that it is permissions issue from the test that I did creating home folders on server.

Server app update 3.1 did not fix the issue for me.