Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
JacksonAlfonso
Creator
Creator

Retorno de comando "Ping" (Return the command "Ping")

Olá pessoal !

Alguem ja fez alguma aplicação que enviasse um comando ping para um endereço de rede, e capturou a resposta, mostrando com uma imagen ou texto se houve ou não comunicação com o ip enviado ?!

Obrigado.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello everybody!

Has anyone made ​​any application to send a ping command network address, and captured the response, showing with an image or text whether or not communication with the ip sent!

Thanks !!!

1 Reply
evan_kurowski
Specialist
Specialist

Hello Jackson,


Yes, I had done some of these.  Essentially by "brute force" inquiries, making a crude QlikView webcrawler.  I switched from ping to nslookup because the response time was quicker (even with 1 packet) and the information returned about the machine name was more useful than just the ping response.


So the attached application is in parts because I never get to finish it (and not sure if I really need to), and as time goes on there seems to be less useful info in the nslookup messages returned because the machines are either getting redirected, or named in ways that don't reveal anything identifiable.

Also, as shift moves over to IPv6, not sure if brute force would ever be on the table again.  I calculated that on ordinary desktops about 30 pc's could cover the full scan of IPv4 in maybe a months time, but then again.. my math isn't braggable.

Someone has pointed out to me that there are many other programs that perform this functionality already, like Nmap and Portmon that already have mature interfaces.  I suppose as long as no one develops and enhances an approach toward different techniques for QlikView, things will always remain that way.

The first component Spidey is going to create .BAT scripts that basically brute-force iterate across an 255.255.0-255.0 - 255 range.  The resulting nslookup commands generated for your .BAT files should be 65,536 (or 256*256 or 2^16), but it takes a long time to do a whole subip 3 segment on an ordinary desktop.  A server on a corporate network will pump through in maybe a quarter of the time (10min vs. hour?). I would start with doing only 256 ip addresses at a time.

The last step of the Spidey component (Step 1) is the .BAT file is executed and the results will begin filling up folders with the result of a single request output per file.

..\nslookup\75_45\3_14.dat  altogether represents the nslookup output from the ip address 75.45.3.14.

Then the second .QVW Collator (Step 2) will pass through all the .dat output and collate them into a place where you can review all the collected information.  Sorry it is in such disarray but... 😕