Hello Christian,

With regards to the question I asked last week (see below), I have looked 
at the event log, which contains the following message:

=============Beginning of BD-w2k-test02 event log=========================
===========
Date: 3/20/02            Source:  Security
Time:  12:24             Category:  Login/Logoff
Type: Failure            Event ID: 529
User:  NT Authority\System
Computer: BD-W2k-test02

Logon Failure:
        Reason:         Unknown user name or bad password
        User Name:      derwent
        Domain:         FERMITEST
        Logon Type:     3
        Logon Process:  NtLmSsp
        Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
        Workstation Name:       \\G4DERWENT

=============End of BD-w2k-test02 event log===============================
===========

In talking with our Windows system administrator, he interprets it as a NTLMv1 
access attempt (we have verified the username and password from a W2K system 
to be correct).  Is there anything else I can check on my end?

-Paul

On Monday, March 18, 2002, at 02:58 PM, Christian Starkjohann wrote:

> Paul Derwent wrote:
>> I am looking into using sharity (currently have a demo version only on Mac
>> OS X) to fit into the existing Windows domains in our office.  It works 
>> well
>> within the NT domains but I am unable to connect to the Win2k domains (I 
>> get
>> "Access Denied  Error context: DOS error on server).   Reading the manual
>> tells me that this error means the server rejected my password.  The Win2k
>> domain is setup to acknowledge Kerberos tickets or NTLMv2 password encryption.
>> Is there a switch to set the encryption method (I know Sharity currently
>> does not support Kerberos) -- I was unable to find information in the manual.
>
> Sharity always uses NTLM authentication (except with Windows for Workgroups
> servers). If you enable NTLMv2 and CIFS over netbios over TCP, Sharity
> should be able to connect.
>
> If it fails, please see the server's event log for details. If you have
> enabled logging of authentication failures, the server should log the reason
> for rejected logins in the event log.
>
> Regards, Christian.
>
> --
> Dipl.-Ing. Christian Starkjohann
> Objective Development
> mailto:[EMAIL PROTECTED] | http://www.obdev.at/
>
>
>

--

Paul Derwent
Fermilab Pbar Source
[EMAIL PROTECTED]
http://www.fnal.gov/

_______________________________________________
Sharity-talk mailing list
[EMAIL PROTECTED]
To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk

Reply via email to