topic Re: Users on Win Terminal Server 2008 R2 losts the access to Alfresco 4.0 CIFS server in Alfresco Archive

Users on Win Terminal Server 2008 R2 losts the access to Alfresco 4.0 CIFS server

icarrara — Tue, 28 Jan 2014 14:20:08 GMT

I have 30 users on a Terminal Server Windows 2008 R2 named \\NT05.I have Alfresco 4.0 Community installed on another Windows 2008 R2 named \\DOC with CIFS server activated, with the below properties:cifs.disableNativeCode=truecifs.maximumVirtualCircuitsPerSession=96All it is ok for stand-alone clien

Re: Users on Win Terminal Server 2008 R2 losts the access to Alfresco 4.0 CIFS server

afaust — Thu, 30 Jan 2014 10:58:33 GMT

Hello,

we have had customers with similar issues running Alfresco on Windows Server and using CIFS for more than just a hand full of users. Almost always the root of the problem could be found in some part of the native Windows handling of SMB/CIFS (i.e. some internal table for TCP handles overflowed, VC#0 issues…).

My personal advice: Do not use the native CIFS code, configure Alfresco to use Java Sockets for CIFS instead. As far as I can remember, cifs.disabledNativeCode=true (which you have already used) has no real effect on Windows unless you do a bit more extensive reconfiguration.
There was an attempt to get this documented in https://issues.alfresco.com/jira/browse/MNT-3494 but since Alfresco does not test this scenario, it is <b>officially not supported</b>. But it works better / more stable than native CIFS for all our customers while we continue to try to convince them to switch to a real server operating system.

Regards
Axel

Re: Users on Win Terminal Server 2008 R2 losts the access to Alfresco 4.0 CIFS server

sysadmin2012 — Tue, 29 Apr 2014 08:00:45 GMT

Hi icarrara,
Just wanted to share some insight i got after weeks of trial and error. We fixed this issue by adding a DNS-wildcard (Ex *.alfresco-cifs) in our internal DNS-server.

So when our terminal server users using Windows Server 2008 R2 Server loggs in we run "netuse Q: \\%username%.alfresco-cifs\Alfresco".

This seems to force Windows to always start a new session for every user and have fixed our "Access denied" problems.

A new problem have arose from this fix and that one you can read about here: https://issues.alfresco.com/jira/browse/JLAN-147

To fix that problem you have to do some coding and build your own alfresco-jlan-embed.

Regards
sysadmin2012