Printable View
Hi, i have a LAN at my house, and i was wondering if there was a command in DOS that would let me see all the IPs of every individual computer that is on my network. I only have 3 computers. All of them connect through a Router. And I have file sharing enabled. Any answers would be appreciated. :)
well you could look at the router interface and find out that way, or you can goto each individual computer and type "ipconfig"... if you would like to access shared resorces you can always click on "network naborhood" (if you are using windows)... as far as a DOS command i am not awaire of one....
a port scanner is always a good option as well...
one way to make it a little easyer is to use the DHCP service on your router to give each of your computers a static IP address..... if you need help doing this please ask....
A quick way can be to use the ping broadcast. e.g., if you are using 192.168.1.x for an ip range then do ping -t 192.168.1.255. After about 15-20 seconds hit CTRL+C to stop it and then arp -a to see a listing.
MsM: A windows machine doesn't respond to a broadcast ping (by default). No machine should reply. If it did his network would be susceptible to a smurf attack...
http://www.cert.org/advisories/CA-1998-01.html
Since you're using a broadcast the layer 2 address would be ff:ff:ff:ff:ff:ff. Because none of the machines should respond your arp table will remain empty.
Hi, "net view" should give you a list of computer names. You can then find their IP addresses easily... I'm not sure on which Windowses the command is available. Also, my box/network is so "secured" that net view doesn't work.
If you have a W2K/XP box, a brute force solution can be used:
for /L %i in (1,1,254) do ping -n 1 192.168.1.%i
::while waiting the for loop completes, you can see which IP is responding
arp -a
Peace always,
<jdenny>
Ok, i'll try all of those commands... and devildell, i dont want to get up and go to every individual computer and look up their IP... thanks anyway...
jdenny?: for /L %i in (1,1,254) do ping -n 1 192.168.1.%i < that was pretty cool, it said bad parameter for all of them though. net view only gives me the computer names not their IPs.
msmittens?: if i didn't ]know my IP range (eg. 192.168.1.x) how would i look up the ips connected in my network?
Really? What's your win version? Can you post the detailed message?Quote:
jdenny?: for /L %i in (1,1,254) do ping -n 1 192.168.1.%i < that was pretty cool, it said bad parameter for all of them though.
Do a "ping computer_name" for each of them... If you have NetBIOS over IP or NetBeui enabled, it should work.Quote:
net view only gives me the computer names not their IPs.
Peace always,
<jdenny>
Sure jdenny this is how it looks like :
Bad parameter 155.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 156
Bad parameter 156.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 157
Bad parameter 157.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 158
Bad parameter 158.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 159
Bad parameter 159.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 160
Bad parameter 160.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 161
Bad parameter 161.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 162
Bad parameter 162.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 163
Bad parameter 163.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 164
Bad parameter 164.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 165
Bad parameter 165.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 166
Bad parameter 166.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 167
Bad parameter 167.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 168
Bad parameter 168.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 169
Bad parameter 169.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 170
Bad parameter 170.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 171
Bad parameter 171.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 172
Bad parameter 172.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 173
Bad parameter 173.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 174
Bad parameter 174.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 175
Bad parameter 175.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 176
Bad parameter 176.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 177
Bad parameter 177.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 178
Bad parameter 178.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 179
Bad parameter 179.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 180
Bad parameter 180.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 181
Bad parameter 181.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 182
Bad parameter 182.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 183
Bad parameter 183.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 184
Bad parameter 184.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 185
Bad parameter 185.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 186
Bad parameter 186.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 187
Bad parameter 187.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 188
Bad parameter 188.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 189
Bad parameter 189.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 190
Bad parameter 190.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 191
Bad parameter 191.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 192
Bad parameter 192.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 193
Bad parameter 193.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 194
Bad parameter 194.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 195
Bad parameter 195.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 196
Bad parameter 196.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 197
Bad parameter 197.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 198
Bad parameter 198.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 199
Bad parameter 199.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 200
Bad parameter 200.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 201
Bad parameter 201.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 202
Bad parameter 202.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 203
Bad parameter 203.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 204
Bad parameter 204.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 205
Bad parameter 205.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 206
Bad parameter 206.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 207
Bad parameter 207.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 208
Bad parameter 208.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 209
Bad parameter 209.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 210
Bad parameter 210.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 211
Bad parameter 211.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 212
Bad parameter 212.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 213
Bad parameter 213.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 214
Bad parameter 214.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 215
Bad parameter 215.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 216
Bad parameter 216.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 217
Bad parameter 217.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 218
Bad parameter 218.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 219
Bad parameter 219.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 220
Bad parameter 220.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 221
Bad parameter 221.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 222
Bad parameter 222.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 223
Bad parameter 223.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 224
Bad parameter 224.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 225
Bad parameter 225.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 226
Bad parameter 226.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 227
Bad parameter 227.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 228
Bad parameter 228.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 229
Bad parameter 229.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 230
Bad parameter 230.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 231
Bad parameter 231.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 232
Bad parameter 232.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 233
Bad parameter 233.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 234
Bad parameter 234.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 235
Bad parameter 235.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 236
Bad parameter 236.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 237
Bad parameter 237.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 238
Bad parameter 238.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 239
Bad parameter 239.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 240
Bad parameter 240.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 241
Bad parameter 241.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 242
Bad parameter 242.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 243
Bad parameter 243.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 244
Bad parameter 244.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 245
Bad parameter 245.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 246
Bad parameter 246.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 247
Bad parameter 247.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 248
Bad parameter 248.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 249
Bad parameter 249.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 250
Bad parameter 250.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 251
Bad parameter 251.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 252
Bad parameter 252.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 253
Bad parameter 253.
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 254
Bad parameter 254.
Hopefully the message isnt to long.
Is it supposed to look like that ?
Dangit, that was to long, sorry about that...
Hi
Create a bat-file and put the following code in it
This should run, as well as Jdenny's command works exactly as it should,Code:for /L %%i in (1,1,254) do ping -n 1 192.168.1.%%i
in the command prompt.
Did you forget the dot before %i? What is your OS?
Cheers.
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... :)
You forgot the dot between 192.168.1 and %i.Quote:
Originally posted here by kyrios
C:\Documents and Settings\Kyri0s>ping -n 1 192.168.1 156
Bad parameter 156.
Code:for /L %i in (1,1,254) do ping -n 1 192.168.1.%i