Unable to connect to LDAP, verify your credentials #10

anasbousselham · 2022-02-16T23:46:56Z

Hi,
It's possible to used it without ldap flags.?!
Thanks

yellow-starburst · 2022-02-17T01:11:13Z

yes it is possible to be used without ldap flags.
Can you close the ticket now?

anasbousselham · 2022-02-17T01:23:41Z

I have this error without any flag!

rvazarkar · 2022-02-17T15:45:45Z

Are you running this through netonly? Do you have a proper domain authentication?

x3rz · 2022-02-19T08:51:44Z

I have this error without any flag!

Same issue for me without supplying any creds it is showing me that error

gabemarshall · 2022-02-24T18:15:32Z

@rvazarkar I'm also experiencing this. I'm running it through netonly and have proper domain auth (Powerview works fine, old versions of Invoke-Bloodhound work).

lungdart · 2022-02-24T21:54:52Z

Same situation here on the HTB forest machine.

When I checkout the old version of SharpHound from the bloodhound repo commit 6a95882e0e88c398f97f2a82a956eef5b3b10ae8, the identical command works (But then starts throwing stack traces later on)

I guess I'll keep going back into the commits until I can find a stable version...

walterone · 2022-02-28T19:28:35Z

still got the same issue, has anyone found a workaround yet?

rvazarkar · 2022-02-28T19:50:08Z

        ///     Tests the current LDAP config to ensure its valid by pulling a domain object
        /// </summary>
        /// <returns>True if connection was successful, else false</returns>
        public bool TestLDAPConfig(string domain)
        {
            var filter = new LDAPFilter();
            filter.AddDomains();

            var resDomain = GetDomain(domain)?.Name ?? domain;
            
            var result = QueryLDAP(filter.GetFilter(), SearchScope.Subtree, CommonProperties.ObjectID, resDomain)
                .DefaultIfEmpty(null).FirstOrDefault();

            return result != null;
        }

This is how we test for a valid LDAP connection: we query for domain objects and make sure we can get at least one. For whatever reason, that test is failing and we're getting nothing back. If you run with -v 0 it might give you some more insight as to where the check is failing, you can report back with that information

walterone · 2022-03-01T09:41:09Z

The verbose option only shows the TRACE info of the "TestConnection link" in the TestConnection() Function.

./sh.exe -v 0
2022-03-01T01:29:38.8844100-08:00|INFORMATION|Resolved Collection Methods: Group, LocalAdmin, Session, Trusts, ACL, Container, RDP, ObjectProps, DCOM, SPNTargets, PSRemote
2022-03-01T01:29:38.9000386-08:00|TRACE|Entering initialize link
2022-03-01T01:29:38.9000386-08:00|INFORMATION|Initializing SharpHound at 1:29 AM on 3/1/2022
2022-03-01T01:29:38.9000386-08:00|TRACE|Entering TestConnection link
2022-03-01T01:29:39.0719120-08:00|ERROR|Unable to connect to LDAP, verify your credentials
2022-03-01T01:29:39.0719120-08:00|TRACE|Exiting TestConnection link

Using powershell AD functionality and/or powerview it's possible to retrive objects in the domain.
Also it looks like that the issue is mainly related to the HTB Forest machine, i still have to try in other environments

rvazarkar · 2022-03-02T19:20:35Z

I beleive I know whats causing this, I'll have a new build soon

YB1-cyber · 2022-03-04T14:24:16Z

@rvazarkar
I joined the "unable to connect to LDAP" club , and also a friend of mine...
so if you can update here , it'll nice

BTW
I wonder:
A) Can you tell why the .ps1 collector had been removed ?
B) Will SharpHound.ps1 support the new format (matching bloodhound 4.1+) when we get it back ?

rvazarkar · 2022-03-07T17:18:09Z

Should be fixed in v1.0.3. Reopen if the problem is still there

@YB1-cyber it was removed because I ran out of time when doing this release, and yes it will

