SMB Sharing OS X Server - Session Timeout after 60 seconds

Question

PeerMahn Author

Level 1

24 points

SMB Sharing OS X Server - Session Timeout after 60 seconds

The behaviour is reproduceable:

- Install OS X Server (tried with 10.8.3, 10.8.4, 10.8.5)

- Set up DNS and filesharing

- add a user (local or OD)

- connect from a Windows system via SMB/CIFS

- copy a bunch of files where you know that it lasts more than a minute to copy the files to the server

- after 60 seconds you get a message "filexy cannot be copied. The specified network name is no longer available" and copying stops

Other misbehaviour: You can't save Adobe Indesign files you opened a while, PDF-files cannot be read after a while and so on.

Workaround: Edit the registry at the Windows client an add the following DWORD value to HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

"SessTimeout" an set an decimal value of "36000".

Then you can copy and work fine.

But: you can't do the following thing with your windows client: Delete folders with subfolders. All the subfolders and other content will be deleted but the root folder cant't be deleted. You have to wait 10 hours (36000 seconds) according to the registry value you set.

Is there anybody who found another way to solve the problem?

I found this behaviour and the workaround working with several installations (Mac mini servers) and I can reproduce it with my MacBoo Pro and a virtual Windows XP Pro/ Windows 7 Pro within Parallels Desktop.

OS X Server-OTHER, OS X Mountain Lion (10.8.5), SMB Filesharing

Posted on Sep 18, 2013 1:51 AM

Reply

Answer 1

Sep 18, 2013 4:45 AM in response to PeerMahn

Exactly. I can only say that i have exactly the same big problem.😟

Reply

Answer 2

haykong

Level 1

119 points

Sep 20, 2013 7:58 AM in response to PeerMahn

Yeah It's a HUGE problem and I can't believe Apple let that slide for a few years now since they converted to LION Server..

Yeah for now I use SMBup 1.4.1 and macports samba 3.6.16 and all is fine.,,,, bu I have to manage two user sets. I wish the guy who did the macports samba had the make file compile it to use LDAP.

Now I'm itching for Mavericks server and hoping they did a rewrite of SMB2.

Reply

Answer 3

Oct 4, 2013 1:52 AM in response to haykong

The MacPorts edition of Samba v3.6.16 has variants for OpenLDAP and Kerberos - simple do:

sudo port install samba3 +openldap

if you want to use LDAP (you can only activate variants after installing the main package).

View the MacPorts samba3 portfile at https://trac.macports.org/browser/trunk/dports/net/samba3/Portfile .

Reply

Answer 4

Dec 4, 2013 7:34 AM in response to Victor Pang

I have a small office with windows 7 clients sharing off a new 10.8.5 server. We have been experiencing the same problems with disconnections, large pdfs crashing, etc. I have created the SessTimeout entry with a decimal value of 36000 which has fixed some of the issues with the pdfs crashing but I'm now seeing new errors. When someone tries to hit the back button in their explorer, they get "An error occurred while reconnecting to F: to \\computername\shared folder Microsoft Windows Network: The local device name is already in use. This connection has not been restored." message. They can then close the window, reopen explorer and then renavigate to the folder but this can be time consuming every time. Also, Windows clients are no longer able to delete pdf and other files from the server. They will delete them but the files will just reappear after a minute or two.

Is anyone else seeing behavior like this after changing the timeout parameters? If so, is there a tweak that can address this?

Or should I consider moving SMBUp which should hopefully fix all these things or will they? Or does anyone have experience with Mavericks server and is there a new implemenation of SMB that works better than ML Server?

Everything worked great with Snow Leopard Server. Sigh. Any insight or suggestions is always greatly appreciated.

Reply