-
Notifications
You must be signed in to change notification settings - Fork 265
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
Binding to host error (adidnsdump) #11
Comments
Hello, |
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! |
If you run the command 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 |
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! |
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'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. |
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
The text was updated successfully, but these errors were encountered: