You are viewing limited content. For full access, please sign in.

Question

Question

Problems logging into the client.

asked on March 24, 2016

I have a user logging into their machine as a domain admin and they would like to log into the client with their domain/username credentials. this works fine when they log into the machine as themselves just not as an admin. They receive a 1201 windows authentication failed error. Are there any settings to get this to be able to work? This is a new system for them and they are using version 10.

 

Stack trace details look like this:

 

Error Code: 1201

Error Message: Windows authentication failed. [1201]

 

------------ Technical Details: ------------

 

LFSO:

    Call Stack: (Exception)

        SSPILogin

        InternalDoLogin

        LFSession::Login

        CLFConnection::Create

    Additional Details:

        ERROR: 1201 (SSPILogin, LFSession.cpp:1779)

         (LFSO/10.0.0.865)

LF.exe (10.0.0.1039):

    Call Stack: (Exception)

        CLoginDialog::AttemptLogin

        CLoginDialog::LoginToServer

        CLoginView::LoginHandler

    Call Stack: (Current)

        CLoginDialog::LoginToServer

        CLoginView::LoginHandler

    Additional Details:

        Exception: 0x800404b1 [1201] (Windows authentication failed.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:796)

    Call History:

        CLoginView::LoginHandler

         CLoginDialog::LoginToServer

          GetOptionString ([WengerGroupSettings]AdminNoPassword)

          GetOptionString ([WengerGroupSettings]UserName)

          GetOptionString ([Settings]UseWindowsAuth)

          GetOptionString ([WengerGroupSettings]UseWindowsAuth)

          CLoginDialog::AttemptLogin

           GetOptionString ([Settings]CheckServerVersion)

0 0

Replies

replied on March 24, 2016

Is the issue user specific?  If you reboot the machine and login with a different windows account, does it work?

0 0
replied on March 30, 2016

Hi Raymond, I'm still waiting to hear back on this. i'll let you know when I get some information. thanks!

0 0
replied on April 1, 2016

I was informed that the specific scenario they were trying to do looks to be resolved. They tried on another machine and it appears to work now.

 

Thank you for your assistance, Raymond

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.