nnposter
nnposter
Please re-run the scan with option `-d` and post the stack trace.
@CrypticGuru Your failed assertion is different from the OP. The issue is possibly the same as #3133, already rectified in Nmap 7.98.
Unfortunately the script is designed for SMB1 only.
@no1unorightnow The issue has been addressed by the patch referenced just before your message.
I believe that the current version of `mswin32/python-wrap.bat` will try to use Python from `%NMAPDIR%zenmap\bin` first anyway. What is the benefit of skipping the other locations? The syntax issue from...
If you run nmap with debug level 1 or higher then you will get an error message: ``` NSOCK ERROR [0.1770s] mksock_bind_addr(): Bind to 0.0.0.0:631 failed (IOD #5): Address already...
As a quick hack, you can replace `nsock_log_error` in the code quoted at the beginning of this issue with `fprintf(stderr,...`
Which specific script was trying to bind to 22/tcp?
I am not aware of any reason why a regular version scan should be binding to specific ports. Are you sure that you were not running `-sC` or some other...
I take it back. Scripts like `rpcinfo` would bind to a port and run during a version scan. Still, they should not be binding to random ports below 512. If...