AnsweredAssumed Answered

CIFS fails with newer windows clients

Question asked by mvba on Mar 25, 2011
CIFS fails on the windows client.

1. if NIO is used, port 138/udp is not listening and nothing happens after SPNEGO
2. if NIO is disabled, the CIFS share is visible, but the folder is empty. and you cannot put a file  in it.
3. host announce doesn't work in both setups, i checked with wireshark, no such broadcasts are being sent out

http://imagebin.org/144844 with NIO
http://imagebin.org/144845 without NIO

after digging a bit deeper with wireshark, it seems that:
-  the windows 7 client gets info on /srvsvc then closes the file and starts transfer, which fails because the file is closed, (see wireshark attachment).

using:
- win 2008 R2 AD with kerberos domain
- win 7 client
- linux alfresco 3.4.c

config:
kerberos.authentication.realm=ALFRESCO.BA.BE
kerberos.authentication.sso.enabled=true
kerberos.authentication.authenticateCIFS=true
cifs.localname=Alfresco
cifs.serverName=Alfresco
cifs.domain=ALFRESCO
cifs.bindto=172.16.1.122
cifs.ipv6=disabled
cifs.broadcast=172.16.1.255
cifs.announce=true
cifs.disableNIO=false
cifs.hostannounce=true
cifs.WINS.autoDetect=true
cifs.WINS.primary=172.16.1.112
filesystem.name=Documenten

Outcomes