[jcifs] client disconnects when lmcompatibility set to 5

Michael B Allen ioplex at gmail.com
Tue Mar 2 15:08:47 MST 2010

Hi Jimmy,

I would need to see a good packet capture before I could even begin to
decipher what is happening.

However, note that I have little to no free time for working on
non-critical issues in JCIFS so unless this turns out to be something
obvious, it's entirely possible that it might end up on the TODO for
"further investigation" and unfortunately we have things on the TODO
that have been under further investigation for years.

But if you send me a capture, I'm happy to at least look at it.


Michael B Allen
Java Active Directory Integration

On Tue, Mar 2, 2010 at 4:26 PM, Jimmy Young <youj at yahoo.com> wrote:
> Hi experts,
> I am using j-interop which uses jcifs for DCOM communication.
> I've been testing with 1.2.19 and 1.3.14.
> The server is a Windows box and the client is a linux box.
> A local acount is used for authentication. The client is constantly read data
> from server in about 1 Hz rate.
> When the lmcompatibility at server is set to 3, everything works fine.
> When the lmcompatibilty is set to 5, the client connects to server fine and
> read data successfully initially. After sometime, the server DCOM log will say
> the client disconnects. Our code will re-connect after disconnection.
> Examining the server event log, there is "logoff" message at multiple of 4
> minutes interval. It does not happen every 4 minutes. It happens at sometime 4
> minutes or 8 minutes, and etc.
> Logon Failure:
>        Reason:         Unknown user name or bad password
>        User Name:      opcclient
>        Domain:         MY.DOMAIN.ORG
>        Logon Type:     3
>        Logon Process:  NtLmSsp
>        Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
>        Workstation Name:       JCIFS121_210_A9
> (This is Microsoft explanation of the event.
> Consider the following scenario. A Microsoft Windows Server 2003-based member
> computer is joined to a domain controller. In the domain controller, the audit
> policy is turned on for logon failures. When a local user on the member
> computer logs off, the following event is logged in the Security log in the
> domain controller:
> )
> What could cause this disconnection? The connection is being used constantly.
> Now the second question. After we re-connect to server, the lsof showed left
> over pipes on the client box.
> < java      18791   console  108r     FIFO        0,6             5053914 pipe
> < java      18791   console  109w     FIFO        0,6             5053914 pipe
> < java      18791   console  110r     0000       0,11        0    5053915
> eventpoll
> < java      18791   console  111r     FIFO        0,6             5053916 pipe
> < java      18791   console  112w     FIFO        0,6             5053916 pipe
> < java      18791   console  113r     0000       0,11        0    5053917
> eventpoll
> Eventually "too many files open" error occurs and forces us to shutdown the
> program.
> Any help is very much appreciated.
> I'll be happy to provide wireshark capture file if needed.
> Please provide the filter if any.
> J.

More information about the jCIFS mailing list