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.

CIFS bug?

pcmonk

I ran into an odd thing today. I am testing ver 3 final. I was testing permissions on CIFS folders. I would disconnect my CIFS drive share on my PC and then go into the Web Client via the Alfresco PC, change my role and then re-create the CIFS share on my PC to test. On the 3rd or 4th cycle I was un-able to re-create the share on my PC. It said the path to \\AlfrescoA\\alfresco could not be found. After I restarted my PC (not alfresco) it worked again. Could there my issues with the CIFS protocol?

Also why do I need to add an A to the host name to get access to CIFS?

Find more posts tagged with

Comments

nadaoneal

Hi pcmonk, I just asked the same question the other day, and got this response:

The name of Alfresco's filesystem needs to be different from the filesystem exposed by windows.

Someone in the depths of time came up with a simple solution which is to call the Alfresco file system <hostname>_A to make it different. More recently the underscore disappeared and it became <hostname>A.

You can change your Alfresco file system configuration to name your drive whatever you want for example "BUFFY" will work just as well as <hostname>A. But it does need to be unique on your network.

So in a way, the answer is "because".

pcmonk

Thanks! I'll check your post and look for the info to change that share name. That may clear up the problems I am having with the CIFS share being unstable.