invictus@victim_server:~$ nmap -T4 -0 10.10.0.0/24
TCP/IP fingerprinting (for OS scan) xxxxxxx xxxxxx xxxxxxxxx. QUITTING!
Obviously, it is not going through. What is the issue here?

A.
OS Scan requires root privileges
B.
The nmap syntax is wrong.
C.
The outgoing TCP/IP fingerprinting is blocked by the host firewall
D.
This is a common behavior for a corrupted nmap application
Answer: B The NMAP syntax is wrong.
Option for OS scan is -O (the letter) not -0 (the number).
Unless it’s actually the letter ‘O’, then A is correct.
In the syntax following the command, it says “TCP/IP fingerprinting (for OS scan)”. The fact is says “for OS Scan” means it did take as a OS scan. EC-Council would not try that hard to trip you up.
If you’ve run an OS NMAP scan, you’ll see that you need to put ‘SUDO’ infront, or you get that QUITTING message. Answer is A
Nmap will not quit with -0
nmap will quit with -O.
A
I doubt EC Council would try that hard to trip you up, by switching a Zero with the letter “O”. Plus the fact that you can see in the scan.. ” TCP/IP fingerprinting (for OS scan)”, it says “For OS Scan” which means it did register it as an proper OS Scan.
you must put ‘Sudo” in front of the syntax, and provide password for user you are using.