-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.Runtime.InteropServices.COMException (0x80070721): A security package specific error occurred. #31
Comments
Having same problem |
Same here, I believe I have default configuration |
Has anyone found a solution for this problem? |
It seems that KrbRelayUp.exe have been fixed in october 2022 with the possibility of create LDAP bind with DCOM. |
For anyone playing around with the code and encountering this error: I get this error when I try to use an SPN with a specified port in it. Has most likely nothing to do with the issue encountered in the posts above, but if you google the error code, you might find this post. |
|
Hello
Did anyone fix this issue?
PS C:\Users\normaluser\Desktop\kbrrelayUp_Debug\Debug> .\KrbRelayUp.exe relay -Domain local.domain -CreateNewComputerAccount -ComputerName fake6$ -ComputerPassword 123456$
KrbRelayUp - Relaying you to SYSTEM
[+] Rewriting function table
[+] Rewriting PEB
[+] Init COM server
[+] Computer account "fake6$" added with password "123456$"
[+] Register COM server
[+] Forcing SYSTEM authentication
[+] Got Krb Auth from NT/SYSTEM. Relying to LDAP now...
[+] LDAP session established
[-] LDAP connection failed
System.Runtime.InteropServices.COMException (0x80070721): A security package specific error occurred.
A security package specific error occurred.
at KrbRelayUp.Relay.Ole32.CoGetInstanceFromIStorage(COSERVERINFO pServerInfo, Guid& pclsid, Object pUnkOuter, CLSCTX dwClsCtx, IStorage pstg, UInt32 cmq, MULTI_QI[] rgmqResults)
at KrbRelayUp.Relay.Relay.Run() in C:\Users\admin.DESKTOP-8OHJG6I\Desktop\TMP\KrbRelayUp-main\KrbRelayUp\Relay\Relay.cs:line 159
The text was updated successfully, but these errors were encountered: