Issue with NMAP using the -sI command

[Z3R0C00]

when Im trying to run a zombie scan using an idle machine with the ip of 10.0.0.10, to scan the ip of 10.0.0.31, I get some odd errors.

Here's the command I'm using: nmap -PN -sI 10.0.0.10 10.0.0.31 * exec: nmap -PN -sI 10.0.0.10 10.0.0.31

which gives me a bunch of errors like this

Failed to resolve given hostname/IP: plugins. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: README. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: scripts. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: test. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges

etc etc etc.......
Im new so take pity on me

Thanks

[promark]

when Im trying to run a zombie scan using an idle machine with the ip of 10.0.0.10, to scan the ip of 10.0.0.31, I get some odd errors.

Here's the command I'm using: nmap -PN -sI 10.0.0.10 10.0.0.31 * exec: nmap -PN -sI 10.0.0.10 10.0.0.31

which gives me a bunch of errors like this

Failed to resolve given hostname/IP: plugins. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: README. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: scripts. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges
Failed to resolve given hostname/IP: test. Note that you can't use '/mask' and '1-4,7,100-' style ip ranges

etc etc etc.......
Im new so take pity on me

Thanks

Not sure if the * is valid but from the error nmap seems to think you are trying to use it as a wildcard and IP ranges are not allowed also not sure what -PN option is supposed to do but try without it and add -v or -vv for verbose output may help to diagnose it

[Gitsnik]

The * is mapping out the local files:

bash-3.2$ ls
cleanup insecurity stealth
bash-3.2$ echo *
cleanup insecurity stealth
bash-3.2$

Which is where your problem appears to be arising:

bash-3.2$ echo 192.168.1.*
192.168.1.*
bash-3.2$

Works fine, however, because it is not a * character on its own.

And yes, * is valid in nmap, but it should be attached somewhere (nmap *.10.23.11 will scan every IP that matches: 1.10.23.11 2.10.23.11 3.10.23.11 and so on... not a good idea).

The giveaway is the hostnames having what look like filenames in them. Should have been your first indicator