Kopano File Integration not working

Hi all,

I’m using Kopano4UCS and currently I’m trying to get file integration of kopano webapp to work.
After adding smb account to settings of my account - apache logs following error and test is unsuccessfull:

path set to share$, referer: https://xyz.local/webapp/
BACKEND_SMB: Opening a nativ smb connection via libsmbclient-php, referer: https://xyz.local/webapp/
BACKEND_SMB: SMB Share openened successfully!, referer: https://xyz.local/webapp/
BACKEND_SMB: [LS] start for dir: /, referer: https://xyz.local/webapp/
BACKEND_SMB: LS failed: Icewind\SMB\Exception\TimedOutException Object\n(\n

Any suggestions?
Kopano WebApp 3.3.0.610-25.1

Seems the LS is slow, perhaps it’s connecting to a very large share.
Could you share the timestamps?

[Wed Jun 28 20:48:33.544147 2017] [:error] [pid 12395] [client :52278] [BACKEND_SMB]: Share path set to share$, referer: https://xyz.local/webapp/
[Wed Jun 28 20:48:33.560144 2017] [:error] [pid 12395] [client :52278] [BACKEND_SMB]: Opening a nativ smb connection via libsmbclient-php, referer: https://xyz.local/webapp/
[Wed Jun 28 20:48:33.599112 2017] [:error] [pid 12395] [client :52278] [BACKEND_SMB]: SMB Share openened successfully!, referer: https://xyz.local/webapp/
[Wed Jun 28 20:48:33.599153 2017] [:error] [pid 12395] [client :52278] [BACKEND_SMB]: [LS] start for dir: /, referer: https://xyz.local/webapp/
[Wed Jun 28 20:48:33.718483 2017] [:error] [pid 12395] [client :52278] [BACKEND_SMB]: LS failed: Icewind\\SMB\\Exception\\TimedOutException Object
[Wed Jun 28 20:48:33.718568 2017] [:error] [pid 12395] [client :52278] [ERROR][AccountStore] Account check failed: smb://xyz/share$/, referer: https://xyz.local/webapp/

Are you able to connect to the share and list its contents with smbclient from commandline?

Using plan smbclient results in

protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

using -mSMB2 or -mSMB3 working fine

Ok I see, that’s an explanation.

Also see https://github.com/eduardok/libsmbclient-php/issues/53

Can you enable SMBv1 on your fileserver until there is a fix for this?

In the meantime we will look into this…