[jcifs] authenticate with 1.2.3

ochaves at ebstudio.com ochaves at ebstudio.com
Fri Aug 26 16:04:05 GMT 2005


Hi!

sorry my english... jeje

I'm testing the new jcifs1.2.3 fixed with the NtlmHttpFilter connecting to a
Win2003 server, but received the next error:

treeConnect: unc=\\WEBCOLPAM\IPC$,service=?????
New data read: Transport1[WEBCOLPAM<00>/200.19.141.60:445]
00000: FF 53 4D 42 73 22 00 00 C0 98 07 C0 00 00 99 91  | SMBs"..+..+....|
00010: E5 92 0C A2 91 D0 00 00 00 00 33 EB 00 00 0A 00  |s..ó.-....3d....|

signature verification failure
00000: 82 5C E6 BB 3A 79 21 B0                          |.\µ+:y!¦        |

00000: 99 91 E5 92 0C A2 91 D0                          |..s..ó.-        |

NtlmHttpFilter: WEBCOL\orchabel: 0xC0000022: jcifs.smb.SmbAuthException: Access
is denied.

********

I have already installed the jcifs1.1.11 working fine and the log show me:

treeConnect: unc=\\200.19.141.60\IPC$,service=?????

NtlmHttpFilter: WEBCOL\orchabel: succesfully authenticated against
0.0.0.0<00>/200.19.141.60

********

I'm using the next web.xml

<filter>
    <filter-name>NtlmHttpFilter</filter-name>
    <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
    <init-param>
        <param-name>jcifs.http.domainController</param-name>
        <param-value>200.19.141.60</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.http.domain</param-name>
        <param-value>WEBCOL</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.smb.client.username</param-name>
        <param-value>orchabel</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.smb.client.password</param-name>
        <param-value>**********</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.netbios.wins</param-name>
        <param-value>200.19.141.60</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.util.loglevel</param-name>
        <param-value>3</param-value>
    </init-param>
    <init-param>
        <param-name>jcifs.netbios.cachePolicy</param-name>
        <param-value>-1</param-value>
    </init-param>
 </filter>

<filter-mapping>
    <filter-name>NtlmHttpFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>
</web-app>


maybe the problem is the same port 445 trying authenticate the user.

thanks in advance.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



More information about the jcifs mailing list