-
Notifications
You must be signed in to change notification settings - Fork 235
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
failure while searching for PORT #56
Comments
Hello, which version of Nmap did you use for the results.txt output? Did you use any special command-line switch options for running Nmap? |
Hello, I'm using nmap version 7.70
|
I'm still facing this issue, I didn't have much time lately to tackle with it, the commands seem right. |
ithilgore
added a commit
that referenced
this issue
Jun 6, 2019
Just fixed it with b8efea7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting this issue when running a scan for hosts discovered via nmap.
The only possible reason might be because I said -oN result.txt instead of -oN result.
Altho I'm not even sure that's relevant, couldn't find any info on it.
The text was updated successfully, but these errors were encountered: