"Error in consumer" when connecting to LDAP server with SH v2.5.x

[jaredbarez]

There is some change that was introduced in branch 2.5.x that now prevents SH to contact LDAP server (i.e. DC) of target domain for collection. Please look into screenshots:

SharpHound 2.5.1 (throws "error in consumer" "The LDAP server is unavailable"), which is release immediately after older 2.4.1:

SharpHound 2.4.1 (works fine):

SharpHound 2.5.7 (the latest one in the moment of reporting the issue, also throws the same error):

In all three tries I am trying to connect to the same LDAP server (i.e. the SH parameters are the same) and the security context of the user is the same (PS CLI is started as "runas /netonly" with domain user context on standalone Windows machine with the DNS servers pointing to DC's of the target domain which are running the DNS service).

Any clues ?

[rvazarkar]

This is cool, cause I've actually never seen this exception before. Stuff always gets a bit screwy in netonly, but I'm pretty sure I know where this error is coming from. The cool part is, the .net docs don't actually say its possible to have an exception in the constructor of this particular function. Will add a ticket for it

[svenhertle]

I just had the same issue and can confirm that the fix works.

I used SharpHound with the --ldapuser and --ldappassword parameters on a standalone machine.

Thank you!

[gumbyDE]

Can also confirm that the issue is fixed with the change. I was also running the collector with runas /netonly.
Any idea when this fix will make it into the release version?