#Iptrace multiple hosts free#

If you have an alert set up – and tied to a host (see above), but it seems like the alert isn't working, then changing your alert parameters (or create a new 'test' alert). Set up an alert that will fire instantly, with an event that is very evident. This should put a around the hop that's being monitored. If those brackets aren't showing, then that host isn't being watched. When a host is being watched by the alert system, there will be brackets around the hop number in the upper graph. Any alerts on the 'Selected' list will watch this host whenever this host is involved in any route (be it an intermediate host, or the final destination). Note that if you're tracing to a destination that doesn't respond, and you want to watch that destination (even though it's not on the upper graph), just right-click on the time-graph on the bottom and this same menu item should be on that menu.įrom here, you can move an alert from the 'Available' to the 'Selected' list. Then, right-click on the hop you want to monitor and select 'Watch this host (Alerts)…' from the menu.

To attach an alert to an IP, trace to the host you're interested in. An alert won't just start working automatically – you need to tell it which host(s) you want that alert to watch. Make sure you're 'Watching' a host with the alert.īy far, the most common reason that an alert isn't working is because it isn't tied to an IP address.

#Iptrace multiple hosts free#

Here are some suggestions - and feel free to check out our support pages for more information.

If alerts aren't working, there are a number of things you can do to troubleshoot.