How do I find the IP address of a device attached to my network?
It's like this - I have a linux-based machine attached to my computer. My network does not detect it, the only way I could FTP from my Windows PC to my Linux is by looking up the IP address on the Linux and connecting via FlashFXP on my Windows. The Linux has a problem and I cannot look up the IP address from the LInux. I use a Router, so I know the IP is somewhere in the 192.168.0.100 - 192.168.0.700 range because that is how I set up the DHCP. So I want to use my WinPC to scan my network for this machine so I can fix it via FTP by deleting what I believe to be is a virus in the Linux Machine. I believe the Linux NIC is working because my router activity light goes on when the LInux Machine is turned on, and even blinks which indicates activity. So how can I scan my network for this machine? Windows will not work, I've tried. What other program scans for this type of thing? I can ONLY access my linux computer via my networked Windows PC. Any Linux programs suggested would be a bad answer for this question. OK, since everyone here is so smart, let me clarify. Something is wrong with the Linux Machine. The IP address a VIRTUAL domain. i.e., you can set up the ports without them actually being there. A file was loaded onto the Linux machine. The machine crashed, and doesn't boot all the way. THEREFORE, since I can get in via FTP, I can go back and delete the file loaded- simple as that. It may have been an error in loading, or it could actually be a virus - Linux isn't bulletproof you know. So maybe you should try reading the question before answering instead of assuming everyone is dumber than you. Typical Linux Geek . . .
Public Comments
- Have you downloaded Samba for linux? Not a big windows users but don't you have to enable fileand printer sharing somehow first?
- There are many good network scanners that can be used for this purpose. Two very good ones are: a) nmap (http://insecure.org/nmap/download.html): Install this on any computer in the network and scan the 192.168.0.100 - 192.168.0.700 range. It will show you all the live IPs. This has be run from the command line: nmap -sS 192.168.0.100-700 b) SuperScan (http://www.softpedia.com/get/Network-Tools/Misc-Networking-Tools/SuperScan.shtml): This serves the same purpose as nmap, except it is a windows program with a nice interface.
- I think the way to find an Ip adress is to first off see if the linux computer will tell you, I haven't worked with linux so I don't know, and if that doesn't work you will have to use a windows computer and just type in 192.168.1.1 and if your router has a password enter it when necessary (not WEP code). then on the router's setup page, somewhere in there you will find a link linking you to the DHCP client table click on that and it will list all of the Ip adresses used. oh and by the way it would 192.168.1.100 - 192.168.1.255 because 255 is the maximum for an ip adress column (in between the dots). Due to the conversion from a 2 base numbering scale (binary code) to a 10 digit based numbering scale, and since the codes are written in 16bit format 255.255.255.255 would be the maximum and would be written in binary like this: 1111111111111111 and 0.0.0.0 would be written like 0000000000000000 and certain ip adresses are reserved for certain uses.
- For a start the IP range you quote is totally wrong, IP addresses can not include numbers higher than 255 in any octet, and no more than 254 in the last, so a number of 700 is totally impossible. Secondly, it is almost impossible to have a virus in the Linux machine. If your Linux box is et up correctly it can give Windows type broadcasts, or could even be used to serve the dhcp and the router dhcp can be turned off. The Ip address of the box would then need to be set manually. It can also be used as a local dns server. Thirdly, ftp can not be used to fix or control anything. It is only a file transfer system, (file transfer protocol is it's name). I would advise you to read up on networking before you totally trash your system.
