-
NOTE: This is not a native "dos" command. You can, however, run it from a command line interface or "dos" as you call it.
get nmap from www.insecure.org
If all machines respond to icmp echo/echo-reply, then you can do a ping scan.
<aka> ping sweep
using nmap...
nmap -sP 192.168.1.0/24
That will ping each ip and report back if a host is alive or dead...
NOTE: You can also combine this with -vv (verbose) to get more info.
This will only work IF the hosts in question respond to ICMP echo/echo-reply.
If not, then you can try other scans... without the ping option.
nmap -sV -O -P0 -vv 192.168.1.0/24
That will probe the computers and try to determine which services and operating system it is running. The -P0 tells it not to ping... or ignore host discovery.
nmap -sS -vv -P0 192.168.1.0/24
that will syn scan with verbose info without host discovery.
Check out the nmap man file or help file for more combinations.
You will need WINPCAP if you're using the win32 nmap binary.
-
sec_ware... I have Win XP Pro SP2. and
/*******************************************
for /L %%i in (1,1,254) do ping -n 1 192.168.1.%%i **
*******************************************/
that came up with this
/*********************************************
C:\>for /L %%i in (1,1,254) do ping -n 1 192.168.1.%%i
%%i was unexpected at this time.
*********************************************/
PhishPhreak... I installed WINPCAP, and nmap still doesnt work...???
-
Hi kyrios
batch file
If you type the for-scan in the command line, you have to use "%i".
If you create a batch-file and start that one, you have to use "%%i".
nmap
The nmap version I occasionally use, on a no-service pack Windows XP,
is 3.75, using the WinPcap 3.0. I also realised now that nmap 3.81 with the 3.1 beta 4
crashes when pinging an unexisting IP (which happens when you perform
a ping scan). I don't know whether this is a known issue.
Cheers.
/edit: to fit phishphreek80's notation:
nmap -sP 192.168.0.254 works and is up
nmap -sP 192.168.0.1 gives an "Application error: memory could not be "read"" on XP pro, some updates
nmap -sP 192.168.0.0/24 gives an "Application error: memory could not be "read"" on XP pro, some updates
However, I just noted that the scan itself actually is performed, ie showing some
machines which are up, if I do not terminate nmap. Confused.
-
haha! How about that. It does crash... hmmm...
Sorry, I didn't test it at the time of writing the post... just went from past experience.
It will allow you to ping individual hosts if they are there or not... seems to have a problem as soon as you add the subnet... which is why you'd want to use the -sP option. bugger.
Using nmap 3.81 with the winpcap 3.1beta4 drivers...
nmap -sP 192.168.1.1 works and is up
nmap -sP 192.168.1.2 works but is down
nmap -sP 192.168.1.0/24 gives me an interface error on xp pro sp2 all updates
nmap -sP 192.168.1.0/24 gives me time errors on 2k sp4 all updates
-
ok, well thanks for the help guys... :)
-
Quote:
Originally posted here by kyrios
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 156
Bad parameter 156.
You forgot the dot between 192.168.1 and %i.
Code:
for /L %i in (1,1,254) do ping -n 1 192.168.1.%i
