If the 3rd party file (or cache) server sends FIND_FIRST2 response without null termination, JCIFS fails to parse the response resulting in FIND_NEXT2 request not being sent. But Windows File server client parses this response fine.

After looking into the "Trans2FindFirst2Response.java", the condition where "lastName" value is initialized fails and "lastName" was set to null value. When JCIFS tries to send FIND_NEXT2 request with this "lastName" (which contains null value), it aborts with Exception.

Patch for fixing the issue:

#diff Trans2FindFirst2Response.java.orig Trans2FindFirst2Response.java.patch

166c166,167
<         SmbFindFileBothDirectoryInfo e;
---
>         SmbFindFileBothDirectoryInfo e = null;
>         lastName = null;

208a210,214
>
>         if (lastName == null) {
>             lastName = e.filename;
>             resumeKey = e.fileIndex;
>         }