LAN IP's

[Phantom Wolf]

When I want connceted IPs on the windows command line I just use:

Code: Select all

arp -a

That's only going to work if your computer has made contact with every computer on the local network. ARP requests don't go out until they're needed.

I still think going to your router's configuration is the best idea, but some routers only list DHCP clients.

Yeah, that would work also, but the reason I only went to 99 is that I doubt that the OP has more than 99 computers on his network, and so searching the whole 255 addresses would be pointless.

Yeah, but there could be computers on his network using higher addresses regardless. For example, just because 192.168.2.2 is open, that doesn't mean that a computer might take 192.168.2.150.

[mShred]

Yeah, but there could be computers on his network using higher addresses regardless. For example, just because 192.168.2.2 is open, that doesn't mean that a computer might take 192.168.2.150.

Really? Why wouldn't the computer just take that first one. I've never heard of it not. But i suppose you learn something new every day.

[Phantom Wolf]

Really? Why wouldn't the computer just take that first one. I've never heard of it not. But i suppose you learn something new every day.

Well, if there's clients that don't have/want to use DHCP for some reason, they may take a high address to lessen the risk of 'stealing' someones IP. Some DHCP servers won't re-lease addresses for a very long time, causing it to give out high addresses even though the lower ones are free.

Also, I've heard of people configuring their clients to turn down the first few addresses. Some servers will completely abandon an address if it gets turned down, so someone looking to cause problems can exhaust a server's address space.

However, they almost always take the first one.

[RevengeDriven]

Are you using XP? Why not use Look@LAN? It works only with XP and not Vista but will tell you what DHCP clients are logged online, their distance, their hostname and other useful things.

Code: Select all

http://web.volftp.tiscali.it/pub/pc/windows/win98/progs/network/tcpip/lalsetup250.exe

[LoGiCaL__]

nmap -sP 192.168.1.* is the way to go. Check you default gateway as the 1 may be a 2.

It will list them all nice and neat.

Well, if there's clients that don't have/want to use DHCP for some reason, they may take a high address to lessen the risk of 'stealing' someones IP. Some DHCP servers won't re-lease addresses for a very long time, causing it to give out high addresses even though the lower ones are free.

Personally I use the first few available IP's for which ever device happens to turn on and choose one. For my development server I purposely make a static IP over the .100 range. No real reason, just a convention I like to use with static ip's.

[mango_leech]

For Ping Sweeping apart from awesome "nmap" you can try "fping" too....
For Example :: In a typical LAN following does a Ping Sweep

Code: Select all

fping -a -g 192.168.1.1 192.168.1.254 2>/dev/null


For a LAN using mainly Windows Network can try "nbtscan" to query the NetBios Name service

Code: Select all

nbtscan  192.168.1.1-254 

Hope it helps!