chinformer · 2022-03-18T16:27:16Z

Hey, I can confirm this is still affecting v1.0.3. I've just compiled the -dev 1.0.3 version (x64) no other changes and when supplying --ldapusername and --ldappassword the error is:

2022-03-18T16:18:27.4755485+00:00|INFORMATION|Resolved Collection Methods: Group, LocalAdmin, GPOLocalGroup, Session, LoggedOn, Trusts, ACL, Container, RDP, ObjectProps, DCOM, SPNTargets, PSRemote

2022-03-18T16:18:27.4876460+00:00|INFORMATION|Initializing sharpyhounds at 16:18 on 18/03/2022

2022-03-18T16:18:27.9424135+00:00|ERROR|Unable to connect to LDAP, verify your credentials

n0kovo · 2022-04-16T02:26:20Z

+1
Same issue with 1.0.3 (x64)

chinformer · 2022-04-19T08:15:06Z

@rvazarkar any update on the potential fix for this? I added the original comment on the 18th March 2022 :). Thank you

rvazarkar · 2022-04-19T15:46:05Z

Open a new issue, and use -v 0 to get verbose logging so I can see where the issue is happening

ronemp · 2022-07-06T16:55:50Z

Is this issue resolved?

mc702 · 2022-08-15T05:24:26Z

C:>SharpHound.exe -c All -v 0
2022-08-15T13:22:29.7881493+08:00|INFORMATION|This version of SharpHound is compatible with the 4.2 Release of BloodHound
2022-08-15T13:22:29.8979655+08:00|INFORMATION|Resolved Collection Methods: Group, LocalAdmin, GPOLocalGroup, Session, LoggedOn, Trusts, ACL, Container, RDP, ObjectProps, DCOM, SPNTargets, PSRemote
2022-08-15T13:22:29.9130347+08:00|TRACE|Entering initialize link
2022-08-15T13:22:29.9130347+08:00|INFORMATION|Initializing SharpHound at 1:22 PM on 8/15/2022
2022-08-15T13:22:29.9130347+08:00|TRACE|Entering TestConnection link
2022-08-15T13:22:48.4446266+08:00|TRACE|[CommonLib LDAPUtils]Creating ldap connection for DC with filter (objectclass=domain)
2022-08-15T13:22:48.4446266+08:00|DEBUG|[CommonLib LDAPUtils]Unable to create ldap connection for domain (null)
2022-08-15T13:22:48.4446266+08:00|TRACE|[CommonLib LDAPUtils]LDAP connection is null for filter (objectclass=domain) and domain (null)
2022-08-15T13:22:48.4446266+08:00|ERROR|Unable to connect to LDAP, verify your credentials
2022-08-15T13:22:48.4446266+08:00|TRACE|Exiting TestConnection link

same here

Castle1984 · 2022-09-30T03:00:46Z

hmm，same issue
|ERROR|Unable to connect to LDAP, verify your credentials

asmar-shikhamirli · 2022-12-16T10:55:11Z

Having the same issue here, has anyone got a solution?

0nopnop · 2022-12-16T16:14:22Z

@rvazarkar any update on the issue and whether the changes have been made? I commented a while back (in Apr)

pkyria14 · 2023-07-07T09:33:30Z

Still having the same issue. any updates?

Trailingslashes · 2023-07-27T21:44:57Z

@pkyria14, I had to reboot the windows machine to get this command to work.

ProjectsFromB · 2024-01-12T17:58:16Z

Anyone have any luck or workarounds?

BaronSam3di · 2024-01-31T19:15:18Z

Hi im also getting this error. Specifically

