search

lefayjey / linWinPwn

linWinPwn is a bash script that streamlines the use of a number of Active Directory tools
MIT License
1.8k stars 264 forks source link

Binding to host error (adidnsdump) #11

Closed user987429837429834 closed 1 year ago

user987429837429834 commented 1 year ago

Hello Guys,

when i try to start and connect with linWinPwn i get the following error from adidnsdump.

my command: ./linWinPwn -t -u -p --auto-config

Screenshot_2023-02-09_09-51-56

lefayjey commented 1 year ago

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?

user987429837429834 commented 1 year ago

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!

lefayjey commented 1 year ago

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

user987429837429834 commented 1 year ago

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!

lefayjey commented 1 year ago

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

lefayjey commented 1 year ago

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