Information and Support

So our Windows dev did some digging and this is what we were told. I've found the reason for the crash this person experienced when installing. If the service fails to start because the Listen() call throws an exception then the exception handler calls Close() and Close() fails to check if the handle pointer is a null reference before using it. What I don't know is why we are not able to start a named pipe on that persons machine. I'll add the missing check to the library code but that won't cure the actual problem they had, so I'll investigate further on what might prevent use opening a named pipe on Windows 10 Pro. I've never seen that fail before. So I don't think we have a general issue here, more likely a restriction configured on that machine or possibly the name we use for the pipe is already being used.

Maybe we were not understanding each other. I reviewed this post and I think what you are asking for is to specify what you'd like to ping. If so, this is something we've considered and may implement in the future but I'd like to explain why it's not that way right now. The main goal of the service is to let you know if your ISP is having problems. That means source and destination but not specifically with the ISP, only through it. In other words, so long as the destination is outside of the ISP, you'll be able to tell when/if your ISP is having problems. If we set the ping destination to a certain hop, then you'll only ever know if that hop becomes unavailable and since packets can take different paths, you may not know about other connections failing. This is why we just go through the provider to our own network where we have target servers that let the agents know if they reached or didn't reach the target, logging in between when there are IP outages. Now, if you were not even seeing hops coming in, that would mean that ICMP is being blocked somewhere and that would affect one aspect of the agent being able to determine outages. Pings aren't really that important but they play one part. There is a constant test being done for source/destination latency. If pings start showing a certain amount of latency, that will trigger an automatic speed test. I hope this helps to explain.

@fardvrsgr Hi Frances, When you create a new agent you are supposed to follow the instructions that are taking you to the point of downloading the executable to install the software on your PC In that page you didn't confirm that you downloaded the software so you cannot see the keys needed to continue the installation From the agent list if you click on the link "Click to complete" you will be taken to the page where you already downloaded the file and there you can simply press YES to confirm you did download the software (assuming you have) and there you will see the keys needed to install

Hi, Not sure how this got past us but there isn't anything that only shows the past hour but perhaps I'm not understanding the question. I believe the free community service shows the past 50 events, and the last four hours of pings. Pings are mainly just a quick way to know if something has been happening. Let us know if you have any more questions and apologies that this somehow got left open.

Thanks for feedback. They key to getting the best reports is to run the agent on something that can remain on 24/7 if possible. If that is not your main PC, then a very low cost second PC or a hardware agent. The only way to really know what is going on is to log everything non stop, at least for a while so you can also see trends.