cancel
Showing results for 
Search instead for 
Did you mean: 

A few CIFS related problems

macros
Champ in-the-making
Champ in-the-making
Hi,

I've been evaluating Alfresco for use in our office over the last week or so and I've run into a few problems mostly related to the CIFS interface(which is the part of alfresco we are mostly interested in).  Can anyone either confirm the following as known bugs/limitations or at least point in the direction of how I would be able to fix them.

1.)  A space that was setup for versioning will create more then one version if you modify a Word document and then save it. (Unless you specifically use the check in/out functionality, changing the Office tmp directory did not help for me)
2.)  Windows Vista with service pack 1 has problems seeing an Alfresco CIFS folder when you host Alfresco on a Windows machine. (oddly it can still see a CIFS folder if the machine hosting the alfresco installation is a Linux machine)
3.)  I cannot get the CheckInOut.exe to work if I host the installation on Linux.  No matter where/how I map the drive I ALWAYS get a "Not a valid Alfresco CIFS folder".
4.)  When hosting Alfresco on an XP machine when you map a drive to \\alfrescoCM\alfresco the DesktopActions work, however mapping the drive to \\alfrescoCM\alfresco\User Homes (or anything else other then the alfresco folder) will cause the DesktopActions to fail.

I've tested the above few things with numerous different versions of Alfresco(from 2.1 all the way up to 3.0) and those issues seems to exist in all of them. 

Any help with any of the issues listed above would be greatly appreciated.

M
6 REPLIES 6

stevereiner
Champ in-the-making
Champ in-the-making
I also have problems with CIFS and Vista SP1.

CIFS worked for me with Vista 32 bit  before Vista SP1 install.

(Tried with most recent Alfresco 2.9 and 3.0 community nightly build versions installed on the Vista system)

After SP1 install, the CIFS name,  \\{hostname}A\Alfresco is still recognized, just can't login (get Incorrect password or unknown username).
Tried all kinds of config changes, can't get it to work.

Steve

pmonks
Star Contributor
Star Contributor
FWIW I see exactly the same behaviour that you describe Steve.  Alfresco seems to have been caught in the cross fire between Microsoft and Samba, yet again.   Smiley Sad

Cheers,
Peter

pmonks
Star Contributor
Star Contributor
I've just created a bug report in JIRA for this issue - it is http://issues.alfresco.com/browse/ETWOTWO-501.

If anyone has time to capture a Wireshark / tcpdump packet trace of the problem and attach it to the ticket, I'm sure that will help expedite the troubleshooting process.

Cheers,
Peter

samuel_penn
Champ in-the-making
Champ in-the-making
Not sure if this is related, but I get the some problem as point 4 in the original post when the client is Windows XP. I have tried it against both Linux and Windows server installs of Alfresco 2.2.

Basically, If I mount M: on \\server\Alfresco, then everything works okay. If I mount G: on \\server\Alfresco\Guest Home, then trying to run an action results in "Not a valid Alfresco CIFS folder".

If I try and run an action in G:\RuleTest (a space within Guest Home), then I get "No parameters for action" instead.

The shortcut link works, but CheckInOut and ShowDetails both fail.

Sam.

zomurn
Champ in-the-making
Champ in-the-making
Here is the solution :

Christopher Dakin - 04-Jul-08 08:19 AM
I found something a little strange yesterday, which I'll mention as I don't know if this'll help anyone work out why this problem exists.

I discovered that if you create a hosts file entry for hostnameA and set it to an IP address that doesn't exist on your network (e.g. 13.13.13.13) then you can suddenly connect to the share ok!

More discuss here : https://issues.alfresco.com/jira/browse/ETWOTWO-501

jefrainmx
Champ in-the-making
Champ in-the-making
That fix do not help for me.

What it helps for me is that instead of mapping to an specific folder map to the root, this is mapthe folder from Windows Explorer to  \\{localhosta}\Alfresco instead of \\{localhosta}\Alfresco\MySpace, in any case this is only a workaround.

Regards