topic Re: mapped driver in Alfresco Archive

mapped driver

andy2_0 — Mon, 30 Dec 2013 16:20:17 GMT

A quick question: "View item details from a mapped drive" thru CIMS is only available in a LAN (local area network)?Thanks!

Re: mapped driver

afaust — Thu, 02 Jan 2014 12:50:19 GMT

Hello,

do you mean CIFS, or is it a typo and you meant to talk about CMIS?
CIFS can be generally made available in LAN, WAN and potentially over the internet. BUT due to the architecture and performance/timing conditions of a WAN / Internet setup, you are very likely going to run into more or less intermittent failures, timeouts … in such a scenario. That is why CIFS is recommended to be used only in LAN or internal corporate WANs of sufficient quality.
CMIS can be used in any networking environment that supports HTTP.

Regards
Axel

Re: mapped driver

andy2_0 — Fri, 03 Jan 2014 03:27:12 GMT

Hi Axel, thanks for your reply.

I mean CIFS. sorry for the typo.
From the response, CIFS can be used in WAN as well. Currently My alfresco Server is hosted in an IDC, I access it from office thru Internet.
The environment is: CentOS 6.3 b4bit, Alfresco Community Edition 4.2.e.
My configuration file about CIFS is as below, I am not sure with the following three settings. All the three are for my office PC's setting. Would you please help review? Thanks!

—————————————–
cifs.domain=WORKGROUP
cifs.broadcast=192.168.0.255
cifs.bindto=192.168.0.85
———————————————

### CIFS settings in alfresco-global.properties ###

### File System ###
### CIFS Server Configuration ###
cifs.platforms=linux,solaris,macosx

# The tcpipSMB and netBIOSSMB beans have a platforms property that allow their configuration to be targeted to Alfresco servers running on specific platforms. The property is formatted as a comma-separated list of platform IDs. Valid platform IDs are windows, linux, solaris, macosx and aix.

cifs.enabled=true
cifs.serverName=${localname}A
cifs.domain=WORKGROUP
cifs.broadcast=192.168.0.255

# An empty value indicates bind to all available network adapters
cifs.bindto=192.168.0.85
cifs.ipv6.enabled=true
cifs.hostannounce=true
cifs.pseudoFiles.enabled=false

#controls whether URL shortcuts or desktop actions are displayed on CIFS.
cifs.pseudoFiles.explorerURL.enabled=false

#Is the URL shortcut for alfresco explorer shown ?
#cifs.pseudoFiles.explorerURL.fileName=__Alfresco.url
#Name of Cifs URL for alfresco explorer

#cifs.pseudoFiles.shareURL.enabled=false
# Enable the use of asynchronous sockets/NIO code
cifs.disableNIO=false

# Disable the use of JNI code. Only currently affects Windows
cifs.disableNativeCode=false

# Session timeout, in seconds. Defaults to 15 minutes i.e. 900 seconds, to match the default Windows client setting. Maximum is 3600.
# If no I/O is received within that time the session is closed by the server
cifs.sessionTimeout=3600
cifs.WINS.autoDetectEnabled=true
cifs.sessionDebug=false

# Can be mapped to non-privileged ports, then use firewall rules to forward requests from the standard ports
cifs.tcpipSMB.port=1445
cifs.netBIOSSMB.sessionPort=1139
cifs.netBIOSSMB.namePort=1137
cifs.netBIOSSMB.datagramPort=1138

Re: mapped driver

afaust — Sun, 05 Jan 2014 12:20:45 GMT

Hello,

the most important of these three properties is the bindTo, which determines the network interface (if any) that CIFS will be listening on. I usually leave this empty to have CIFS listen on all available network adapters. If it is set to a specific IP value and no network adapter on the Alfresco server is assigned that IP, than CIFS will NOT listen on any interface and can not be used.
I never use or take much care of the broadcast / domain settings as in our customers environment the "host announcement" feature is not relevant and usually disabled. When you access Alfresco CIFS directly via a known IP or DNS name, these two settings are pretty much irrelevant.

Seeing that you have used ports 1137, 1138, 1139 and 1445 in the configuration, have you made sure that NAT rules are in place using iptables or other NAT services to redirect the CIFS ports 137,138,139 and 445 to the respective ports Alfresco CIFS is listening on?

If you want to use the ability to view item details on CIFS, you need to enable the Alfresco pseudo files, otherwise you won't be presented with the actions to open the item details from the shared drive. Set cifs.pseudoFiles.enabled=true to enable this. Depending on which client you are using (Share vs. Explorer) you may also want to activate the specific URL pseudo file and potentially wire up a different JavaScript file for the __ShowDetails.exe (this will have to be configured in Spring XML, not in alfresco-global.properties).

See <a href="http://wiki.alfresco.com/wiki/File_Server_Subsystem_4.0#Configuration">File Server Configuration</a> and <a href="http://wiki.alfresco.com/wiki/File_Server_Subsystem_4.0#Desktop_Actions">Desktop Actions</a>

Regards
Axel