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 on Windows 2003

mojo-jojo

System:
Windows 2003 x64
Alfresco 1.2.0 final
MySQL 4.1
JDK 5.0 Update 6

All of the functions work (WebDAV, image transformation, document conversion, etc.) except for CIFS access. Should the default configuration work right away? When I try to access \\ALFSERVERNAME_A it can't be found.

I have included Win32NetBIOS.dll in the path and Alfresco finds it just fine. I do receive this error though.

13:15:12,842 ERROR [org.alfresco.smb.protocol.mailslot] HostAnnouncer initialization error
org.alfresco.filesys.netbios.win32.WinsockNetBIOSException: 10047:CreateDatagramSocket - Address family not supported by protocol family
   at org.alfresco.filesys.netbios.win32.Win32NetBIOS.CreateDatagramSocket(Native Method)
   at org.alfresco.filesys.netbios.win32.NetBIOSSocket.createDatagramSocket(NetBIOSSocket.java:154)
   at org.alfresco.filesys.smb.mailslot.WinsockNetBIOSHostAnnouncer.initialize(WinsockNetBIOSHostAnnouncer.java:89)
   at org.alfresco.filesys.smb.mailslot.HostAnnouncer.run(HostAnnouncer.java:248)‍‍‍‍‍‍

Is this why it's not working? If not, what steps do I need to take to make the CIFS access work on a Windows server?

Thanks.

Find more posts tagged with

Comments

gary_spencer

Hi,

Could you try changing the following setting in the file-servers.xml file (in the WEB-INF/classes/alfresco folder) :-

<Win32NetBIOS api="netbios"/>

See if that fixes the problem.

Cheers

Gary

mojo-jojo

Okay setting the api to netbios got rid of the error.

My workstation is running WinXP Pro SP2.

But when I try to access \\SERVERNAME_A Windows says it cannot find it. So, I thought it was a name resolution problem. But, I am able to ping the server from my workstation using the name SERVERNAME_A. The record for SERVERNAME_A shows up in the WINS server db and in my Network Neighborhood.

I ran nbtstat on the server and the workstation which both give me

Local Area Connection:
Node IpAddress: [10.0.0.90] Scope Id: []



           NetBIOS Remote Machine Name Table



       Name               Type         Status

    ———————————————

    SERVERNAME        <00>  UNIQUE      Registered 

     SERVERNAME        <20>  UNIQUE      Registered 

    DOMAIN_NAME        <00>  GROUP       Registered 

     SERVERNAME_A      <20>  UNIQUE      Registered 

     SERVERNAME_A     <00>  UNIQUE      Registered 

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

DOMAIN_NAME being my domain name.
SERVERNAME being the name of the box that alfresco is running on.

Netbios is enabled on both machines. I've disabled to firewalls on both machines.

Any ideas?

gary_spencer

Hi,

There is an issue with the WINS name registration that I have to look at some time where it seems to register but the server is still not accessible, this sounds like the same problem.

Try adding a static mapping to the WINS database for the Alfresco server, that should fix it for now.

Cheers

Gary

mojo-jojo

Okay so I modified the WINS db so that there are only static mappings for SERVERNAME_A.

The login prompt came up once the first time I tried to access the CIFS server. But, after that the CIFS server gives me an error: "you were not connected because a duplicate name exists on the network".

mojo-jojo

bump

Is there anything else I can try to get this working? This really is a must have feature for my company.

cmeinck

How long is your actual server name? I had a problem recently, where my Alfresco server name + "_A", was too long, so it was truncated. I was able to access it with the truncated name, but not with the "real" name.

I think the character limit for the name is 15.

gary_spencer

Hi,

The name limit is 15 characters with NetBIOS, there's a 16th character which indicates the service type (0x20 in the case of a file server).

Cheers

Gary

mojo-jojo

The Server's name is only 5 characters long.

gary_spencer

Hi,

Have you tried the latest code as it now contains support for 64bit Windows, there is a seperate JNI DLL for 64bit, the correct DLL will be loaded at startup depending on the platform type.

Cheers

Gary

mojo-jojo

I am running Version: Community Network - v1.2.1 and it is a fresh install

I made sure to edit the config to:
<Win32NetBIOS api="netbios"/>

I was running 1.2.0 when I first starting having problems.

The server is a Windows file server if that makes any difference.