[jcifs] Re: Can't get NTLM HTTP Authentication to work

mac671 mac671mac at wp.pl
Fri Oct 13 10:30:36 GMT 2006


I seem to be experiencing the very similar or even same problem that
Christian has described.
That is why I post in this thread. Even tho I am using WINS, the symptoms
are as described in the OT.

I made a network capature and I am not getting the response to the type
three message.

I turned on the logging of the jcifs.util.loglevel to lvl 4.
and also jcifs.smb.client.soTimeout 1000000

session established ok with <<DOMAIN_NAME>><1C>/<<WINS_IP_ADDRESS>>
requesting negotiation with <<DOMAIN_NAME>><1C>/<<WINS_IP_ADDRESS>>
operation completed
LM 0.12]
new data read from socket: <<DOMAIN_NAME>><1C>/<<WINS_IP_ADDRESS>>
byteCount=38 but readBytesWireFormat returned 18
operation completed
Oct 13 12:04:51 CEST
treeConnect: unc=\\<<WINS_IP_ADDRESS>>\IPC$,service=?????
sessionSetup: accountName=wro03372,primaryDomain=<<DOMAIN_NAME>>
operation completed
operation completed
new data read from socket: <<DOMAIN_NAME>><1C>/<<WINS_IP_ADDRESS>>
operation completed
Server 2003 3790 Service Pack 1,nativeLanMan=Windows Server 2003
operation completed
java.net.SocketTimeoutException: Receive timed out
	at java.net.PlainDatagramSocketImpl.receive0(Native Method)
	at java.net.PlainDatagramSocketImpl.receive(Unknown Source)
	at java.net.DatagramSocket.receive(Unknown Source)
	at jcifs.netbios.NameServiceClient.run(NameServiceClient.java:184)
	at java.lang.Thread.run(Unknown Source)

even tho the jcifs.smb.client.soTimeout is set to a very high value this
Exeption is thrown in my Tomcat sysout very quickly ( less than 3 sec ).

I also found another topic

which says the java.net.SocketTimeoutException: Receive timed out
is harmless but I think it is not.

I cant figure out what is the matter, and I been stuck with this since

Christian do you also get the timeOutException in your Tomcat log?


Eric Glass wrote:
> Are you going direct against Tomcat's HTTP server, or through an
> intermediate web server (Apache or IIS, etc.)?  If you are seeing the
> browser send a Type 3 message, but the server not responding
> appropriately, you should see some messages in the app server log;
> i.e. it would imply the failure is occurring on the backend
> authentication rather than IE just dropping the handshake.
> If you can provide a packet trace, that might give some additional
> insight; ideally one taken at the app server including both HTTP and
> SMB/CIFS traffic, as that would show the end-to-end authentication
> process.  Don't send to the full mailing list though, as it may
> contain sensitive information.
> Otherwise, you can try upping the log level for jCIFS and see if that
> gives any more information.
> Eric
> On 10/13/06, Christian <wuerdemann at gmail.com> wrote:
>> Christian <wuerdemann <at> gmail.com> writes:
>> > When we load the Tomcat Application with IE on the client, we receive a
>> "Page
>> > not found". We did a network capture and found that the server is not
>> > responding to the "type 3" Message of the client.
>> No idea at all? We are really stuck with that problem. Are there specific
>> settings for the Win 2003 DC that has to be enabled?
>> Thanks!
>> Christian

View this message in context: http://www.nabble.com/Can%27t-get-NTLM-HTTP-Authentication-to-work-tf2416840.html#a6793266
Sent from the Samba - jcifs mailing list archive at Nabble.com.

More information about the jcifs mailing list