On Thu, 29 Oct 2020 15:23:51 -0500, Knute Johnson wrote:
> Sorry to be slow responding Martin. It's been one of those weeks.
>
No problem - been there too. Thanks for the fuller explanation.
Of course you can't ask a client to run Wireshark, but it probably
wouldn't help with the problem anyway, now that I understand the setup.
However, if you know the problem client's URL or IP or can get then to
tell you what it is, then there's nothing to stop you pinging them or
using traceroute to see if the problem was transient or permanent and
where it is.
Whether you get a response from ping will depend on how their cable/ADSL/
whatever modem and firewall is configured. Mine, for example, is
configured to give no response whatsoever on any channel to stop the bad
lads from thinking there's anything turned on at my site (and checked for
invisibility against Gibson Labs).
However, traceroute should do its thing no matter what state how the
client 's front door is configured. because it will and either reach the
client's endpoint and say so, or, if it can't reach that, show you where
the failure is.
I hope this is useful info.