*Evil-WinRM* PS C:\Users\FSmith\Documents> ./Sharphound.exe -c all, gpolocalgroup -v 0
2024-01-31T18:10:30.6811548-08:00|INFORMATION|This version of SharpHound is compatible with the 4.3.1 Release of BloodHound
2024-01-31T18:10:30.8217740-08:00|INFORMATION|Resolved Collection Methods: Group, LocalAdmin, GPOLocalGroup, Session, LoggedOn, Trusts, ACL, Container, RDP, ObjectProps, DCOM, SPNTargets, PSRemote
2024-01-31T18:10:30.8373984-08:00|TRACE|Entering initialize link
2024-01-31T18:10:30.8373984-08:00|INFORMATION|Initializing SharpHound at 6:10 PM on 1/31/2024
2024-01-31T18:10:30.8373984-08:00|TRACE|Entering TestConnection link
2024-01-31T18:10:58.9768518-08:00|TRACE|[CommonLib LDAPUtils]Testing LDAP connection for domain (null)
2024-01-31T18:10:58.9768518-08:00|TRACE|[CommonLib LDAPUtils]Creating ldap connection for DC with filter (objectclass=domain)
2024-01-31T18:10:58.9768518-08:00|DEBUG|[CommonLib LDAPUtils]Unable to create ldap connection for domain (null)
2024-01-31T18:10:58.9768518-08:00|WARNING|[CommonLib LDAPUtils]LDAP connection is null for filter (objectclass=domain) and domain Default Domain
2024-01-31T18:10:58.9768518-08:00|TRACE|[CommonLib LDAPUtils]Result object from LDAP connection test is null
2024-01-31T18:10:58.9768518-08:00|ERROR|Unable to connect to LDAP, verify your credentials
2024-01-31T18:10:58.9768518-08:00|TRACE|Exiting TestConnection link
*Evil-WinRM* PS C:\Users\FSmith\Documents>

Is this issue a dupe of something or should it be reopened if still unresolved 😌

JonasBK · 2024-01-31T19:53:43Z

Hi @BaronSam3di,
Try the latest SharpHound version here: https://github.com/BloodHoundAD/SharpHound/releases/latest

stuartw1 · 2024-03-18T15:45:54Z

I had this error message today. My target environment had 389 disabled and 636 open for LDAPS

I used the -SecureLDAP flag, but this didnt work and returned an "unable to connect to LDAP" error until I tried -DisableCertVerification and -DisableSigning, which made it work perfectly. Interestingly I had to provide domain, ldapusername and ldappassword too, with ldapusername set to user.name@internal.example.com rather than INTERNAL\user.name

Perhaps the error message could be expanded - either to include if it is a connection security fault, or to suggest trying flags that drop security validation measures if appropriate. It would be good if the logs contained the port that was being tried also.

vcap-kali · 2024-04-03T20:59:56Z

people are asking for workarounds, and I still observe this on HTB Sauna and Forest as of today, WHY is this issue closed then @JonasBK ?!

still getting the "ERROR|Unable to connect to LDAP, verify your credentials"

.\SharpHound.exe --DisableCertVerification --DisableSigning --Domain EGOTISTICAL-BANK.LOCAL --ldapusername svc_loanmgr --ldappassword '...'

superswan · 2024-04-08T01:59:52Z

Same issue with SharpHound 2.3.3 and 1.1.1

