Alternate Windows Auth login failure for SQL Server

[pwillinger]

All -

We are receiving a login failure...

the user has not been granted the requested logon type at this computer.

...when using alternate windows credentials to connect to a SQLServer database.  Using the option, use current credentials is successful when using the same windows account as tested for the alternate account.  The tested account can successfully connect to the database using Management Studio.  The DBA has viewed the logs and found no log-on failures during our test.  To me that means it didn't even get to the database for authentication but was likely stopped either at the originating PC or the server running SQLServer.

Any insight from anyone?

tia

patw

[rar59b]

Has anyone able to solve this issue? We are currently experiencing this error while onnecting to Impala via directquery using alternate creds.

[Anonymous]

I am having a very similar issue. Did you find a resolution? I am working with a VPN connection remotely and can get on to SSMS but not the SQL database. DBA said that it has something to do with powerBI and no one seams to have an ansewr. 

[v-yuezhe-msft]

@pwillinger,

I am unable to reproduce this issue. Do you enter domain\username as user name? What Windows group is the user located in?


Regards,
Lydia

[pwillinger]

Thank you for your response.  In your test were you connecting to a SQLServer db on the same machine as PowerBI is installed.  In our tests the SQLServer db is on a seperate server.  We can connect to the remote database using current credentials but if we switch and use alternate credentials and test using the same account used in current credentials we fail to authenticate.   

The login failure is…

Logon failure: the user has not been granted the requested logon type to this computer.

…this does not appear to be a database authentication error but rather a Windows error.

[Conarl_on_BI]

Hi @pwillinger,

There is a lot of determining factors for windows authentication to be successfully either via the current OS user or using the alternative user option. For example from your comment the DB is in a separate data center/domain hence for you to use alternative crediential domains between where you're using your OS user and where the DB is installed needs to resolve to each other. 

Also I not saying that this the solution since there many more determining factors that can be the problem if you provide an overview of the architecture I can guide you on how to approach this. 

Hope this helps.

Thanks

Conarl_On_BI