We are not able to connect JLAN application no more , getting an issue with NETBIOS

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
srinubhusala
Member II

We are not able to connect JLAN application no more , getting an issue with NETBIOS

018-04-07 22:11:34.555 [Sess_T279_172.31.26.61] SessionLogger - State changed to NBHANGUP
2018-04-07 22:11:34.555 [Sess_T279_172.31.26.61] SessionLogger - Cleanup session, vcircuits=0, changeNotify=0
2018-04-07 22:11:34.555 [Sess_T279_172.31.26.61] SessionLogger - State changed to NBHANGUP
2018-04-07 22:11:35.781 [CIFSSessHandler_NetBIOS] SessionLogger - [SMB] Session request received from 172.18.227.146
2018-04-07 22:11:35.781 [CIFSSessHandler_NetBIOS] SessionLogger - [SMB] Waiting for session request ...
2018-04-07 22:11:35.782 [Sess_N22_172.18.227.146] SessionLogger - Server session started
2018-04-07 22:11:36.079 [AlfJLANWorker12] SessionLogger - Closing session due to exception
org.alfresco.jlan.netbios.NetBIOSException: NBREQ Called name is not this server (FILEREPOSITORY)
        at org.alfresco.jlan.smb.server.SMBSrvSession.procNetBIOSSessionRequest(SMBSrvSession.java:962)
        at org.alfresco.jlan.smb.server.SMBSrvSession.processPacket(SMBSrvSession.java:1572)
        at org.alfresco.jlan.smb.server.CIFSThreadRequest.runRequest(CIFSThreadRequest.java:64)
        at org.alfresco.jlan.server.thread.ThreadRequestPool$ThreadWorker.run(ThreadRequestPool.java:155)
        at java.lang.Thread.run(Thread.java:745)
2018-04-07 22:11:37.800 [CIFSSessHandler_TCP-SMB] SessionLogger - [SMB] Session request received from 172.31.26.62
2018-04-07 22:11:37.800 [CIFSSessHandler_TCP-SMB] SessionLogger - [SMB] Waiting for session request ...
2018-04-07 22:11:37.800 [Sess_T280_172.31.26.62] SessionLogger - Server session started
2018-04-07 22:11:37.915 [Sess_T280_172.31.26.62] SessionLogger - ## Session closing.
Remote disconnect

1 Reply
afaust
Master

Re: We are not able to connect JLAN application no more , getting an issue with NETBIOS

Are you using JLAN in standalone mode or are you working with JLAN embedded in Alfresco Content Services?

Anyway, there is really no point working with that library any more, since Alfresco does not support its use in a standalone capacity (standalone library hasn't had a release since ca. 2009) and will remove the support of CIFS / SMB based shared drives in one of the upcoming versions since Microsoft / WIndows no longer supports the old CIFS / SMB 1.0 dialect provided by JLAN.