austoonz
Unsuccessful ping is still low
Using fastping against a list of computers is fast - if they are pingable - but still slow (3-4 seconds) if they are not.
At the end of the day when 80% of the users are out of the office, I'm still waiting for 75% of the computers to fail before FastPing returns.
The command and options I'm using are: fastping pcname -count 1 -timeout 50
If you want to reproduce the issue, create an array of online devices and add 60 random names. Then iterate through the list.
I'm guessing its due to this, which was added to prevent a different issue (when the first host in a list of hosts doesn't resolve DNS, I saw other issues).
If you want to comment that out in your local module folder and let me know if that speeds it up for you? I can add a switch to prevent this attempt to resolve the DNS name if that's your issue, or skip this for the n+1 host in the list.
Yes – that does help.
However…If I want to avoid DNS lookups – then probably should not feed a list of DNS names, 70% of which will not be resolveable…
Lol – sorry about that – your changes made it 50% faster – my DNS Name submission is responsible for the remaining delay. It is very fast when I use IP only and then resolve the successful IPs.
Thanks for your help.
Thomas Beardshear Ph.949-261-9222 x218 From: Andrew Pearce @.> Sent: Saturday, March 25, 2023 5:02 PM To: austoonz/FastPing @.> Cc: Mckadmin @.>; Author @.> Subject: [EXTERNAL] Re: [austoonz/FastPing] Unsuccessful ping is still low (Issue #3)
I'm guessing its due to thishttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_austoonz_FastPing_blob_master_src_FastPing_Public_Invoke-2DFastPing.ps1-23L142&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=YTfOXjyQ8rY60WaGEb0CqB7FRpp2ik4yKjn9ZT9Odzw&e=, which was added to prevent a different issue (which I can no longer recall what it was).
If you want to comment that out in your local module folder and let me know if that speeds it up for you? I can add a switch to prevent this attempt to resolve the DNS name if that's your issue.
— Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_austoonz_FastPing_issues_3-23issuecomment-2D1483951186&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=Mki6HFfHBh5ZcWyIv9_WQoijMq4ivgbQFBNJzxk8mEA&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AH2VJG2FBTL5Y4Z4Y4MN6YLW56BNVANCNFSM6AAAAAAWHHDQ7U&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=vCbMwf_GEtSnzjipbrBrgTjCvC3GzOuNJtFz1NGS4Lw&e=. You are receiving this because you authored the thread.Message ID: @.@.>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
I just rewrote my script to use Pingsweep and then resolve the returned successful entries. It is much faster. I used to write a list to a file and then only rerun the query every 180 minutes so that other powershell sessions in other dos windows could use the list but not have to wait for the query.
It’s so fast now – I can remove the wait time.
Thanks for a great app. Well done!
Thomas Beardshear Ph.949-261-9222 x218 From: Thomas Beardshear Sent: Tuesday, March 28, 2023 2:16 PM To: austoonz/FastPing @.>; austoonz/FastPing @.> Cc: Mckadmin @.>; Author @.> Subject: RE: [EXTERNAL] Re: [austoonz/FastPing] Unsuccessful ping is still low (Issue #3)
Yes – that does help.
However…If I want to avoid DNS lookups – then probably should not feed a list of DNS names, 70% of which will not be resolveable…
Lol – sorry about that – your changes made it 50% faster – my DNS Name submission is responsible for the remaining delay. It is very fast when I use IP only and then resolve the successful IPs.
Thanks for your help.
From: Andrew Pearce @.@.>> Sent: Saturday, March 25, 2023 5:02 PM To: austoonz/FastPing @.@.>> Cc: Mckadmin @.@.>>; Author @.@.>> Subject: [EXTERNAL] Re: [austoonz/FastPing] Unsuccessful ping is still low (Issue #3)
I'm guessing its due to thishttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_austoonz_FastPing_blob_master_src_FastPing_Public_Invoke-2DFastPing.ps1-23L142&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=YTfOXjyQ8rY60WaGEb0CqB7FRpp2ik4yKjn9ZT9Odzw&e=, which was added to prevent a different issue (which I can no longer recall what it was).
If you want to comment that out in your local module folder and let me know if that speeds it up for you? I can add a switch to prevent this attempt to resolve the DNS name if that's your issue.
— Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_austoonz_FastPing_issues_3-23issuecomment-2D1483951186&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=Mki6HFfHBh5ZcWyIv9_WQoijMq4ivgbQFBNJzxk8mEA&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AH2VJG2FBTL5Y4Z4Y4MN6YLW56BNVANCNFSM6AAAAAAWHHDQ7U&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=1SI5ozOnISHukjU2LUKx99SY1b5gsrfXRiQkUw6nhtM&m=wws5wnYBRQhgxHB8xOJrHZgpKkKMuuAwAiQkks6DMOA&s=vCbMwf_GEtSnzjipbrBrgTjCvC3GzOuNJtFz1NGS4Lw&e=. You are receiving this because you authored the thread.Message ID: @.@.>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.