Samba in Lion and ML Server keeps disconnecting, PC InDesign crashes

Here is an update:

I came in Thursday morning and I started getting the error again. I rebooted the server the night before. I Reinstalled SMBup and it worked again. What appears to be the issue is the SAMBA server can't start on quick enough for OS X and it skips it. I don't have to restart all I have to do is, if I do restart, open up SMBup and tell it start SAMBA from the menu, BUT I have to do this twice before it actually starts. Then it will be fine until the next reboot.

Thank you for your help. My users are much happier.

ZPJET, I've got another update. I said in my last couple of post that SMBup wouldn't start Samba on restart. I found out why: Apples SMB is still running (contrary to SMBup's installation saying it would remove Apple's SMB). I went into system preferences/sharing and turned off sharing with windows computers. I restarted then and Samba started immediately without me doing anything. And the server isn't thinking near as much in SMBup.

Hi zpjet

Did the installation of SMBUp resolve you Windows InDesign Problem ?

We're having the same issue.

It solved the Indesign problem for me. I can't speak for ZPjet

Since an upgrade of a multiserversystem (MacMini SRV 10.8.3, OD Master / MacPro SRV 10.8.3 OD Replica) from 10.6 to 10.8, we suffer the same problem. The Windows clients are of Windows XP SP3 and Windows 7. Also CS 6 was upgdated to the newest Version.

And - not only Adobe Indesign has this problems. Also an application called "solidworks" suddenly can't save to the server anymore.

Also installing smbUP didn't solve the problem really. With Windows 7 it seems to work more or less (we couldn't test in depth today), but Windowx XP has access rights problems and can't save to the shares correctrly.

We also tried to change to WebDAV, but also there we have heavy problems as the windows clients most the time says the share wouldn't exist (although it does and the client could connect to it one time). But that is an other story that can be related to our selfsigned certificates on the server.

Let's hope for 10.8.4 to solve the problem 😉

There are some things around SMB-sharing with mountain lion and as I found out today, there is one reason:

"Client session timeout

It is the most common exchange timeout. This is defined in [MS-CIFS] as a system-wide parameter Client.SessionTimeoutValue. This value can be configured through the SessTimeout registry key [KB102067].

\HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\

Value type: Dword

Value name: SessTimeout

Default: 45 seconds (Windows NT)

Default: 60 seconds (Windows 2000)

(details here: http://blogs.msdn.com/b/openspecification/archive/2013/03/19/cifs-and-smb-timeou ts-in-windows.aspx)"

If you create the Dword value on the client and set the value to decimal 86400, the strange behaviour vanishes (because the timout is one day). I didn't try Indesign, but:

- viewing large PDF-files (hung up after a while)

- copying large data amounts (connection was broken after one minute and copying stopped, now it works)

- suddenly disconnected network drive

It may help you too.

I can state now that the "SessTimeout"-Value also protects against Indesign crashes. I tried it within a second environment with another server, bot OS X 10.8.3.

Sorry for mistyping the value of SessTimeout. I set it to decimal 36000. The value must be between 45 and 65535.

I wanted to thank all of you for this post!!! I run a film/video design shop. We use Adobe Creative Suite on both Macs & WIN7 machines along with a host of other applications. I am testing a new Mountain Lion Server. Well, through my testing I have run into SMB issues. I am glad that all of you have documented your issues as well. I am moving towards replacing the native SMB server with SMBup or similar. This post makes it clear the native Mountain Lion SMB server is flawed. Serious production work will require an alternative SMB server.

Thank you!

I think you can try to set the SessTimout Registry Parameter. It cleans all errors that happened (all the Adobe stuff, lost connections and so on).

But I agree that Apple has to do something with Mountain Lion server. Snow Leopard was a good product with good performance and reliability.

Hello,

I tried to implement smbup last night as we have a user on the network using Indesign on Windows 7 and large files over 100mb with links are getting this lost connection error. But smbup was not as smooth as I was expecting. Maybe others can confirm my experiance or let me know what I am misunderstanding?

1. Installing smbup was point and click.
2. Adding file shares seemed to make sense.
3. In System Preferences > Sharing > Options, I turned of Windows sharing.
4. Am I correct that you users have to be local users to make use of smbup? This seemed to be the only way to get it to work.
5. I was trying to set up 4 file shares. The first one worked but I could not get anymore to work?
6. I had set up a separate local user for my tests so I did of course have to give this user access rights to the file share in Server.app but I suspect that had the user been in a group with access it would have worked too.

Questions

1. Do I need to just share the parent folder and let the permissions be picked up after that? Can a user only connect to the one smbup share?
2. Any other tips?

Thanks

Morgs

Yes, it worked also for me, but now i have problems on logout that takes 5 minutes. If i select halt or If i remove hte key SessTimeout (with value 600 decimal) logout takes few seconds.

Did anyone had the same problem?