[jcifs] jcifs.smb.SmbAuthException:

[Sokolov, Oleg]

Michel,

I'm not changing any thing fir credential. Just replacing jar file. With
0.7.12 I do get list of files but with 1.2.17 getting an exception

-----Original Message-----
From: Michael B Allen [mailto:miallen at ioplex.com] 
Sent: Thursday, January 03, 2008 1:42 PM
To: Sokolov, Oleg
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] jcifs.smb.SmbAuthException:

On Thu, 3 Jan 2008 13:29:01 -0500
"Sokolov, Oleg" <oleg_sokolov at merck.com> wrote:

> Hi,
> 
>  
> 
> We were using jcifs for a few years to connect from web app to windows
> share. The version we were using was old - 0.7.12. Now we upgraded to
> the 1.1.17 and we start receiving jcifs.smb.SmbAuthException: Logon
> failure: user not allowed to log on to this computer.
> 
> We are connecting using service account. If we switch to the personal
> account to connect to the share then everything working fine with new
> version. What should we do to be able to connect using service
account?

Hi Oleg,

You would need to get a capture of 0.7.12 and 1.2.17 and compare to see
verify what credentials were really being used and compare the captures
to see what is different. In general, that error is pretty much what
it sounds like - the credentials supplied really cannot log into that
computer which suggests that 0.7.12 really can't either.

Mike

-- 
Michael B Allen
PHP Active Directory SPNEGO SSO
http://www.ioplex.com/




------------------------------------------------------------------------------
Notice:  This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is 
available at http://www.merck.com/contact/contacts.html) that may be 
confidential, proprietary copyrighted and/or legally privileged. It is 
intended solely for the use of the individual or entity named on this 
message. If you are not the intended recipient, and have received this 
message in error, please notify us immediately by reply e-mail and then 
delete it from your system.

------------------------------------------------------------------------------