You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following error appears when executing a command in Server B and tries to pass credentials to a Server C using sqlcmd command.
Command [ERROR ] Execution finished with the following error (winrm-exec.py:267)[root]
18:40:34 [ERROR ] Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'..
18:40:34 (winrm-exec.py:268)[root]
Expected behavior
It's expected the Double Hop to work.
Screenshots
Desktop (please complete the following information):
Describe the bug
Actually not possible to perform double Hop from Rundeck Server to a Server C. Server B is unable to pass credentials to Server C.
Rundeck Server > Server B > Server C.
linux > windows > windows
My Rundeck detail
To Reproduce
Steps to reproduce the behavior:
Create a job, use pywinrm + kerberos authentication and execute the command in Server B
Example:
"query_execution.sql"
use rundeckdb;
select * from execution;
"Job"
sqlcmd -S ServerC -i C:\sql\query_execution.sql
The following error appears when executing a command in Server B and tries to pass credentials to a Server C using sqlcmd command.
Command [ERROR ] Execution finished with the following error (winrm-exec.py:267)[root]
18:40:34 [ERROR ] Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'..
18:40:34 (winrm-exec.py:268)[root]
Expected behavior
It's expected the Double Hop to work.
Screenshots
Desktop (please complete the following information):
Additional context
A workaround ( not working when connecting to database, but working when using for example "net view" ) . https://blogs.technet.microsoft.com/ashleymcglone/2016/08/30/powershell-remoting-kerberos-double-hop-solved-securely/
$ServerB = Get-ADComputer -Identity ServerB
$ServerC = Get-ADComputer -Identity ServerC
Set-ADComputer -Identity $ServerC -PrincipalsAllowedToDelegateToAccount $ServerB
Then on ServerB: KLIST PURGE -LI 0x3e7
Job is included
The text was updated successfully, but these errors were encountered: