Binding to host error (adidnsdump) about linwinpwn HOT 6 CLOSED

Hello,
From the error message, it seems like you're using ldaps instead of ldap (i.e. port 636 instead of 389). Did you specify the parameter --ldaps with linWinPwn?
Also, are you sure to be using the latest version of adidnsdump?

from linwinpwn.

Hello lefayjey,

Thanks for the quick respond.

Yes, i also tried it with --ldaps parameter. Same problem.

adidnsdump is also on the latest version.

Br!

from linwinpwn.

If you run the command adidnsdump followed by the same IP, do you have the same error?

The issue can be related to adidnsdump, or the target IP could be blocking the connection or just doesn't have the LDAP ports open

from linwinpwn.

Yes.

im connected to LAN.

I tried the bloodhound python script and it worked, so i think its something with adidnsdump.

Do you know how bloodhound bind to hosts ?

Br!

from linwinpwn.

If the issue is with adidnsdump, then it's not related to linWinPwn, and I can't really help you with that. Even if adidnsdump fails, you can still use most checks of linWinPwn.
I've also just added an open port check to help identify which relevant ports are open on the target

from linwinpwn.

I'm going to close this issue since it seems to be related to another tool. I'll keep the comments on in case you need more assistance on that.
Thanks

from linwinpwn.