• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discovering other IP's of other Workstations...

Poontos

Platinum Member
Out of the box, is there a way in Windows 2000 to discover what the IP's of other workstations in your LAN are?

Or the NetBIOS name of the other machine? How about a table listing the computers in the LAN? And what about shares?

Thanks!
 
A scanner would do all of that. IP's open ports per IP, etc. Some of them will even draw a diagram of the network based on the scan. Be aware that alot of scanners only work on the local subnet.
If you have access to the snap in, you could always connect to the DHCP server via the MMC snap-in.
It would have a list of every IP leased out, and the name of the computer currently holding the lease.
 


<< A scanner would do all of that. IP's open ports per IP, etc. Some of them will even draw a diagram of the network based on the scan. Be aware that alot of scanners only work on the local subnet.
If you have access to the snap in, you could always connect to the DHCP server via the MMC snap-in.
It would have a list of every IP leased out, and the name of the computer currently holding the lease.
>>


Thank you for the response.

Now with the MMC snap-in... this would be valid if I was running DHCP on a Win2K server? My laptop is the only node on the network that uses DHCP, and it receives its IP from my Netgear RT314.

Still curious...
 
Best bet is to scan the whole subnet with something like nmap.

For something less intrusive you could setup a rarp server, but it would have to sit for a while to generate a full table from watching ARP requests.
 
Also note that if you are connected to a switch, you'll only see broadcasts from machines on the other ports. Since ARP is a broadcast, you should still see the other machines as they look for IP to MAC translation or Netbios names. You won't see any of the regular data traffic though, if you were interested in seeing that.


FWIW

Scott
 


<< Also note that if you are connected to a switch, you'll only see broadcasts from machines on the other ports. Since ARP is a broadcast, you should still see the other machines as they look for IP to MAC translation or Netbios names. You won't see any of the regular data traffic though, if you were interested in seeing that.


FWIW

Scott
>>


I guess my Netgear RT314 broadband router is technically a 10/100 switch too.

Basically, I am looking for the tool that (I guess Windows 2K don't have) will allow me to find out at least the IP addresses of the other workstations in my LAN. I realize that I could it many other ways, however, that wouldn`t resolve my situation.

An example of this in the Windows world, would be Network Neighbourhood... were it lists all the computers (setup correctly) in your LAN, with there NetBIOS names... I am looking for an equivalent of this for IP addresses of workstations in my LAN.


Tanks
 
I see... although I do not have a non-Windows computer at this time to install Nmap on.

I just chose nmap because I like it and it's the first one that comes to mind. I'm sure there are port scanners for Windows that can do whole networks, and even if there isn't I know nmap has been ported to Windows, I don't have a link but I know I've seen it before.

An example of this in the Windows world, would be Network Neighbourhood... were it lists all the computers (setup correctly) in your LAN, with there NetBIOS names... I am looking for an equivalent of this for IP addresses of workstations in my LAN.

The reason you get that list is because there's a browser out there with a list of the computers (or you're using WINS which is sorta the same thing) because as they came up they found the master browser for their network and registered with him. IP has nothing like this because it wasn't meant to be "browsed", DHCP is probably the closest thing like Saltin mentioned.
 
Back
Top