PS C:\Users\vim\Downloads\sharphound-v2.3.3> .\SharpHound.exe --version
2024-04-07T18:57:38.3685762-07:00|INFORMATION|This version of SharpHound is compatible with the 5.0.0 Release of BloodHound
SharpHound 2.3.3
PS C:\Users\vim\Downloads\sharphound-v2.3.3> .\SharpHound.exe -c localadmin
2024-04-07T18:58:44.0134919-07:00|INFORMATION|This version of SharpHound is compatible with the 5.0.0 Release of BloodHound
2024-04-07T18:58:44.1537624-07:00|INFORMATION|Resolved Collection Methods: LocalAdmin
2024-04-07T18:58:44.1699613-07:00|INFORMATION|Initializing SharpHound at 6:58 PM on 4/7/2024
2024-04-07T18:58:57.9663013-07:00|WARNING|[CommonLib LDAPUtils]Failed to setup LDAP Query Filter: Error creating LDAP connection: GetDomain call failed for
2024-04-07T18:58:57.9663013-07:00|ERROR|Error running SharpHound: Failed to setup LDAP Query Filter
   at SharpHoundCommonLib.LDAPUtils.<QueryLDAP>d__40.MoveNext()
   at System.Linq.Enumerable.<DefaultIfEmptyIterator>d__93`1.MoveNext()
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
   at SharpHoundCommonLib.LDAPUtils.TestLDAPConfig(String domain)
   at Sharphound.SharpLinks.TestConnection(IContext context) in D:\a\SharpHound\SharpHound\src\Sharphound.cs:line 148
   at Sharphound.Program.<>c__DisplayClass0_0.<<Main>b__1>d.MoveNext() in D:\a\SharpHound\SharpHound\src\Sharphound.cs:line 532
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CommandLine.ParserResultExtensions.<WithParsedAsync>d__20`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Sharphound.Program.<Main>d__0.MoveNext() in D:\a\SharpHound\SharpHound\src\Sharphound.cs:line 406

It appears to be a permissions issue, above output was ran as local admin user from console session. Runs fine as SYSTEM under remote shell.

nga1hte · 2024-04-11T18:18:48Z

people are asking for workarounds, and I still observe this on HTB Sauna and Forest as of today, WHY is this issue closed then @JonasBK ?!

still getting the "ERROR|Unable to connect to LDAP, verify your credentials"

.\SharpHound.exe --DisableCertVerification --DisableSigning --Domain EGOTISTICAL-BANK.LOCAL --ldapusername svc_loanmgr --ldappassword '...'

Resetting the machine works for me.

htinaunglu · 2024-04-14T23:16:52Z

people are asking for workarounds, and I still observe this on HTB Sauna and Forest as of today, WHY is this issue closed then @JonasBK ?!

still getting the "ERROR|Unable to connect to LDAP, verify your credentials"

.\SharpHound.exe --DisableCertVerification --DisableSigning --Domain EGOTISTICAL-BANK.LOCAL --ldapusername svc_loanmgr --ldappassword '...'

Came here for exact issue

k0rg · 2024-04-15T18:06:38Z

I had this error message today. My target environment had 389 disabled and 636 open for LDAPS

I used the -SecureLDAP flag, but this didnt work and returned an "unable to connect to LDAP" error until I tried -DisableCertVerification and -DisableSigning, which made it work perfectly. Interestingly I had to provide domain, ldapusername and ldappassword too, with ldapusername set to user.name@internal.example.com rather than INTERNAL\user.name

Perhaps the error message could be expanded - either to include if it is a connection security fault, or to suggest trying flags that drop security validation measures if appropriate. It would be good if the logs contained the port that was being tried also.

This is what worked for me: adding the two LDAP flags and changing the username from DOMAIN\username to username@domain.com

StavrosCaptain · 2024-07-30T09:22:51Z

If you have problem with Sharphound as above, do the following (example from sauna machine in HTB):

a) bloodhound-python -u svc_loanmgr -p '<PASSWORD>' -d EGOTISTICALBANK.LOCAL -ns 10.10.10.175 -c All
b) zip info.zip *.json
c) drag&drop the .zip file in BloodHound

To install bloodhound-python:
sudo apt install bloodhound
sudo pip install bloodhound-python

PurpleLinux · 2024-10-25T01:03:02Z

Just a quick note to anyone perusing, if you don't ad the -d <domain> flag, you will also get this error

rvazarkar closed this as completed Mar 7, 2022

slokie-so reopened this Apr 9, 2024

slokie-so added the bug Something isn't working label Apr 9, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to connect to LDAP, verify your credentials #10

Unable to connect to LDAP, verify your credentials #10

anasbousselham commented Feb 16, 2022

yellow-starburst commented Feb 17, 2022

