[jcifs] Ntlm authentication prompts 2nd user - Win 2003

Fri Jul 8 18:00:11 GMT 2005

For some reason, yesterday the first user was getting in fine and the second user had the problem.  Today it appears that everytime I connect, I get the prompt.  I'm baffled as to what changed over night to cause this behavior.

I will try to download 1.1.11 jar and I'll let you know what happens.

Thanks for the help, Mike.


P.S. As for those timeouts, they occur instantly after I get the prompt.  I'm not sure if that is significant, but I thought I would mention it since you said they happen when the smb transports have been idle "for a while" (of course a while can be very relative :-).

-----Original Message-----
From: Michael B Allen [mailto:mba2000 at ioplex.com] 
Sent: Friday, July 08, 2005 12:37 PM
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] Ntlm authentication prompts 2nd user - Win 2003

On Fri, 8 Jul 2005 10:25:52 -0500
"AARON WILT" <AARONWILT at afninet.com> wrote:

> "Explain what the problem is and not what you think the problem is."
> Ok, sorry for not being clear.  The problem is that when I try to access the NtlmHttpAuthExample servlet, I get prompted for a username/password/domain instead of it automatically determining my NT Domain information.  You can see my web.xml in the previous email.
> "Do you get an error?"
> Yes - now that I've added log level init param (level 3) and I downloaded ethereal, I can see what these errors are.
> "If so what is the error?"
> In my Tomcat server log, I get the following error:
> <snip>
> signature verification failure
> 00000: 9A 61 B5 BB A0 C4 7C ED                          |.aµ» Ä|í        |
> 00000: 03 2D 79 55 9A E3 24 88                          |.-yU.ã$.        |

So what happend to the "2nd user" part? Is that not true? If it is still occuring and you have established preauthentication then it should work. Try 1.1.11 vs 1.2.1. Send me an ethereal capture of the error.

> java.net.SocketTimeoutException: Receive timed out
> 	at java.net.PlainDatagramSocketImpl.receive(Native Method)
> 	at java.net.DatagramSocket.receive(DatagramSocket.java:711)
> 	at jcifs.netbios.NameServiceClient.run(NameServiceClient.java:184)
> 	at java.lang.Thread.run(Thread.java:534)
> java.net.SocketTimeoutException: Read timed out
> 	at java.net.SocketInputStream.socketRead0(Native Method)
> 	at java.net.SocketInputStream.read(SocketInputStream.java:129)
> 	at jcifs.util.transport.Transport.readn(Transport.java:29)
> 	at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:319)
> 	at jcifs.util.transport.Transport.loop(Transport.java:89)
> 	at jcifs.util.transport.Transport.run(Transport.java:229)
> 	at java.lang.Thread.run(Thread.java:534)

Actually these timeouts are normal. These are the name service and smb transports timing out after having been idle for a while.


More information about the jcifs mailing list