[
https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823800#comment-16823800
]
Karl Wright commented on CONNECTORS-1498:
-----------------------------------------
Hi,
The following settings were suggested by Michael Allen, original developer of
Jcifs:
{code}
jcifs.smb.client.soTimeout: 150000
jcifs.smb.client.responseTimeout: 120000
jcifs.resolveOrder: LMHOSTS,DNS,WINS
jcifs.smb.client.listCount: 20
jcifs.smb.client.dfs.strictView: true
{code}
The timeout values he chose were based on the behavior of the protocol, and
were the maximum values he felt were reasonable given that. The resolve order
was chosen based on his sense of how fast each one of these is. The listCount
is also based on protocol considerations, and strictView is required for proper
functioning of the connector.
> Support SMBv2/v3 protocol for Windows Shares connector
> ------------------------------------------------------
>
> Key: CONNECTORS-1498
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1498
> Project: ManifoldCF
> Issue Type: Improvement
> Components: JCIFS connector
> Environment: OS: CentOS 7.2
> ManifoldCF: 2.8.1
> Reporter: Hiroaki Takasu
> Assignee: Karl Wright
> Priority: Major
> Fix For: ManifoldCF 2.10
>
>
> Windows Shares connector (JCIFS connector) uses
> [JCIFS|https://jcifs.samba.org/] library which supports only samba protocol
> v1.
> But many file servers were disabled SMBv1 by vulnerability
> [MS17-010|https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2017/ms17-010],
> so we can not use Windows Shares connector.
> I hope that ManifoldCF support SMBv2/v3 with other CIFS library (e.g.
> [smbj|https://github.com/hierynomus/smbj])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