anasbousselham commented Feb 17, 2022

rvazarkar commented Feb 17, 2022

x3rz commented Feb 19, 2022

gabemarshall commented Feb 24, 2022

lungdart commented Feb 24, 2022 •

edited

Loading

walterone commented Feb 28, 2022

rvazarkar commented Feb 28, 2022 •

edited

Loading

walterone commented Mar 1, 2022

rvazarkar commented Mar 2, 2022

YB1-cyber commented Mar 4, 2022 •

edited

Loading

rvazarkar commented Mar 7, 2022 •

edited

Loading

chinformer commented Mar 18, 2022

n0kovo commented Apr 16, 2022

chinformer commented Apr 19, 2022

rvazarkar commented Apr 19, 2022

ronemp commented Jul 6, 2022

mc702 commented Aug 15, 2022

Castle1984 commented Sep 30, 2022

asmar-shikhamirli commented Dec 16, 2022

0nopnop commented Dec 16, 2022

pkyria14 commented Jul 7, 2023

Trailingslashes commented Jul 27, 2023

ProjectsFromB commented Jan 12, 2024

BaronSam3di commented Jan 31, 2024

JonasBK commented Jan 31, 2024

stuartw1 commented Mar 18, 2024 •

edited

Loading

vcap-kali commented Apr 3, 2024

superswan commented Apr 8, 2024 •

edited

Loading

nga1hte commented Apr 11, 2024

htinaunglu commented Apr 14, 2024

k0rg commented Apr 15, 2024

StavrosCaptain commented Jul 30, 2024 •

edited

Loading

PurpleLinux commented Oct 25, 2024

Unable to connect to LDAP, verify your credentials #10

Unable to connect to LDAP, verify your credentials #10

Comments

anasbousselham commented Feb 16, 2022

yellow-starburst commented Feb 17, 2022

anasbousselham commented Feb 17, 2022

rvazarkar commented Feb 17, 2022

x3rz commented Feb 19, 2022

gabemarshall commented Feb 24, 2022

lungdart commented Feb 24, 2022 • edited Loading

walterone commented Feb 28, 2022

rvazarkar commented Feb 28, 2022 • edited Loading

walterone commented Mar 1, 2022

rvazarkar commented Mar 2, 2022

YB1-cyber commented Mar 4, 2022 • edited Loading

rvazarkar commented Mar 7, 2022 • edited Loading

chinformer commented Mar 18, 2022

n0kovo commented Apr 16, 2022

chinformer commented Apr 19, 2022

rvazarkar commented Apr 19, 2022

ronemp commented Jul 6, 2022

mc702 commented Aug 15, 2022

Castle1984 commented Sep 30, 2022

asmar-shikhamirli commented Dec 16, 2022

0nopnop commented Dec 16, 2022

pkyria14 commented Jul 7, 2023

Trailingslashes commented Jul 27, 2023

ProjectsFromB commented Jan 12, 2024

BaronSam3di commented Jan 31, 2024

JonasBK commented Jan 31, 2024

stuartw1 commented Mar 18, 2024 • edited Loading

vcap-kali commented Apr 3, 2024

superswan commented Apr 8, 2024 • edited Loading

nga1hte commented Apr 11, 2024

htinaunglu commented Apr 14, 2024

k0rg commented Apr 15, 2024

StavrosCaptain commented Jul 30, 2024 • edited Loading

PurpleLinux commented Oct 25, 2024

lungdart commented Feb 24, 2022 •

edited

Loading

rvazarkar commented Feb 28, 2022 •

edited

Loading

YB1-cyber commented Mar 4, 2022 •

edited

Loading

rvazarkar commented Mar 7, 2022 •

edited

Loading

stuartw1 commented Mar 18, 2024 •

edited

Loading

superswan commented Apr 8, 2024 •

edited

Loading

StavrosCaptain commented Jul 30, 2024 •

edited

Loading