Skip to content
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

Closed
noleaknaynay opened this issue May 24, 2019 · 4 comments
Closed

failure while searching for PORT #56

noleaknaynay opened this issue May 24, 2019 · 4 comments

Comments

@noleaknaynay
Copy link

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.

root@kali:~# ncrack -v -U usr.txt -P pw.txt -T5 -iN result.txt                                                   
                                                                                                                   
Starting Ncrack 0.6 ( http://ncrack.org ) at 2019-05-24 22:11 CEST                                                   │
                                                                                                                     
-iN fgets failure while searching for PORT                                                                   
                                                                                                                   
QUITTING!
@ithilgore
Copy link
Collaborator

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?

@noleaknaynay
Copy link
Author

noleaknaynay commented May 25, 2019

Hello, I'm using nmap version 7.70
Here's a block out of the result.txt

# Nmap 7.70 scan initiated as: nmap -p 3389 -n -iL ranges.txt -oN result.txt
Nmap scan report for xxx.xxx.xxx.208
Host is up (0.0061s latency).

PORT     STATE  SERVICE
3389/tcp closed ms-wbt-server

Nmap scan report for xxx.xxx.xxx.209
Host is up (0.0061s latency).

PORT     STATE  SERVICE
3389/tcp closed ms-wbt-server

Nmap scan report for xxx.xxx.xxx.210
Host is up (0.0061s latency).

PORT     STATE  SERVICE
3389/tcp closed ms-wbt-server

@noleaknaynay
Copy link
Author

noleaknaynay commented Jun 6, 2019

I'm still facing this issue, I didn't have much time lately to tackle with it, the commands seem right.

@ithilgore
Copy link
Collaborator

Just fixed it with b8efea7
Should be working now on latest github version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants