cancel
Showing results for 
Search instead for 
Did you mean: 

CIFS on win2003 64bit

frederick
Champ in-the-making
Champ in-the-making
Hello,

While testing Alfresco 2.9B on a Windows 2003 professional 64bit server, we noticed that CIFS did not work correctly.
Our mapping is \\ice, which works most of the time. The trouble starts when a user clicks his way into a folder structure: after several clicks, either the explorer window closes, or an error message appears (system unavailable) and the window hangs.
Either way, we cannot use cifs for longer than a few seconds (though sometimes it lasts for several minutes).

In the logfile, the following errors appear:
08:27:15,821 ERROR [smb.protocol.mailslot] Host announce error  (LANA 4)
08:27:25,821 ERROR [smb.protocol.mailslot] Host announce error  (LANA 4)
08:27:45,822 ERROR [smb.protocol.mailslot] Host announce error  (LANA 4)
08:27:45,822 ERROR [smb.protocol.mailslot] Marked LANA as unavailable due to send errors

Has anyone else encountered this situation on a win64 environment?

It looks like this issue has been around for a while: http://forums.alfresco.com/viewtopic.php?f=9&t=7583
In our case also the returned status code is 119, which is not recognized by the Win32NetBIOSHostAnnouncer and is treated as an error.
16 REPLIES 16

jbarmash
Champ in-the-making
Champ in-the-making
I don't have an answer to your problem, but assuming you were trying to use the native implementation I'd suggest to perhaps try the java-based implementation only.

vycitalr
Champ in-the-making
Champ in-the-making
Hello,

I started to experience this error too - on MS Win Server 2003 Enterprise Edition. However, I am not sure if it blocks us from using CIFS. At the first glance it seems to work despite this error. Also I think this is related only to the "netbios" implementation, if I  use the default "winsock", this errror is not shown. Try switching to winsock impl.

Regards Robert.

vycitalr
Champ in-the-making
Champ in-the-making
Btw, Jbarmash, what do you exactly mean by using only java-based implementation on Windows?  Does it mean to comment out

<Win32NetBIOS/>
<Win32Announce interval="5"/>

and instead have

<tcpipSMB/>
<netBIOSSMB/>

In that case, I do I need to apply the registry change described somewhere like:

To enable native SMB support under Windows requires that the Windows native SMB support is disabled by editing, or creating, the following registry key :-
      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
      "SMBDeviceEnabled"=dword:00000000

Thanks for clarification.

ashish
Champ in-the-making
Champ in-the-making
We are facing the same issue with Win2003 64 bit. We have tried it on 32 bit versions of Win XP and Win 2003, and it works.

On Win2003 64 bit, we have tried to switch to JNI based netbios by changing Win32NetBIOS api to netbios, as well as disabling the SMB device by setting the registry entry.

Has any been able to get CIFS working with Win2003 64 bit OS?

ashish
Champ in-the-making
Champ in-the-making
Adding to the last post -
With Winsock impl of Win32NetBIOS, we get error about 'Address Family not supported by the requested protocol'. Using JNI based NetBios implementation, we get error about unable to announce host.

grosisimo
Champ in-the-making
Champ in-the-making
Hi I'm facing the same problem.
I'm using a Windows server 2003 64 bits with java 1.6u6 (32 bits) and I need alfresco to work as a service (that's why I installed a 32 bits java). I'm using Alfresco 2.9B.
Alfresco throws me
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:162)
   at org.alfresco.filesys.smb.mailslot.WinsockNetBIOSHostAnnouncer.initialize(WinsockNetBIOSHostAnnouncer.java:103)
   at org.alfresco.filesys.smb.mailslot.HostAnnouncer.run(HostAnnouncer.java:270)
Before installing the 32 bits java I was using a 64 bits java, and CIFS did work (sometimes not very well). It used to throw the "LANA" error to the log (LANA 4, LANA 6 and LANA 7), but I (almost) always could access CIFS. So I guess this issue is related to the java version somehow.
vycitalr, have you tried modifing the registry? Did it work?.

Thanks!
Thanks

grosisimo
Champ in-the-making
Champ in-the-making
Any help? Smiley Sad

vycitalr
Champ in-the-making
Champ in-the-making
As to the registry change - this does not regard 64-bit system, perhaps it's little bit off this topic. It's just general enabling native samba on win, I read somewhere. I did not try.
Regards Robert

grosisimo
Champ in-the-making
Champ in-the-making
Hi, I've been trying it and finally could use alfresco. Now I'd like to know if this modification has any drawback. Mainly, I'd like to know what side effects the registry modification has (disabling smb native support in windows).
The one I saw was that netbios naming gets enabled only for the alfresco adapter. For the others I needed to use its ip addresses (I could use hosts file and I guess dns too, but not netbios naming).
I must install alfresco in a server. Users need to connect using smb to this server, so I was thinking in disabling netbios in one of the network adapters, but leaving it enabled in the others so they could access to shared files using one of them. Will this registry modification affect them?. Will I have any problem?. Will this work?.

Thanks!
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.