How to Troubleshoot ‘Request Timed Out’ Error When Implementing ControlUp’s High Latency Analysis Script

A user asked for help with a script found at https://www.controlup.com/script-library-posts/analyze-high-latency-issues/, which was running the full 5 minutes before timing out. A member suggested to change the endpoint IP to the public one if the client is on the same network or at least pingable, but noted that most home firewalls will not allow ping so it will likely time out.

Read the entire ‘Troubleshooting Script from ControlUp Timing Out’ thread below:

Good morning. Not sure if this is the right place, but I’m trying to implement the script at https://www.controlup.com/script-library-posts/analyze-high-latency-issues/ and it looks like it tries to access the endpoint IP, not the public IP. The script runs the full 5 minutes before timing out, but we get "request timed out" messages after the tracert leaves our firewall. Am I missing something easy here? New to ControlUp so any assistance and patience is appreciated.

This can and will only work if the client is on the same network or at least pingable from your network. You could change it to client public ip but that depends on remotedx data being available and most home firewalls will not allow ping so it will probably timeout

Thank you very much for the insight. It’s appreciated.

Continue reading and comment on the thread ‘How to Troubleshoot ‘Request Timed Out’ Error When Implementing ControlUp’s High Latency Analysis Script’.  Not a member? Join Here!