Login fails

  • Win 2k sql 2K security sql server and Windows.

    Domain A Server 1

    Domain B Client 1

    No trust between A and B

    Through EM client 1 wants to register server1 using IP and sa. It fails server does not exist or invalid user. No errors in SQL Server log, security event log on Server 1 gives

     The logon to account: jzach
    
    by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    from workstation: MYWORKSATIONHERE
    failed. The error code was: 3221225572

    Next error

    
    
    Logon Failure:
    Reason:Unknown user name or bad password
    User Name:jzach
    Domain:DOMAIN_B
    Logon Type:3
    Logon Process:NtLmSsp
    Authentication Package:NTLM
    Workstation Name:MYWORKSATIONHERE

    Any ideas why it would be using nt authentication and not SQL. it's like it completly ignored my SQL Server Autheticaton request.

    John Zacharkan


    John Zacharkan

  • Can you ping to server1? Is server1 configured with mixed authentication mode?

    Edited by - Allen_Cui on 07/10/2003 3:24:55 PM

  • I can ping and also point to file shares.

    quote:


    Can you ping to server1? Is server1 configured with mixed authentication mode?

    Edited by - Allen_Cui on 07/10/2003 3:24:55 PM


    John Zacharkan

    Edited by - zach_john on 07/11/2003 09:14:41 AM


    John Zacharkan

  • What is the operating system on the client?

  • Win 2K 5.00.2195

    quote:


    What is the operating system on the client?


    John Zacharkan


    John Zacharkan

  • Is the client using named pipes or TCPIP? NTLMSSP services are for RPC programs that use transports other than named pipes. Try changing the client to use named pipes instead.

    Just one thought.

  • One other question. Is your Windows enterprise all Active Directory or are you running mixed mode?

  • Well, I think I'm going to throw in the towel on this for now. Gotta get back to work. Here's the best I could find:

    quote:


    When a down-level client fails a logon attempt, Windows 2000 generates Event Id 681 on the Windows 2000 domain controller.

    NOTE: This also happens through a trust to a down-level domain.

    The source of the event is Security.

    NOTE: The error codes in the Security Event log message are displayed in decimal.

    Error Code Hexadecimal

    Error Code Cause

    3221225572 C0000064 User logon with misspelled or bad user account


    I think you'll have your hands full with this one. Good luck.

    All the best,

    Dale

  • Active Directory native mode

    quote:


    One other question. Is your Windows enterprise all Active Directory or are you running mixed mode?


    John Zacharkan


    John Zacharkan

  • Well, then AD is not likely to be the cause of the problem. I think Allen's question would be my next question, "Is Server1 configured with mixed authentication mode [or Windows only]?".

  • quote:


    Well, then AD is not likely to be the cause of the problem. I think Allen's question would be my next question, "Is Server1 configured with mixed authentication mode [or Windows only]?".


    Just to clarify, this is in reference to SQL server running on Server1.

    Dale

  • I missed answering that I guess, yes Server1 is configured with mixed authentication mode.

    quote:


    I think Allen's question would be my next question, "Is Server1 configured with mixed authentication mode [or Windows only]?".


    John Zacharkan


    John Zacharkan

  • What is "EM client 1"? What is the application?

  • What happens if you try and connect as sa using Query Analyzer from the client? Same issue?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • Nevermind. I just got it. Are you referring to Enterprise Manager? Did you install client tools?

Viewing 15 posts - 1 through 15 (of 36 total)

You must be logged in to reply to this topic. Login to reply