3 posts in this topic
Hello everyone !
While writing a sample of code to test ping to my internet box, I got stuck..
While the code is Pinging with let say.. 5000ms of timeout, I need to update a progress bar from 0 to 5000 ms at the same time but I don't know how could I do this..
Is there a way or something that could get around the pause of the ping like in InetGet -> InetGetInfo?
i want a script that
"on the beginning of the program it pings to check if there is internet connectivity.
if there is internet connectivity
then it executes my code
else if there is no internet it waits at background to detected internet connectivity then executes my code."
Is this possible
Is there a way, preferably natively within AutoIt, to replicate:
ping -i 2 <nearby_IP>
The ping() function only has an option to set the timeout, but I want to set the TTL to 2 instead.
I want to check whether machine is up or not after we poweron a VM.
So to check that, I am using ping.
With the below command, when we run it, it will capture the value success or not with the errorlevel.
ping -n 1 sinra09-lod11 >nul: 2>nul: so we can track the return code back using below.
echo %errorlevel% So it is able to return the 1 when it is failure and 0 when it is success.
But when I convert the above commands to AutoIT, the return code is always giving 0 even on failure.
MsgBox(0,pingCheck("sinra09-lod11"),"sinra09-lod11") Func pingCheck($system_name) ;$system_name = "sinra09-lod1" $command = @SystemDir&"\ping.exe -n 1 "& $system_name & " >nul: 2>nul:" ConsoleWrite($command) Local $iReturn = RunWait($command) ;MsgBox(0,$system_name,$iReturn) ConsoleWrite($iReturn) if $iReturn = 0 then Return True Else Return False EndIf EndFunc Please suggest..
I have a rather strange issue on some machines.
If I attempt to use the inbuilt PING function, no ICMP packet is sent out.
Ping("internal.fqdn.com") is returning "Host Unreachable"
If I ping using the command prompt, it's all fine.
Using wireshark I can see that it hasn't even attempted an ICMP request. I can see it has looked up DNS to check for the correct IP address (I can see reply packet returns 10 different IP address as round robin - which is expected), but then it simply doesn't send the request.