topic Re: possible bug for cifs-server in file-servers.xml in Alfresco Archive

possible bug for cifs-server in file-servers.xml

stegbth — Mon, 08 Dec 2008 10:12:56 GMT

hello everybody,i found a possible bug in Alfresco-Labs-3c-Linux-x86-Installin tomcat/webapps/alfresco/WEB-INF/classes/alfresco/file-servers.xmlin line 5 i have <host name="${cifs.localname}A" domain="${cifs.domain}"/> ‍my servername is alfresco, which leads to cifsname \\ALFRESCOAwhich

Re: possible bug for cifs-server in file-servers.xml

loftux — Mon, 08 Dec 2008 10:53:54 GMT

This is as it is supposed to be, you cannot have two CIFS server names that clash, the localname is already use by the server you are running on.
So this setting makes up a name using the local name and appending an A to it.
This name is then broadcasted on your networkm, or depending on you config added to wins server.

Think of it as a standalone file server on your network, only this time it is hosted on another server.

You can specify a completely different name, just type in what you want it to be called, and add that to you dns or wins.

Re: possible bug for cifs-server in file-servers.xml

stegbth — Mon, 08 Dec 2008 11:28:43 GMT

hi,

thanx for the reply,

but i cant also not have two different services on one port tcp/139?

greetings
thomas

Re: possible bug for cifs-server in file-servers.xml

loftux — Mon, 08 Dec 2008 11:47:52 GMT

That is correct, you should not run a samba server in your linux box.
See more here http://wiki.alfresco.com/wiki/File_Server_Configuration

Re: possible bug for cifs-server in file-servers.xml

stegbth — Mon, 08 Dec 2008 12:50:07 GMT

thanx for your answer, but i still doesn't recognize the sense of changing the name.
if there must not run a samba-server running and the windows-smb service get disabled. where is is the problem alfresco uses the same cifs-name?

Re: possible bug for cifs-server in file-servers.xml

stegbth — Wed, 21 Jan 2009 13:06:32 GMT

Hi,

i installed alfresco-labs 3stable today and see the same setting.
as this isn't a bug as noted above, i dont understand, why it is necassery to modify the windows-hostname, as it isn't allowed to run samba on linux and on windows the smb must get disabled??

greetings
thomas