Sign in to follow this  
Followers 0
RichardL

AutoIt ping fails, but cmd> ping succeeds. -Fixed in AutoIt 3.3.10.2

4 posts in this topic

#1 ·  Posted (edited)

Hi,

I'm using ping to check network availability at work. The example from help (almost) does not work, similarly using the IP address. Both fail with error = 1 = Host Offline.

Ping("www.AutoItScript.com")
Ping("208.87.35.103")

Within a corporate/domain environment, you might expect some things to be blocked, but the strange thing is that from a cmd prompt, pinging those addresses is successful. Similarly www.google.co.uk fails from AutoIt ping, but is alright from cmd. Internet access is permitted, and Firefox can go to AutoIt and Google. (I tried another computer at work, same.) With the same computer, on WiFi at home, both ping methods succeed.

How is the corporate environment blocking AutoIt ping, but not cmd ping?

Richard.

Edited by RichardL

Share this post


Link to post
Share on other sites



Hey, maybe

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

The way AutoIT forms it's ping packet is not quite to IEEE standards so a lot of router configs and intrusion detection/prevention systems will block it vs the properly formated one Windows PING uses.

Ah, Rob beat me to it. ;-) And yes that thread he mentioned is exactly why with a nice alternative UDF one of our amaizing peers created. Gotta love these forums! :)

Edited by EnigmaV8

Share this post


Link to post
Share on other sites

@Robjong, @EnigmaV8

Yes, that's it. Agree, there's always a good chance that someone's done/fixed it before.

Thanks,

Richard.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0