nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

CIF AD SMBException invalid parameter

mstransky

Hello,
Im unable to get working CIF integration on AD.
I have passthru (and LDAP) setting correct, I belive, and I am able to login to 8080\alresco and 8080\share
when Iam trying to connect on CIF ERROR reports:
ERROR [smb.protocol.auth] org.alfresco.jlan.smb.SMBException: Invalid parameter

can anyone help me??
this is my passthru

passthru.authentication.sso.enabled=flase
passthru.authentication.useLocalServer=false
passthru.authentication.domain=
# (domain specific property): NetBIOS name of your domain and
# domain controller.s IP address, add more separated by commas
#passthru.authentication.servers=DOMAIN\\192.168.0.1,192.168.0.1
passthru.authentication.servers=intra\\xx.xx.xx.xx,xx.xx.xx.xx

passthru.authentication.guestAccess=false
passthru.authentication.defaultAdministratorUserNames=administrator,Administrator 
passthru.authentication.connectTimeout=5000
passthru.authentication.offlineCheckInterval=300
passthru.authentication.protocolOrder=TCPIP,,NETBIOS

ntlm.authentication.sso.enabled=false
alfresco.authentication.allowGuestLogin=false
ntlm.authentication.mapUnknownUserToGuest=false
passthru.authentication.authenticateCIFS=true
passthru.authentication.authenticateFTP=false
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

and this is my alfresco-globals

# Authenticaton AD
#————————–
#authentication.chain=passthru1:passthru,ldap-ad1:ldap-ad
authentication.chain=passthru1:passthru


# Doamin mapping
#————-
filesystem.domainMappings=intra
filesystem.domainMappings.value.intra.subnet=192.168.2.0
filesystem.domainMappings.value.intra.mask=192.168.2.255
‍‍‍‍‍‍‍‍‍‍‍‍‍

my ldap sync works well so I think there is no problem in it

here is my fileServer subsystem default default seting

cifs.enabled=true
# (domain specific property): change to match alfresco hostname + ‘A’
cifs.serverName=dmsA
#cifs.serverName=192.168.2.142
#cifs.serverName=${localname}


# (domain specific property): NetBIOS domain name
cifs.domain=intra
cifs.hostannounce=true
cifs.sessionTimeout=900
# (domain specific property): network broadcast address
cifs.broadcast=192.168.2.255
#cifs.broadcast=255.255.255.0
#cifs.tcpipSMB.port=1445
#cifs.ipv6.enabled=false
#cifs.nerBIOSSMB.namePort=1137
#cifs.nerBIOSSMB.datagramPort=1138
#cifs.nerBIOSSMB.sessionPort=1139

# (domain specific property): change to match alfresco hostname
#cifs.urlfile.prefix=http://hostname:8080/alfresco/ 
cifs.urlfile.prefix=http://192.168.2.142:8080/alfresco/ 
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

please can anyone show me what to do to make CIF running

conf: alfresco Version :Community - v3.3.0 (2765)
server: ubuntu 10.1
DB: PosgreSQL

Find more posts tagged with

Comments

mstransky

Seams We found solution…

Control Panel - Administrative Tools Double - Local Security Policy
Local Policy - Security Options - then for Network security: LAN manager - authentication level - Send LM & NTLM

jzaruba

I wonder if there's an alternate way of achieving CIFS+AD working together. I'm not sure it is acceptable to force users to play with secpol.msc on their client for this feature to work… and, more importantly, to force them to use attack prone protocol.
Were you able to find any other solution, or were you just OK with setting the NTLM to negotiate?

quilesg

Hey Guys,

At my current site we are using Alfresco 3.4d community edition. The issue which took place was that we were unable to login properly from the Alfresco plugin in Moodle. It turned out that this particular error was a result of the clock being off on the Moodle server. The clock on Moodle was roughly six and a half minutes behind the Alfresco server (which was the real time). The moment that we updated the clock on the Moodle server it started working again.